On Tue, Apr 24, 2018 at 10:38:03AM +0000, Arvin Gan wrote:
Hi All,
I notice that BGP can support RFC 5549 using configuration "ext_next_hop", bird can sync with kernel table using netlink assuming kernel support route with IPV4 DIP and IPV6 next hop. ... that mean if bird received IPV4 NLRI with IPV6 next hop, the gateway is parsed with IPV4 address since address family is IPV4 unicast on this case, does my understand correct ? If yes, this parse process have a bug ?
Hi BIRD does not support mixed next hops on netlink. It would be simple to implement that, but i think that Linux kernel does not (yet) support such routes anyway. At least i failed to setup such routes using 'ip' tool. Could you (or anybody) get such routes to work in Linux? -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."