The idea is to make 9.1 zeroconf ready. http://www.zeroconf.org
zeroconf is a system for configuring machines completely automatically, assigning ip addresses on local lan without dhcp and all, and the 169.254/16 network is a part of that
do we really need computers marketed for the stupid? in the end it'll be windoze all over again. -- ray http://www.redrum.org rcanfiel@blade.redrum.org "UNIX _IS_ user friendly, its just picky about who its friends are."
On Thu August 19 2004 11:19 am, ray canfield wrote:
The idea is to make 9.1 zeroconf ready. http://www.zeroconf.org
zeroconf is a system for configuring machines completely automatically, assigning ip addresses on local lan without dhcp and all, and the 169.254/16 network is a part of that
do we really need computers marketed for the stupid? in the end it'll be windoze all over again.
-- ray
The legend I have heard is that 169.254.x.x is a Class B address range that was owned by an individual that worked at Microsoft. He sold it to Microsoft and Microsoft put it to use for those instances where no DHCP server or static address was available. WIndows OS could then boot up without timing out waiting for a network connection. I believe Microsoft has voluntarily retired this Class B range for the public good to be used in ways that Anders and others have described. I don't believe that it is a public internet, routable IP address range just like 192.168.x.x and 10.x.x.x. Thats what I've heard anyway... And yes, I do believe we need computers that are easy for anyone to use so that there will always be a need for computer service and support professionals. Stan Stan
On Thu, 19 Aug 2004 11:56:53 -0500
SRGlasoe
I don't believe that it is a public internet, routable IP address range just like 192.168.x.x and 10.x.x.x. It definitely is not. I checked with IANA before I posted my original message. only 192.168.x.x and 10.x.x.x. and 172.16.x.x.
BTW: here is the IANA writeup on 169.254:
169.254.0.0/16 - This is the "link local" block. It is allocated for
communication between hosts on a single link. Hosts obtain these
addresses by auto-configuration, such as when a DHCP server may not
be found.
--
Jerry Feldman
On Thu August 19 2004 1:52 pm, Jerry Feldman wrote:
On Thu, 19 Aug 2004 11:56:53 -0500
SRGlasoe
wrote: I don't believe that it is a public internet, routable IP address range just like 192.168.x.x and 10.x.x.x.
It definitely is not. I checked with IANA before I posted my original message. only 192.168.x.x and 10.x.x.x. and 172.16.x.x.
Agreed. Should have worded my reply better. It is advised to NOT route this through the public internet. It is advised to treat it AS IF it is a private subnet like 192.169.x.x., 172.16.x.x and 10.x.x.x and not let it out 'into the wild'.
BTW: here is the IANA writeup on 169.254: 169.254.0.0/16 - This is the "link local" block. It is allocated for communication between hosts on a single link. Hosts obtain these addresses by auto-configuration, such as when a DHCP server may not be found.
Exactly. A little further googling on my part and this range seems to have originated from MS with link-local in mind. http://files.zeroconf.org/draft-ietf-zeroconf-ipv4-linklocal.txt section 2.6.2 gives a good explanation for this range. Appears also that SUSE 9.1 is the first time its been used by SUSE. Stan
Exactly. A little further googling on my part and this range seems to have originated from MS with link-local in mind. http://files.zeroconf.org/draft-ietf-zeroconf-ipv4-linklocal.txt section 2.6.2 gives a good explanation for this range. Appears also that SUSE 9.1 is the first time its been used by SUSE. That is true. I initially was curious because the first time I saw this in the routing table was when I was trying to set my laptop up at MIT. Under 9.0, I had several profiles, but they were destroyed when I upgraded to 9.1, and I rebuilt the profiles. I initially had the MIT
On Thu, 19 Aug 2004 16:45:09 -0500
SRGlasoe
On Thursday 19 August 2004 11:19 am, ray canfield wrote:
The idea is to make 9.1 zeroconf ready. http://www.zeroconf.org
zeroconf is a system for configuring machines completely automatically, assigning ip addresses on local lan without dhcp and all, and the 169.254/16 network is a part of that
do we really need computers marketed for the stupid? in the end it'll be windoze all over again.
Of course we do! What we really need are computers that are usable by people who like to work on things other than computers. Once upon a time I enjoyed working on cars, now they are simply a means of transportation. Computers should be the same, something the average guy can use to help him do productive work or fun. But, the guy that likes to putter with electrics and such things should have the option to play to his hearts content. No one should have all the fun to the exclusion of others with different tastes. richard
participants (4)
-
Jerry Feldman
-
ray canfield
-
Richard
-
SRGlasoe