Hoi,
On 3/30/24 19:24, Juliusz Chroboczek wrote:
Yes, it's legal, but discouraged. Please see RFC 9229 Section 2.1:
Thanks Juliusz, for confirming and for making the allowance in the RFC
in the first place.
Attached is a patch that optionally allows extended next hop to be set
for IPv4
> I don't think it's a violation of the Babel protocol to use IPv6 next hops
> when
> an IPv4 address is present.
Yes, it's legal, but discouraged. Please see RFC 9229 Section 2.1:
If the outgoing interface has been assigned an IPv4 address, then, in
the interest of maximising
Hoi folks,
By means of context, I am working on allowing VPP and Bird2/Babel to
program the routing table with IPv6 nexthops for IPv4 destinations.
I finished a few small code changes in VPP to allow transit-net-less
transport of IPv4 and IPv6 in VPP and wrote about it on
