| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
DHCP Autoconfiguration / Automatic Private IP Addressing (APIPA) (Page 3 of 3) APIPA Limitations Bear in mind that APIPA is not a proper replacement for full DHCP. The 169.254.0.0/16 block is a private IP range and comes with all the limitations of private IP addresses, including inability to use these addresses on the Internet. Also, APIPA cannot provide the other configuration parameters that a client may need to get from a DHCP server. Finally, APIPA will not work properly in conjunction with proxy ARP, because the proxy will respond for any of the private addresses, so they will all appear to be used. Since it uses ARP to check for address conflicts, APIPA is not well-suited for large internetworks. To use it on an internetwork with multiple subnets, you would require software that allows each subnet to use a different portion of the full 169.254.0.0/16 blocks, to avoid conflicts. In practice, APIPA is a solution for small networks; large internetworks deal with the problem of not being able to contact a DHCP server by making sure that a client can always contact a DHCP server. J
Home - Table Of Contents - Contact Us The TCP/IP Guide (http://www.TCPIPGuide.com) Version 3.0 - Version Date: September 20, 2005 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||