-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cumulus_NVUE: Add gateway support #1782
base: dev
Are you sure you want to change the base?
Conversation
wait: 30 | ||
wait_msg: Waiting for RA message to generate the default route | ||
nodes: [ h1, h2 ] | ||
plugin: default6() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Issue here is multiple default routes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that's always the issue with multiple IPv6 routers attached to the same subnet. I wrote about that 11 years ago: https://blog.ipspace.net/2014/02/first-hop-load-balancing-in-ipv6/
5655cfa
to
a55cbf8
Compare
* Anycast ipv4 (ipv6 also configured if provided, module officially only supports ipv4) * VRRPv3 ipv4 and ipv6 * Comment out ipv6 addresses in VRRP test case (requires OSPFv3 which Cumulus NVUE does not support) * Add VRRP ipv6 test case (issue with multiple ipv6 default routes popping up)
… reach hosts via R2 (ECMP)
583d740
to
5c385f5
Compare
Anycast ipv4 (ipv6 also configured if provided, module officially only supports ipv4)
VRRPv3 ipv4 and ipv6, with preempt and priority
Comment out ipv6 addresses in anycast test case (requires OSPFv3 which Cumulus NVUE does not support, and anycast is only supposed to support ipv4 according to the documentation)
Add VRRP ipv6 test case (issue with multiple ipv6 default routes popping up)
Update documentation
Validation:
Ping test fails on occasion, I suspect due to having multiple ipv6 default routes with different next hops. Also tested EOS;
same issue
I would suggest to consider this after the new release; the changes are incremental and shouldn't break any existing functionality, but the VRRP v6 validation test needs more work