[Bug 214481] [ports][net/quagga] ipv6 routes fail in quagga

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214481

            Bug ID: 214481
           Summary: [ports][net/quagga] ipv6 routes fail in quagga
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: mat at FreeBSD.org
          Reporter: dgilbert at eicat.ca
          Assignee: mat at FreeBSD.org
             Flags: maintainer-feedback?(mat at FreeBSD.org)

After upgrading to 10.3p12 and messing about a bit, I found something else
strange.  On another mpd router, the ipv6 route was showing up as being on an
unused port (bce1, in this case).  I have the port connected to the switch (so
it's up) but I'm not using it.  So... I ifconfig'd down bce0.  Then, quagga
claims:

my.other.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 lo0

... which is somewhat ridiculous.



On Sun, Nov 13, 2016 at 12:51 AM, Zaphod Beeblebrox <zbeeble at gmail.com> wrote:

    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?)

-- 
You are receiving this mail because:
You are the assignee for the bug.