On Mon, 28 Aug 2017 at 22:10, Mark Kamichoff <p...@prolixium.com> wrote:

> On Mon, Aug 28, 2017 at 02:52:24PM +0200, Kurt Jaeger wrote:
> > On FreeBSD (and maybe somewhere else) there's this bug in 1.2.1
> > of quagga:
> >
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214481
> >
> > https://bugzilla.quagga.net/show_bug.cgi?id=870
> >
> > So maybe use 1.1.1 to stay away from that bug.
> >
> > > I understand for existing users of Quagga they might have a choice
> > > either to stay with Quagga or move on to FRR.
> >
> > At least on FreeBSD, net/frr is a port and therefore, switching
> > between quagga and free looks pretty straigtforward.
> >
> > I don't know if the problem above is fixed in FRR (which is a fork
> > of quagga, as far as I know).


This would be closed soon. Working on this. Would try to address this at
the earliest

Thanks
  Balaji

>
>
> I'm the reporter of bug ID 870.  From my personal experience, FRR does
> not suffer from this problem.  It was also discussed on the FRR dev
> mailing list earlier this year:
>
> https://lists.frrouting.org/pipermail/dev/2017-March/000498.html
>
> - Mark
>
> --
> Mark Kamichoff
> p...@prolixium.com
> https://www.prolixium.com/
> _______________________________________________
> Quagga-users mailing list
> Quagga-users@lists.quagga.net
> https://lists.quagga.net/mailman/listinfo/quagga-users
>
_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-users

Reply via email to