I think the link-local scope was set to /10 simply to "fit in" better with the other scopes, e.g. site-local (before it was replaced with unique local). Initially I had thought maybe it was to allow the use of many link-local networks on the same link, but RFC 4291 explicitly states that only fe80::/64 may be used.
JUNOS also allows You to configure link local addresses with masks shorter than 64: ## Using /48 netmask [edit interfaces ge-0/0/1] regress@R1# set unit 0 family inet6 address fe80::1111:2222:3333:4444/48 [edit interfaces ge-0/0/1] regress@R1# show unit 0 { family inet { address 10.0.113.2/24; address 203.0.113.6/29; } family inet6 { address fe80::1111:2222:3333:4444/48; } } [edit interfaces Using a prefix other than fe80 for a link-local address can result in unexpected behaviors. Although permitted by the RFC 4291, using a prefix other than fe80 should be tested prior to usage. In Chapter 6 we will examine the structure, uses, and configuration options for link-local addresses in much more detail. Sep 01, 2019 · If we configure a global unicast address without configuring a link-local address. It automatically generates a link-local address. The figure3 illustrates the verification of ipv6 address. Unless we configure link-local address manually, Cisco routers create the link-local address using FE80::/10 prefix and also using the EUI-64 process. Aug 13, 2014 · The DHCP is working, BUT my problem is that the Link-local IPv6 address is being assigned AAAA and PTR records in my DNS and NOT the IPv6 IP addresses that I am assigning from DHCP. For example: I have a workstation that I am assigning an IPv6 address from DHCP to the IPv6 network with an address of FD80:4000:2000::2:23 (/64). Oct 22, 2004 · Description of problem:Whenever I do ping6 of a link-local address (FE80), pikg6 says "connect: Invalid argument" Version-Release number of selected component (if applicable): How reproducible: every time Steps to Reproduce: 1.ping6 fe80::a00:20ff:fe9d:5c55 2. 3. Jun 15, 2019 · 1. The link-local address is a 128bit address that has a link local scope meaning that it is only relevant on it's local link/segment. 2. These have the prefix FE80::/10 meaning that the first 10 bits of a link-local address will always be the sam コンピュータネットワークにおいて、リンクローカルアドレス（英語: link-local address ）とは、ホストが接続されている ネットワークセグメント （英語版） （リンク）または ブロードキャストドメイン （英語版） 内の通信に対してのみ有効な ネットワークのアドレス （英語版） である。
link-local address as far as I understand it is a device that has an IPv6 ip assigned to that nic and normally starts with FE80::. This ip is used only for your single-link network scope and should at all purposes avoid routing it.
Aug 07, 2014 · Addresses in the Unique Local Address range must be manually assigned, while link-local addresses are generated automatically. A Unique Local Address (if assigned) has no special significance, while a link-local address must exist on each IPv6-enabled interface as these addresses play a crucial role in providing core IPv6 services (such as IPv6 Link Local Addresses can be configured in two ways. These Link-Local address configuration ways are : Auto-Address Configuration; Manual Configuration . Auto-Address Configuration is done automaticaly with the help of Link Local Prefix (FE80::/10) and Interface Identifier in EUI-64 Format. This is the widely used method to configure a IPv6
IPv6 Link Local addresses are identified among IPv6 addresses by reserving the left most 64 bits as 1111111010000000 0000000000000000 0000000000000000 0000000000000000 (translates to FE80 in hexadecimals). IPv6 Link Local addresses are used by devices for communicating with other nodes on the same link. The scope of an IPv6 Link Local address
I'm looking to prevent the IPv6 link local address from being randomly assigned. I'm not looking to disable v6 but rather statically assign my own link local. I've done ifconfig vboxnet0 inet6 add fe80::/126 and it works and I can do ping6 -I vboxnet0 fe80::1 and successfully ping my VM but then eventually I end up with 2 link local addresses # Edited by hand to avoid using the ipv6 link local scopeless address # check resolv.conf.old to see normal file #nameserver fe80::beef nameserver 127.0.1.1 search lan So. unless I start playing with chattr +i and other tricks to prevent that script (or whatever it is) from touching /etc/resolv.conf, I feel like this semi-static option isn't In the IPv6 address scheme, the network of fe80::/10 is reserved for link-local addresses. The address fe80::/64 is a network address that indicates, in this workstation, fe80::/64 is actually used for link-local addresses. Thus the address fe80::30d0:115:3f57:fe4c/128 is a valid IPv6 link-local address.