Introduction

The purpose of this record is to carry out an knowledge of IPv6 Link-neighborhood address in a netjob-related. A link-regional address is an IPv6 unicast attend to that can be immediately configured on any interface utilizing the link-regional predeal with FE80::/10 (1111 1110 10) and the interconfront identifier in the modified EUI-64 format. Link-local addresses are not necessarily bound to the MAC address (configured in a EUI-64 format). Link-local addresses deserve to likewise be manually configured in the FE80::/10 format utilizing the ipv6 resolve link-regional command.

You are watching: Why can the same link-local address be assigned to both ethernet interfaces

These addresses refer only to a certain physical attach and also are offered for addressing on a single connect for objectives such as automatic deal with configuration and also neighbor discovery protocol. Link-regional addresses can be supplied to reach the bordering nodes attached to the very same connect. The nodes perform not require a worldwide distinctive resolve to connect. Routers will not forward datagram using link-neighborhood addresses. IPv6 routers must not forward packets that have link-local resource or destination addresses to various other links. All IPv6 allowed interdeals with have actually a link-local uniactors address.

Prerequisites

Requirements

Ensure that you have understanding of IPv6 Address Formats before you attempt this configuration.

Materials Used

This record is not restricted to particular software application and also hardware versions.

The configurations in this document are based upon the slrfc.org 3700 series router through slrfc.org IOS® Software Release 12.4 (15)T1.

Conventions

Refer to slrfc.org Technical Tips Conventions for even more information on document conventions.

Configure

In this example, the routers R1, R2 and R3 are linked by means of serial interconfront and have the IPv6 addresses configured as stated in the network-related diagram. Loopback addresses are configured on the routers R1 and also R3, and the routers use OSPFv3 to interact through each other. This example uses the ping command also to demonstrate the connectivity between the routers utilizing link-regional addresses. The routers R1 and R3 can ping each other via the IPv6 international unicast attend to, however not with their link-regional attend to. However, router R2 being directly associated to R1 and also R3 can communicate through both the routers utilizing their link-neighborhood address, bereason link-regional addresses are provided just within that neighborhood netjob-related certain to the physical interface.

Network-related Diagram

This document supplies this network setup:

*

Configurations

This document uses these configurations:

Here is a connect to a video clip (easily accessible on slrfc.org Support Community) that demonstrates the crucial distinction in between the IPv6 Link-Local Address and international uniactors resolve in slrfc.org IOS routers:

Understanding IPv6 Link-Local Address

*

Router R1

!hostname R1!ipv6 cef!ipv6 unicast-routing!interface Loopback10 no ip attend to ipv6 address 2010::/64 eui-64!--- Assigned a IPv6 unicast attend to in EUI-64 format. ipv6 ospf 1 location 1!--- Enables OSPFv3 on the interface and also associates the interface looback10 to location 1.!interchallenge Loopback20 no ip address ipv6 resolve 2020::/64 eui-64 ipv6 ospf 1 location 2!--- Associates the Interconfront loopback20 to location 2.!interchallenge Serial0/0 no ip attend to ipv6 attend to 2001::1/124 ipv6 ospf 1 area 0!--- Associates the Interface serial0/0 to area 0. clock rate 2000000!ipv6 router ospf 1 router-id 1.1.1.1!--- Rexternal R1 offers 1.1.1.1 as rexternal id. log-adjacency-changes!finish

Router R2 Rexternal R3

hostname R2!ipv6 cef!!!!ipv6 unicast-routing!!!interface Serial0/0 no ip address ipv6 resolve 2001::2/124 ipv6 ospf 1 location 0 clock price 2000000!!interconfront Serial0/1 no ip attend to ipv6 attend to 2002::1/124 ipv6 ospf 1 area 0 clock rate 2000000!!!ipv6 router ospf 1router-id 2.2.2.2log-adjacency-changes!finish

!hostname R3!ipv6 cef!ipv6 unicast-routing!interface Loopback10 no ip attend to ipv6 address 1010::/64 eui-64 ipv6 ospf 1 location 1!interface Loopback20 no ip resolve ipv6 resolve 2020::/64 eui-64 ipv6 ospf 1 location 2!interface Serial0/0 no ip deal with ipv6 deal with FE80::AB8 link-local ipv6 address 2002::2/124 ipv6 ospf 1 area 0 clock rate 2000000!ipv6 router ospf 1 router-id 3.3.3.3 log-adjacency-changes!finish

Verify

Verifying OSPF Configuration

Use this section to confirm that your configuration functions correctly.

In order to verify the OSPF has actually been configured appropriately, usage the present ipv6 course ospf command also in routers R1 and R3.

show ipv6 course ospf
Router R1

R1#show ipv6 course ospfIPv6 Routing Table - 10 entriesCodes: C - Connected, L - Local, S - Static, R - RIP, B - BGP U - Per-user Static path, M - MIPv6 I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interlocation, IS - ISIS summary O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2 ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2 D - EIGRP, EX - EIGRP externalOI 1010::C002:1DFF:FEE0:0/128 <110/128> using FE80::C001:1DFF:FEE0:0, Serial0/0O 2002::/124 <110/128> using FE80::C001:1DFF:FEE0:0, Serial0/0OI 2020::C002:1DFF:FEE0:0/128 <110/128> via FE80::C001:1DFF:FEE0:0, Serial0/0 Rexternal R3 R3#display ipv6 path ospfIPv6 Routing Table - 10 entriesCodes: C - Connected, L - Local, S - Static, R - RIP, B - BGP U - Per-user Static path, M - MIPv6 I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interlocation, IS - ISIS summary O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2 ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2 D - EIGRP, EX - EIGRP externalO 2001::/124 <110/128> by means of FE80::C001:1DFF:FEE0:0, Serial0/0OI 2010::C000:1DFF:FEE0:0/128 <110/128> by means of FE80::C001:1DFF:FEE0:0, Serial0/0OI 2020::C000:1DFF:FEE0:0/128 <110/128> using FE80::C001:1DFF:FEE0:0, Serial0/0

Verifying Link-Local Address Reachability

The routers have the right to ping each various other with the worldwide uniactors attend to. However, as soon as making use of link-neighborhood attend to only the straight connected netfunctions have the right to communicate. For instance, R1 have the right to ping R3 utilizing worldwide uniactors deal with yet the 2 routers cannot communicate utilizing link-neighborhood addresses. This is displayed using the ping and also debug ipv6 icmp commands in rexternal R1 and R3. This section provides scenarios to construct a better knowledge about link-regional addresses.

Pinging Link-Local Address From Remote Network

When the router R1 tries to interact through router R3 using the attach regional attend to, the router R1 returns via an ICMP time-out message indicating that the link-neighborhood attend to is locally particular and cannot interact to link-regional addresses that are exterior the directly associated network-related.

Pinging R3"s Link-Local Address from rexternal R1
In Router R1

R1#ping FE80::AB8!--- Pinging Link-Local Address of rexternal R3.Output Interface: serial0/0!--- To ping LLA, output interconfront must be entered.Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to FE80::AB8, timeout is 2 seconds:Packet sent through a resource address of FE80::C000:1DFF:FEE0:0.....Success price is 0 percent (0/5)!--- The ping is uneffective and also the ICMP packet cannot reach the destination via serial0/0.!--- This timeout suggests that R1 has not got any kind of replies from the rexternal R3.

Pinging Link-Local Address From Directly Connected Network

For router R2, the routers R1 and R3 are directly associated and deserve to ping the link-regional deal with of both router R1 and also R2 by stating the equivalent interconfront that is associated to the router. The output is displayed here:

Pinging R1 Link-Local Addresses from rexternal R2
In Rexternal R2 Pinging R3 Link-Local Addresses from rexternal R2
In Rexternal R2

The link-regional attend to as the name means, is specific just to that neighborhood netjob-related. In other words, the routers deserve to have the exact same link-local resolve and also still the directly connected network-related deserve to interact with each various other without any type of dispute. This will not be the exact same in instance of international unicast attend to. The international unicast deal with being routable must be distinctive in a netjob-related. The show ipv6 interchallenge brief command reflects the information around link-neighborhood resolve on the interchallenge.

display ipv6 interchallenge brief
In rexternal R1

R1#present ipv6 interconfront briefSerial0/0 FE80::AB8 2001::1Loopback10 FE80::C000:1DFF:FEE0:0 2010::C000:1DFF:FEE0:0Loopback20 FE80::C000:1DFF:FEE0:0 2020::C000:1DFF:FEE0:0 In router R3 R3#display ipv6 interface briefSerial0/0 FE80::AB8 2002::2Loopback10 FE80::C002:1DFF:FEE0:0 1010::C002:1DFF:FEE0:0Loopback20 FE80::C002:1DFF:FEE0:0 2020::C002:1DFF:FEE0:0!--- Shows that R1 and also R3"s serial interconfront has very same link-regional attend to FE80::AB8.

In this example, R1 and R3 are assigned with the same link-local deal with and R2 have the right to still reach both the routers by specifying the matching output interconfront.

See more: Flow In Cities Skylines How To Change Road Direction Of One, How Do I Convert Or Upgrade Roads

Pinging R1 and R3"s Link-regional deal with from R2
Pinging R1"s link-neighborhood address from R2

Note:The R2 deserve to ping the link-regional resolve of R1 and also R3 just bereason they are straight associated. R2 cannot ping the link-local attend to of the loopearlier interdeals with in routers R1 and also R3 as they are not directly linked. Ping works on link-local addresses only in situation of directly linked networks.

Note:Tracepaths perform not job-related in instance of link-local addresses and also rerevolve with the % No valid resource address for location. error message. This is bereason IPv6 routers should not forward packets that have actually link-local resource or destination addresses to other links.