Date: Sat, 2 Jun 2018 08:23:37 +0200 From: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= <olivier@freebsd.org> To: Mike Tancsa <mike@sentex.net> Cc: FreeBSD Ports ML <freebsd-ports@freebsd.org> Subject: Re: net/frr 4.0 crashing Message-ID: <CA%2Bq%2BTco03gJ=ZmoT3r%2BH76hoF59FyVr2FKXL75v%2BF9qKehuAHA@mail.gmail.com> In-Reply-To: <3fa47fe3-23ab-8358-4b52-8fee9a0a9b62@sentex.net> References: <3fa47fe3-23ab-8358-4b52-8fee9a0a9b62@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 30, 2018 at 9:05 PM Mike Tancsa <mike@sentex.net> wrote: > Hi, > On a recent RELENG_11 (r334152) I am no longer able to start up t= he > routing daemons. I get an Abort at the end. Anyone have any ideas what > this might be about ? > > =E2=80=8BHi, seems that FRR 4.0 crash if there are tun,gre,gif interfaces=E2=80=8B on Fr= eeBSD. https://github.com/FRRouting/frr/issues/1907 https://github.com/FRRouting/frr/issues/2338 I'm thinking of creating a net/frr3 (FRR version 3.0.3) and moving net/frr to net/frr4 for allowing FreeBSD users to revert back to FRR 3.0.3 meanwhile. Regards, Olivier
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2Bq%2BTco03gJ=ZmoT3r%2BH76hoF59FyVr2FKXL75v%2BF9qKehuAHA>