You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cannot ping to link-local ipv6 interface address of the switch. (sonic-net#774)
* Cannot ping to link-local ipv6 interface address of the switch.
Fixes:
1. Packets destined to the switch's routing interface link-local ipv6 address
are not coming to CPU. Hence the ping fails.
Since all interfaces have the same link-local ipv6 address, all we need is
a single ip2me /128 route corresponding to this address added in the hardware.
We don't need fe80 ip2me route added to hardware for every interface. Hence the
address overlap issue won't arise for the link-local interface address.
2. Fixed another issue as part of this PR.
Where the link-local ipv6 neighbors are not learned via netlink by neighsync.
As a result, we could not add an ipv6 route via link-local nexthop.
Allow neighsync to learn the link-local neighbors too.
Signed-off-by: [email protected]
* Incremental change to the code changes.
* Incremental change to the code changes.
* Incorporated review comments.
* Incorporated review comments.
* Add fe80::/10 route to CPU to forward all locally destined link-local ipv6 packets to CPU.
* Retain fe80.../128 ip2me route in the hardware along with fe80::/10 subnet route.
Signed-off-by: Kiran Kella <[email protected]>
0 commit comments