Michael wrote:
> The new private address interested me too, I noted it down and looked it
> up:
> 169.254.0.0 - 169.254.255.255 (169.254/16 prefix)
If memory serves, winders uses that range for its DHCP if you don't
specify... winders is the only area I have come accross it to date.
Adrian
1252
- Original Message -
From: "Nick Rout" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 01, 2002 9:09 AM
Subject: Re: private address 169.254.x.x (was: Many thanks)
> I had a machine coming up with these addresses a while ago and did some
> research
I had a machine coming up with these addresses a while ago and did some
research that basically led me to believe that the 169.254 addresses
were not supposed to be used in any real way, and that MS machines were
configured to an address in that range when they couldn't get an address
via dhcp etc
Christchurch
[EMAIL PROTECTED]
Ph 025 246 0592
Fax 03 354 1252
- Original Message -
From: "Chris Hellyar" <[EMAIL PROTECTED]>
To: "linux" <[EMAIL PROTECTED]>
Sent: Wednesday, May 01, 2002 12:27 AM
Subject: Re: private address 169.254.x.x (was: Many thanks)
> This
This is the draft ietf document for the range...
http://www.ietf.org/proceedings/00dec/I-D/draft-ietf-zeroconf-ipv4-linklocal
-01.txt
I can't find a RFC that formally defines it, but other drafts such as:
http://www.ietf.org/internet-drafts/draft-hong-autoconf-multicast-ipv4-00.tx
t
refer to t
The new private address interested me too, I noted it down and looked it up:
169.254.0.0 - 169.254.255.255 (169.254/16 prefix)
rfc1918 doesn't mention it of course. Most of the examples I dug up on the
net refer to MS network implementation where they use Automatic Private IP
Addressing (APIPA
