cothrige wrote:
* H.S. ([EMAIL PROTECTED]) wrote:
Okay. I was actually thinking that maybe your modem is set to 'dial on
demand' and the Windows laptop may be sending some packets
intermittently to keep the connection up (it does weird things you know,
not that I know much about all of them). L
* H.S. ([EMAIL PROTECTED]) wrote:
>
> Okay. I was actually thinking that maybe your modem is set to 'dial on
> demand' and the Windows laptop may be sending some packets
> intermittently to keep the connection up (it does weird things you know,
> not that I know much about all of them). Looks like
cothrige wrote:
> * H.S. ([EMAIL PROTECTED]) wrote:
>> Does the same 'blackout' period occur on your computer when your wife's
>> laptop is also connected to the linksys router? Or does it occur only
>> when your computer is ON.
>
> Initially I noticed this when her computer was not being used or
* H.S. ([EMAIL PROTECTED]) wrote:
>
> Does the same 'blackout' period occur on your computer when your wife's
> laptop is also connected to the linksys router? Or does it occur only
> when your computer is ON.
Initially I noticed this when her computer was not being used or was
completely shut d
cothrige wrote:
> I knocked around a bit in a browser and it appears that 192.168.15.1
> is my Linksys router, and 192.168.1.254 is the DSL modem. I would
Yup, that makes sense. I was expecting it to be 192.168.15.1 though, in
which case I would expect the router to get the nameservers from the
> installation, was automatic. During boot everything would be
> connected and all the dhcp stuff with the router would be setup and I
> could see this come across the screen and then bang, I was online.
> The same is true here in Debian, except that nothing ever appears
> onscreen or in dmesg and
* H.S. ([EMAIL PROTECTED]) wrote:
>
> So your router's LAN address is 192.168.15.1. Is that correct? You can
> check this by opening your router's web configuration page. OR, you can
> also try on your wife's laptop (which IIRC runs Windows and works fine)
> and open a command prompt terminal and
cothrige wrote:
>> When you expect a connection to have been established, what is the
>> output of these commands:
>>
>> $> route -n
>> $> ifconfig -a
>> $> cat /etc/resolv.conf
>
> BTW, I had to run this as root, even though it appears you were
> expecting a user account to work, but I could no
On Thu, Nov 09, 2006 at 12:48:24PM -0600, cothrige wrote:
> * H.S. ([EMAIL PROTECTED]) wrote:
> ...
> worked fine, but lately the connection is uber-flaky. It doesn't
> always come up at boot, and even when it does it is dropping out
> badly. When this happens I will experience something like fiv
* Andrew Sackville-West ([EMAIL PROTECTED]) wrote:
> On Thu, Nov 09, 2006 at 12:57:06PM -0600, cothrige wrote:
> >
> > Maybe that could be my trouble, but why do you suppose I would not
> > have the same problem with the other computer using that same router?
>
> crucial information. maybe you sa
On Thu, Nov 09, 2006 at 12:57:06PM -0600, cothrige wrote:
>
> Maybe that could be my trouble, but why do you suppose I would not
> have the same problem with the other computer using that same router?
crucial information. maybe you said it before, but I didn't see
it. That pretty much narrows it
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
>
> Perhaps the router is taking care of PPPoE? SWBell (which I
> previously used as ISP) typically uses PPPoE.
I don't believe so. I had initially connected the modem directly to
the computer, this was when I first switched to DSL, and I had not
i
* H.S. ([EMAIL PROTECTED]) wrote:
>
> I am not sure if I see the picture: are you trying to connect to your
> ADSL modem through a router or directly from your Debian computer?
I have an ADSL modem which is connected to my Linksys router with my
computer then connected to that, as is my wife's.
* cothrige <[EMAIL PROTECTED]> [061109 09:52]:
> * Russell L. Harris ([EMAIL PROTECTED]) wrote:
> >
> > From your bellsouth address and the fact that you have DHCP, I presume
> > you are also have to contend with PPPoE. I suspect that PPPoE may be
> > the culprit.
>
> No, I have never had to
cothrige wrote:
I have been having some troubles with my DSL internet connection for a
while now. First an upgrade appeared to remove some or all of the
dhcp related software on my box. Thanks to this list I think I fixed
that by installing dhcp3-client. But, then the connection would only
be
* Russell L. Harris ([EMAIL PROTECTED]) wrote:
> Patrick -
>
> From your bellsouth address and the fact that you have DHCP, I presume
> you are also have to contend with PPPoE. I suspect that PPPoE may be
> the culprit.
>
No, I have never had to use PPPoE before that I am aware of. Under
Sl
cothrige wrote:
I have been having some troubles with my DSL internet connection for a
while now. First an upgrade appeared to remove some or all of the
dhcp related software on my box. Thanks to this list I think I fixed
that by installing dhcp3-client. But, then the connection would only
be
I have been having some troubles with my DSL internet connection for a
while now. First an upgrade appeared to remove some or all of the
dhcp related software on my box. Thanks to this list I think I fixed
that by installing dhcp3-client. But, then the connection would only
be there about half o
18 matches
Mail list logo