Re: weird network address

Bah, my reply went to jamie, and not aklug. Here's what I put:

I believe that like 10.0.0.0/8, 192.168/16, 172.[16-31]/16, the
169.254.0.0/16 network is just another block of nonroutable, local-LAN
ip addresses.

Windows machines will, by default, assign themselves a 169.x address if
they cannot find a DHCP server, but are configured by DHCP.

If you're getting a 169.x.x.x address, it might be because either your
machine can't find a DHCP address, is finding another DHCP server, or is
just wacked out on wowie sauce.

For more information on nonroutable, special-use IPv4 addresses, see
RFC3330: http://www.faqs.org/rfcs/rfc3330.html

Woo, aren't RFC's just *wonderful* reads?!

Adam

jonr@destar.net wrote:
> Quoting Greg Madden <pabi@gci.net>:
>
>
>> I am behind a Ipcop firewall, with a dhcp server running, internal
>> address's are 192.169.0.x range. I ran ifconfig and got a strange address
>> for my box, 169.254.4.199, and a whois spits out the following. How
>> would something like this happen ?
>>
>
> Isn't that just an address that gets assigned if no network can be found? I know
> M$ boxes get that type of IP address when they can't. I would check the
> connection from the computer getting that address and make sure it is good.
>
> Jon
> ---------
> To unsubscribe, send email to <aklug-request@aklug.org>
> with 'unsubscribe' in the message body.
>
>

---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
Received on Wed Jun 21 22:09:15 2006