| Description | This article explains the use of IPv6 link-local address (of BGP neighbor for example) in an IPv6 network. |
| Scope | IPv6, FortiGate. |
| Solution |
The remote device redistributes the connected network (loopback network 2402:800:6a00:24::100/64) to the local FortiGate, assuming that BGP was enabled on both IPv4 and IPv6 at its neighbor 2402:800:6a00:27::303 and 10.211.244.81.
The local FortiGate also has both neighbors 2402:800:6a00:27::301 and 10.211.244.82 activated BGP on IPv4 and IPv6.
The above results showed that FortiGate learned the network 2402:800:6a00:24::100/64 with the next-hop 2402:800:6a00:27::301 from both neighbors, but neighbor 10.211.244.82 only advertised the IPv6 global address, while the neighbor 2402:800:6a00:27::301 advertised both global and link-local IPv6 address.
As a result, next-hop shows the global address instead of the link-local address in the routing table, because the route with a higher weight was chosen:
As a result, next-hop shows the global address instead of the link-local address in the routing table:
|
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2026 Fortinet, Inc. All Rights Reserved.