[Tfug] Slightly OT: Weird home networking issue

[Bexley Hall]

Hi Timothy,

On 2/22/2013 5:35 PM, Timothy D. Lenz wrote:
> 169.?? My network uses 192.168.xxx.xxx

I suspect the router (DHCP server therein) isn't actually
serving up 169 addresses but, rather, the client (PC) is
*assuming* a 169 address indicative that it doesn't have a
valid IP address (yet).  You will often see this on wireless
interfaces as they come up since you typically have the
system "already running" when you try to connect to an AP
whereas wired connections tend to negotiate their IP's
*while* booting (i.e., you don't often "plug/unplug" wired
connections like you do wireless ones)

AFAIK, you should be able to verify this by checking the lease
time on the IP address *at* the client (i.e., how long the
client has been *told* it is valid for).

[I only use static addresses, here, so can't comment firsthand]

> On 2/22/2013 4:04 PM, Zack Breckenridge wrote:
>> You mentioned DHCP "giving out" 169.x.y.z addresses, which to my
>> knowledge are so called "link local" addresses - usually indicative of
>> the *absence* of a DHCP server.

>> On Feb 22, 2013 3:26 PM, "Christopher Robbins" <robbinsc at gmail.com
>> On Fri, Feb 22, 2013 at 2:02 PM, Bexley Hall <bexley401 at yahoo.com
>>
>> 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.