Link-local address




In a computer network, a link-local address is a network address that is valid only for communications within the network segment or the broadcast domain that the host is connected to. Link-local addresses are most often assigned automatically through a process known as stateless address autoconfiguration or link-local address autoconfiguration.[1]


Link-local addresses are not guaranteed to be unique beyond their network segment, therefore routers do not forward packets with link-local addresses.


Link-local addresses for IPv4 are defined in the address block 169.254.0.0/16 in CIDR notation. In IPv6, they are assigned the address block fe80::/10.[2]




Contents






  • 1 Address assignment


  • 2 IPv4


  • 3 IPv6


  • 4 See also


  • 5 References





Address assignment


Link-local addresses may be assigned manually by an administrator or by automatic operating system procedures; this process is also known as self-assigned IP addressing. For Internet Protocol (IP) networks, they are assigned most often using stateless address autoconfiguration. In IPv4,[3] they are normally only used to assign IP addresses to network interfaces when no external, stateful mechanism of address configuration exists, such as the Dynamic Host Configuration Protocol (DHCP), or when another primary configuration method has failed. In IPv6,[4] link-local addresses are mandatory and required for the internal functioning of various protocol components.


Automatic address configuration of link-local addresses is often non-deterministic as the resulting address cannot be predicted. However, in IPv6 it is usually derived automatically from the interface media access control (MAC) address in a rule-based method.



IPv4


In RFC 3927, the Internet Engineering Task Force (IETF) has reserved the IPv4 address block 169.254.0.0/16 (169.254.0.0 – 169.254.255.255) for link-local addressing. The entire range may be used for this purpose, except for the first and last 256 addresses (169.254.0.0/24 and 169.254.255.0/24), which are reserved for future use and must not be selected by a host using this dynamic configuration mechanism.[5] Link-local addresses are assigned to interfaces by host-internal, i.e. stateless, address autoconfiguration when other means of address assignment are not available.[3]


RFC 3927 warns against the simultaneous use of IPv4 addresses of different scope,[6] such as configuring link-local addresses as well as globally routable addresses on the same interface. Therefore, hosts search for a DHCP server on the network before assigning link-local addresses.


In the automatic address configuration process, network hosts select a random candidate address within the reserved range and use Address Resolution Protocol (ARP) probes to ascertain that the address is not in use on the network. If a reply is received to the ARP, it indicates the candidate IP address is already in use; a new random candidate IP address is then created and the process repeated. The process ends when there is no reply to the ARP, indicating the candidate IP address is available.


When a globally routable or a private address becomes available after a link-local address has been assigned, the use of the new address should generally be preferred to the link-local address for new connections but communication via the link-local address is still possible.[7]


Microsoft refers to this address autoconfiguration method as Automatic Private IP Addressing (APIPA).[8] It is sometimes also casually referred to as auto-IP.



IPv6


In the Internet Protocol Version 6 (IPv6), the address block fe80::/10 has been reserved for link-local unicast addressing.[2] Of the 64 bits of a link-local addresses' network component, the most significant 10 bits (1111111010) correspond to the IANA-reserved "global routing prefix" for link-local addresses, while the "subnet ID" (the remaining 54 bits) is zero.[9]


Unlike IPv4, IPv6 requires a link-local address on every network interface on which the IPv6 protocol is enabled, even when routable addresses are also assigned.[10] Consequently, IPv6 hosts usually have more than one IPv6 address assigned to each of their IPv6-enabled network interfaces. The link-local address is required for IPv6 sublayer operations of the Neighbor Discovery Protocol, as well as for some other IPv6-based protocols, such as DHCPv6.


When using an IPv6 link-local address to connect to a host, a zone index must be added to the address so that the packets can be sent out on the correct interface.


In IPv6, addresses may be assigned by stateless (automatic) or stateful (manual) mechanisms. Stateless address autoconfiguration is performed as a component of the Neighbor Discovery Protocol (NDP),[11] as specified in RFC 4862. The address is formed from its routing prefix and the MAC address of the interface.


Through NDP routing prefix advertisements, a router or server host may announce configuration information to all link-attached interfaces which causes additional IP address assignment on the receiving interfaces for local or global routing purposes. This process is sometimes also considered stateless, as the prefix server does not receive or log any individual assignments to hosts. Uniqueness is guaranteed automatically by the address selection methodology. It may be MAC-address based according to RFC 4862, or randomized according to RFC 4941. Automatic duplicate address detection algorithms prevent assignment errors.



See also



  • Zero-configuration networking

  • Private network

  • Unique local address



References





  1. ^ RFC 3927. IETF. doi:10.17487/RFC3927. https://tools.ietf.org/html/rfc3927. 


  2. ^ ab RFC 4291 section 2.4


  3. ^ ab RFC 3927, Dynamic Configuration of IPv4 Link-Local Addresses, S. Cheshire, B. Aboba, E. Guttman, The Internet Society (May 2005)


  4. ^ R. Hinden; S. Deering (February 2006). IP Version 6 Addressing Architecture. IETF. doi:10.17487/RFC4291. RFC 4291. https://tools.ietf.org/html/rfc4291.  Updated by RFC 5952, RFC 6052, RFC 7136, RFC 7346, RFC 7371, RFC 8064.


  5. ^ RFC 3927 section 2.1


  6. ^ RFC 3927 section 1.9


  7. ^ RFC 3927 section 2.6.1


  8. ^ "APIPA". Microsoft..mw-parser-output cite.citation{font-style:inherit}.mw-parser-output .citation q{quotes:"""""""'""'"}.mw-parser-output .citation .cs1-lock-free a{background:url("//upload.wikimedia.org/wikipedia/commons/thumb/6/65/Lock-green.svg/9px-Lock-green.svg.png")no-repeat;background-position:right .1em center}.mw-parser-output .citation .cs1-lock-limited a,.mw-parser-output .citation .cs1-lock-registration a{background:url("//upload.wikimedia.org/wikipedia/commons/thumb/d/d6/Lock-gray-alt-2.svg/9px-Lock-gray-alt-2.svg.png")no-repeat;background-position:right .1em center}.mw-parser-output .citation .cs1-lock-subscription a{background:url("//upload.wikimedia.org/wikipedia/commons/thumb/a/aa/Lock-red-alt-2.svg/9px-Lock-red-alt-2.svg.png")no-repeat;background-position:right .1em center}.mw-parser-output .cs1-subscription,.mw-parser-output .cs1-registration{color:#555}.mw-parser-output .cs1-subscription span,.mw-parser-output .cs1-registration span{border-bottom:1px dotted;cursor:help}.mw-parser-output .cs1-ws-icon a{background:url("//upload.wikimedia.org/wikipedia/commons/thumb/4/4c/Wikisource-logo.svg/12px-Wikisource-logo.svg.png")no-repeat;background-position:right .1em center}.mw-parser-output code.cs1-code{color:inherit;background:inherit;border:inherit;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;font-size:100%}.mw-parser-output .cs1-visible-error{font-size:100%}.mw-parser-output .cs1-maint{display:none;color:#33aa33;margin-left:0.3em}.mw-parser-output .cs1-subscription,.mw-parser-output .cs1-registration,.mw-parser-output .cs1-format{font-size:95%}.mw-parser-output .cs1-kern-left,.mw-parser-output .cs1-kern-wl-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right,.mw-parser-output .cs1-kern-wl-right{padding-right:0.2em}


  9. ^ Hinden, R.; Deering, S. (February 2006), "2.5.6: Link-Local IPv6 Unicast Addresses", RFC 4291: IP Version 6 Addressing Architecture, Fremont, CA: IETF.


  10. ^ Hinden, R.; Deering, S. (February 2006), "Section 2.8: A Node's Required Addresses", RFC 4291: IP Version 6 Addressing Architecture, Fremont, CA: IETF.


  11. ^ RFC 4862, IPv6 Stateless Address Autoconfiguration, S. Thompson, T. Narten, T. Jinmei (September 2007)









-

這個網誌中的熱門文章

12.7 cm/40 Type 89 naval gun

圖片
12.7 cm/40 Type 89 naval gun Type 89 gun mounted on Chitose Type Naval gun anti-aircraft gun Place of origin Japan Service history In service 1932–45 Used by Imperial Japanese Navy Wars World War II Production history Designed 1928–32 Produced 1932–45 No.  built ~1500 Variants Type 88 Specifications Mass 3,100 kilograms (6,834 lb) Barrel length 5,080 millimeters (16 ft 8 in) (bore length) Shell Fixed Shell weight 20.9–23.45 kilograms (46.1–51.7 lb) Caliber 12.7-centimeter (5.0 in) Breech horizontal breech block Elevation -8° to +90° [1] Rate of fire 8-14 rounds per minute Muzzle velocity 720–725 meters per second (2,360–2,380 ft/s) Maximum firing range 9,440 meters (30,970 ft) at 90° (AA ceiling) 14,800 meters (48,600 ft) at 45° The 12.7 cm/40 Type 89 naval gun was a Japanese anti-aircraft (AA) gun introduced before World War II. It was the Imperial Japanese Navy's standard heavy AA
閱讀完整內容

Shark

圖片
For other uses, see Shark (disambiguation). Sharks Temporal range: Ludfordian-Present, 425–0 Ma PreЄ Є O S D C P T J K Pg N [1] Clockwise from top left: spiny dogfish, Japanese sawshark, whale shark, great white shark, horn shark, frilled shark, scalloped hammerhead and Australian angelshark representing the orders Squaliformes, Pristiophoriformes, Orectolobiformes, Lamniformes, Heterodontiformes, Hexanchiformes, Carcharhiniformes and Squatiniformes respectively. Scientific classification Kingdom: Animalia Phylum: Chordata Class: Chondrichthyes Subclass: Elasmobranchii Infraclass: Euselachii Superorder: Selachimorpha Orders Carcharhiniformes Heterodontiformes Hexanchiformes Lamniformes Orectolobiformes Pristiophoriformes Squaliformes Squatiniformes † Cladoselachiformes † Hybodontiformes † Symmoriida † Xenacanthida (Xenacantiformes) † Elegestolepis † = extinct Synonyms Pleurotremata Sharks
閱讀完整內容

Wiciokrzew

圖片
Wiciokrzew, suchodrzew Morfologia (wiciokrzew pospolity) Systematyka [1] Domena eukarionty Królestwo rośliny Klad rośliny naczyniowe Klad rośliny nasienne Klasa okrytonasienne Klad astrowe Rząd szczeciowce Rodzina przewiertniowate Rodzaj wiciokrzew Nazwa systematyczna Lonicera L. Sp. Pl. 173. 1 Mai 1753 Typ nomenklatoryczny Lonicera caprifolium L. [2] Multimedia w Wikimedia Commons Hasło w Wikisłowniku Kwiaty suchodrzewu pospolitego Owoce suchodrzewu pospolitego Kwiaty wiciokrzewu pomorskiego Kwiaty wiciokrzewu przewiercienia Wiciokrzew , suchodrzew ( Lonicera L.) – rodzaj roślin wieloletnich należący do rodziny przewiertniowatych ( Caprifoliaceae ). Rośliny zielne i pnące nazywane są wiciokrzewami, natomiast krzewy i niewielkie drzewa – suchodrzewami. Rodzaj liczy około 180 gatunków szeroko rozprzestrzenionych na całej półkuli północnej [3] [4]
閱讀完整內容