[Tfug] Slightly OT: Weird home networking issue

Bexley Hall bexley401 at yahoo.com
Fri Feb 22 16:11:28 MST 2013


Hi Christopher,

On 2/22/2013 3:26 PM, Christopher Robbins wrote:
> On Fri, Feb 22, 2013 at 2:02 PM, Bexley Hall<bexley401 at yahoo.com>  wrote:
>
>> I'd had problems with the *wireless* functionality in a Centurylink
>> (Qwest) "router".  It would crash the router after some period of
>> operation (I believe a thermal issue taking down the power supply
>> periodically).  Disabling the radio "fixed" the problem.
>>
>> Have you assigned static IP's?  I.e., are you sure the router
>> hasn't reset itself and its idea of what *your* IP should be, etc.?
>> (i.e., can you bring *another* host online after the crash and
>> access the router?  Or, has it lost *all* wired connectivity?)
>
> It COMPLETELY falls apart.   DHCP gives out 169.x.y.z addresses, static
> addresses quit responding, etc.

So, the reason the ping fails is not because the interface is
"dead" (down) but, rather, has "moved" to a different IP (?).

Sounds like the router has reset itself (can you watch the
power LED -- or any other visible indicators -- to see if it "winks"
at about the time it bites the shed?

Do you have another similar/equivalent wall wart that you could
power it with, temporarily (i.e., these are easy to swap out
so relatively painless test to try).

[And I'm sure you've already verified you have the most current
firmware?]

>> (I've also seen some devices have problems re-autonegotiating
>> link speeds -- esp Gb-to-Gb)
>
> Might be related - the ports on the router are 100 Mbps, and the switch is
> supposed to autonegotiate.  What's weird is how long everything stays up -
> I can see the switch establish the connection to the router, and the ping
> works for a few minutes...I'm not sure what happens, but the whole thing
> resets and the ping dies.  :-/

The operative word seems to be "resets".

Turn off the wireless and repeat the test.  (i.e., disable the
radio, don't just stop using it).

> I dug up an Airport Express I had laying around, and using that to connect
> the clients behind the switch works...Definitely something wrong with the
> router.  Looks like this now -
>
> Modem/router - (wireless) ->  Airport Express - (wired) ->  Switch

So, the wired interface is not working even though the wireless is
staying up?  Are you sure the wireless I/F isn't also "glitching"
but possibly recovering (without you noticing it)?




More information about the tfug mailing list