Date: Sun, 13 Nov 2016 00:51:53 -0500 From: Zaphod Beeblebrox <zbeeble@gmail.com> To: FreeBSD Net <freebsd-net@freebsd.org> Subject: quagga misinterpreting route. Message-ID: <CACpH0MemfJqFVZxc4Rg_qbzcqgM5fRjojxKeoD4wTAY9KBOu6g@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
I have an if-up mpd5 rule that says: route -n6 add $route -iface $interface where $route is something like 1001:abcd:1::/64 and $interface is something like ng2. When I go into quagga, I see: my.router.ca# sh ipv6 route 1001:abcd:1::1 Routing entry for 1001:abcd:1::/64 Known via "kernel", distance 0, metric 0, tag 0, vrf 0, best, fib >* fe80::212:3fff:fe41:72fd, via bge0 ... now there's two things wrong with this. It's not a kernel route and it's not via bge0. This leads the ospf6 advertisement of this route to be: my.router.ca# sh ipv6 ospf6 route 1001:abcd:1::1 Destination: ::/0 Destination type: Network Installed Time: 00:13:29 ago Changed Time: 00:13:29 ago Lock: 2 Flags: BA-- Memory: prev: 0x0 this: 0x7026f0 next: 0x704dd0 Associated Area: 0.0.0.0 Path Type: External-1 LS Origin: AS-External Id: 0.0.0.0 Adv: 1.2.3.4 Options: --|-|-|--|-|-- Router Bits: -------- Prefix Options: xxx Metric Type: 1 Metric: 20 (0) Nexthop: fe80::21a:64ff:fe79:3348 bge0.401 ... which leads other ospf6 routers on the network to not see the route at all (invalid?)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACpH0MemfJqFVZxc4Rg_qbzcqgM5fRjojxKeoD4wTAY9KBOu6g>