Hi Olivier, I just couldn't think of anything else (except changing frr with bird). You are absolutely right about the panic (as well as for the zebra daemon crash). This should not happen, regardles the wrong configuration. The system is still working as expected (no traffic going in or out, as it is a test system, but zebrad has not crashed so far). Tomorrow I will check again with the original image and report back . Regards,
Lyubomir On Mon, 8 Apr 2019 at 17:52, Olivier Cochard-Labbé <oliv...@cochard.me> wrote: > On Mon, Apr 8, 2019 at 3:37 PM Lyubomir Yotov <l.yo...@gmail.com> wrote: > >> I actually found an error in the AS number (last digit was missing). >> So far (more than an hour) it seems fine. As it has happened before that >> it could crash after several hours I will wait until tomorrow. >> If everything is fine I will try again with a fresh install (on another >> flash drive) to check if the wrong config was the problem. >> Just for the record here is the "show version" from the installed frr6: >> router.bsdrp.net#show version >> FRRouting 6.0.2 (router.bsdrp.net). >> >> > Hi, > Like you've seen, the binary version is stil 6.0.2, because the port > revision "2" didn't modified the binary: > - frr6.0.2_1 : It was just an update of an RC script, so no change into > FRR binaries > - frr6.0.2_2 : It was just a typo in RC script's comment > So I don't think the resolution came from this upgrade. > > But in any case, even if the panic came from the wrong AS number: it > should have not triggered a panic. > > Regards, > > Olivier > _______________________________________________ > Bsdrp-users mailing list > Bsdrp-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bsdrp-users >
_______________________________________________ Bsdrp-users mailing list Bsdrp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bsdrp-users
