[quagga-users 14517] Re: quagga 1.1 seems to have completely broken ospf6

I have a custom version that I built using the 418805 revision of the port
and the quagga-1.0.20161017 revision of the tarball.  The current version
of the port won't patch the older tarball.

That said, 1.0.20161017 works for ipv6 (although ospf6d has a tendency to
crash every so often) and 1.1.0 is broken.

On Mon, Nov 14, 2016 at 10:26 AM, jan hugo prins <[email protected]> wrote:

> I noticed the same issues.
> After upgrading one of my BGP routers I got blackholes in my IPv6 OSPF
> core.
> I'm using 0.99.24.1 in my core network and the router I upgraded was
> upgraded to version 1.1.
> After downgrading the router again everything was fixed.
>
> Jan Hugo
>
>
>
> On 11/13/2016 05:29 PM, Zaphod Beeblebrox wrote:
>
> I posted on FreeBSD-net last night how quagga 1.1 doesn't appear to be
> picking up ipv6 routes correctly.  It attributes them to the wrong
> interface.  This may be part of this problem.
>
> I have a linux router running ospf, ospf6 and zebra.  It's running
> 0.99.23.1-1+deb8u.  It's an border router between the main LAN and it's own
> guests.  sh ipv6 ospf6 route gives expected output as does sh ipv6 ospf6
> nei.
>
> The FreeBSD BGP router (running quagga-1.1.0_1) shows expected neighbour
> output, but shows no ospf6 routes ... not even it's own interfaces and
> static routes.  oddly, the ospf6 database is populated.
>
> Help?
>
>
> _______________________________________________
> Quagga-users mailing listQuagga-users-UOy77sIEA+cAd7ICUelF/YSV3M38o/[email protected]://lists.quagga.net/mailman/listinfo/quagga-users
>
>
>
> _______________________________________________
> Quagga-users mailing list
> Quagga-users-UOy77sIEA+cAd7ICUelF/[email protected]
> https://lists.quagga.net/mailman/listinfo/quagga-users
>
>

_______________________________________________
Quagga-users mailing list
Quagga-users-UOy77sIEA+cAd7ICUelF/[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-users