Date: Sun, 9 Dec 2001 00:06:09 -0600 From: "Jim Fleming" <jfleming@anet.com> To: "Andrew C. Hornback" <achornback@worldnet.att.net>, "FBSD Questions" <questions@FreeBSD.ORG> Subject: Re: internal private IP address standards? Message-ID: <013001c18077$9a6bbca0$a300a8c0@ipv16> References: <000701c18070$d79d7e80$6600000a@ach.domain>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "Andrew C. Hornback" <achornback@worldnet.att.net> To: "Jim Fleming" <jfleming@anet.com>; "FBSD Questions" <questions@FreeBSD.ORG> Sent: Saturday, December 08, 2001 11:17 PM Subject: RE: internal private IP address standards? > > -----Original Message----- > > From: owner-freebsd-questions@FreeBSD.ORG > > [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Jim Fleming > > Sent: Sunday, December 09, 2001 12:00 AM > > To: Andrew C. Hornback; Joe & Fhe Barbish; FBSD Questions > > Subject: Re: internal private IP address standards? > > > > ----- Original Message ----- > > From: "Andrew C. Hornback" <achornback@worldnet.att.net> > > > > > > Most people that I know of use the address blocks set aside in RFC 1918. > > > > > > "3. Private Address Space > > > > > > The Internet Assigned Numbers Authority (IANA) has reserved the > > > following three blocks of the IP address space for private internets: > > > > > > 10.0.0.0 - 10.255.255.255 (10/8 prefix) > > > 172.16.0.0 - 172.31.255.255 (172.16/12 prefix) > > > 192.168.0.0 - 192.168.255.255 (192.168/16 prefix)" - RFC 1918 > > > > > > Full text can be found at: > > > http://www.faqs.org/rfcs/rfc1918.html > > > > Everyone does not follow RFCs... > > > > http://msdn.microsoft.com/downloads/sdks/platform/tpipv6/start.asp > > "If you have an IPv4 address that is part of the private address > > space (10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16) or the > > Automatic Private IP Addressing (APIPA) address space of > > 169.254.0.0/16 used by Windows 98 and Windows 2000, it is not globally > > routable. Otherwise, it is probably a public IP address and is > > globally routable. See the Debugging 6to4 configuration in this > > document for more help in determining whether your ISP connection > > supports 6to4." > > Isn't this par for the course as far as Microsoft is concerned? *shrug* > Don't answer that (that means you too, Anthony). > > Is APIPA an IETF thing or something similar? > > --- Andy > > http://www.isc.org/ml-archives/dhcp-server/2001/01/msg00674.html Ok, update. With a search on Google using "linklocal" I found a draft standard (draft-ietf-zeroconf-ipv4-linklocal-00.txt dated October 8th 2000) and the web site of an IETF working group (www.zeroconf.org, chartered Sept 1999) exploring the feasibility of "zero configuration networking" in the which this draft would probably play a major role. There are articles on Microsoft's web site that talk about the behavior change from the pre APIPA days. Specifically (as in the DHCP protocol from what I understand of it), the device would keep its address until the lease expired even if it couldn't contact a DHCP server. There is a registry setting that will cause an APIPA machine to revert to the old behavior. I think I saw similar hacks for Mac's while searching. The next logical question then is will the ISC DHCP client support this, in light of the "market" support this is gaining? A configurable option would of course be necessary. Then again, the ISC software is a reference implementation. Does that mean only official standards are supported? Just wondering, Adam -----Original Message----- From: JAMES, WARREN (SBCSI) [mailto:wj3857@sbc.com] Sent: Wednesday, January 24, 2001 1:26 PM To: 'dhcp-server@isc.org' Subject: RE: 169.254.0.0 What standard is this from? > Many DHCP clients these days, when they can't locate a DHCP > server, assign > themselves and address in the 169.254.0.0/16 range. Is this > specified in a > standard somewhere? I searched RFC pages, the DHCP FAQ pages > and the mailing > list archives for "169.254" and some variants, but couldn't > find anything. (pretty much) self-explanatory: $ whois -h rs.arin.net 169.254.0.0 Internet Assigned Numbers Authority (IANA) (NETBLK-LINKLOCAL) For use with Link Local Networks Information Sciences Institute University of Southern California 4676 Admiralty Way, Suite 330 Marina del Rey, CA 90292-6695 Netname: LINKLOCAL Netblock: 169.254.0.0 - 169.254.255.255 Coordinator: Internet Corporation for Assigned Names and Numbers (IANA-ARIN) iana@IAN A.ORG (310) 823-9358 Domain System inverse mapping provided by: BLACKHOLE.ISI.EDU 128.9.64.26 BLACKHOLE.EP.NET 198.32.1.116 Record last updated on 30-Aug-2000. Database last updated on 24-Jan-2001 07:54:28 EDT. ------ http://www.thecertificationhub.com/tips_tricks_hacks_2000.htm HOW TO DISABLE AUTOMATIC IP ADDRESSING Windows 2000 provides the ability for clients to automatically assume an IP address from the private subnet 169.254.n.n if no DHCP server is available on the network. This feature is called Automatic Private IP Addressing, or APIPA. It's great when you don't have a DHCP server, you don't need public IP addresses, and don't want the hassle of having to assign IP addresses manually. In some situations, however, you might want to disable APIPA. For example, perhaps you do have a DHCP server on the network but don't want the system to use APIPA when the DHCP server is unable to service requests or the client is unable to communicate with the server for some reason. Having the system fail to obtain an IP address is a good means of notification that a problem exists on the network. You can disable APIPA in one of two ways. You can implicitly disable it by assigning a static IP address to the workstation. Or, you can modify the registry to disable APIPA explicitly so that the workstation, when unable to obtain an IP address from a DHCP server, generates an error to that effect. To disable APIPA, open the Registry Editor and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<adapter> where <adapter> is the name of the interface for which you want to disable APIPA. Add a REG_DWORD value named IPAutoconfigurationEnabled in the key and set it to 0x0. Repeat the process for any other adapters that need to have APIPA disabled, then restart the computer. ----- It all boils down to fairness. Which list do you think is more fair ? The "toy" IPv4 Internet Early Experimentation Allocations ? http://www.iana.org/assignments/ipv4-address-space or The Proof-of-Concept IPv8 Allocations ? http://www.ntia.doc.gov/ntiahome/domainname/130dftmail/unir.txt Why would people pay for Address Space, when it is FREE ? Jim Fleming http://www.DOT-BIZ.com http://www.in-addr.info 3:219 INFO To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?013001c18077$9a6bbca0$a300a8c0>