On Wed, Aug 21, 2019 at 02:35:13PM +0100, Tom Bird wrote: > Hi, > > I recently updated some virtual machine hosting nodes to Debian Buster from > Stretch, and I'm having an interesting problem with IPv6 kernel routes. My > example uses 1.6.6 but 1.6.7 shows the same behaviour, so I'm just wondering > what I am missing. v4 is all working as expected.
Hi It seems that it is related to adding routes using 'route' command instead of 'ip route' command. # ip r a 2001:db8:1:14::/64 via 2001:db8:1:1::14 # route -6 add 2001:db8:1:15::/64 gw 2001:db8:1:1::15 # ip r a 2001:db8:1:16::/64 via 2001:db8:1:1::16 metric 1 # ip -6 r l ... 2001:db8:1:14::/64 via 2001:db8:1:1::14 dev ve0 metric 1024 pref medium none 2001:db8:1:15::/64 via 2001:db8:1:1::15 dev ve0 metric 1 pref medium 2001:db8:1:16::/64 via 2001:db8:1:1::16 dev ve0 metric 1 pref medium ... bird> show route protocol kernel1 2001:db8:1:14::/64 via 2001:db8:1:1::14 on ve0 [kernel1 17:39:42] * (10) 2001:db8:1:16::/64 via 2001:db8:1:1::16 on ve0 [kernel1 17:42:50] * (10) Note the 'none' in route added by 'route' command. Perhaps such route has some strange attribute and that is why it is ignored by BIRD. > I tried a bird6.conf from a machine still running Debian Stretch, and that > also did not import the kernel routes. > > I've tried this on a test VM with bird 1.6.3 and kernel 4.9.0 and it imports > the routes as expected. Perhaps it may be difference in in kernel version? Different traslation of old route API calls? -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: [email protected]) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
