frr
frr copied to clipboard
FRRouting
EVPN Support for IPv6 underlay
The Linux kernel supports IPv6 underlay for VXLAN tunnels. It would be nice if EVPN also supported using a v6 underlay (v6 next-hops for EVPN prefixes).
Ran into this limitation while deploying green field. Pretty important feature and supported by every major vendor.
https://news-blogs.cisco.com/datacenter/vxlanv6-vxlanv-what https://eos.arista.com/eos-4-24-1f/ipv6-underlay-support-for-vxlan-with-evpn-control-plane/ https://apps.juniper.net/feature-explorer/feature-info.html?fKey=7914&fn=EVPN-VXLAN%20support%20for%20VXLAN%20Gateways%20using%20an%20IPv6%20underlay
+1 for this.
It's going to affect a lot of products out there that rely on it (including big-label products) and prevent IPv6 being used as the transport.
It seems you can configure IPv6 VTEPs, and BGP works between them, but the routes which get distributed seem to point next hop addresses to the router-id, which is tied to IPv4, thus not allowing the various EVPN route types to be exchanged back and forth.
there still is no support for this feature. it needs to be added by a developer
+1 for this feature. There are significant benefits to being able to run underlay infrastructure as IPv6-only, especially in larger environments where neither rfc1918 nor public IPv4 scale well. It's also simpler to be able to move an underlay to be IPv6-only rather than needing to keep it dual-stacked.
Since IPv4 address exhaustion, IPv4 became obsolete since new organizations, ISPs, data centers are unable to obtain new IPv4 address to take part of internet. IPv6 is the internet standard and IPv4 should be treated as a legacy backward compatibility mode.
Since FRRouting is all about the present and the future, all functionalities shall support IPv6. +1 for this feature.
IPv6 being used as underlay will scale much better than IPv4!
+1 for this feature.
Today IPv6 is the standard Internet protocol, so it's a shame not to have it as an underlay. +1 for this feature
I don't think it's a shame, but if we can use IPv6 as underlay will be usefull.
Besides, Proxmox is using FRR to create VXLAN and EVPN, and because IPv4 exhaustion, use IPv6 will helpfull to connect multiple datacenters.
I also think it's necessary to have IPv6 support for this functionality.
I was able to get an intermediate without IPv4 transport running, used IPv4 with IPv6 nexthop IETF Draft and it worked ok, but still had to use IPv4 for the VTEP endpoints and ipv4-unicast enabled in BGP, not IPv6 natively all round.
This issue has been lodged for 3 yrs now, surely there would have been some movement at the ranch by now. I'd put something together but my code would need more editing than would be useful by someone with the skills doing it from scratch.
Really? Nothing going on here besides a bunch of people crying for this feature (myself included)? :smile:
As with all things open source. Someone needs to step up and do the work..... If you are using FRR through one of it's vendors I would suggest putting pressure on them that way to get the functionality