[196073] in North American Network Operators' Group
Re: AS PATH limits
daemon@ATHENA.MIT.EDU (Ken Chase)
Sun Oct 1 04:12:52 2017
X-Original-To: nanog@nanog.org
Date: Sun, 1 Oct 2017 01:05:46 -0400
From: Ken Chase <math@sizone.org>
To: Christopher Morrow <morrowc.lists@gmail.com>
In-Reply-To: <CAL9jLaZ2Rso4bjLAFA7Y7GKg=akSwD3Ahcr00k=Zffr-sTuxeQ@mail.gmail.com>
Cc: nanog list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
I don't quite understand the exact situation that causes the issue - our
cogent facing router (quagga .99.22 debian) was receiving the route but that
session stayed up - it was it while sending or the other igp router (also
quagga .99.22) receiving (I think the latter) that was crashing their session.
Not quite sure why the cogent session didn't crash as well (or first, before
propagating the bad route).
At any rate, we should likely take this discussion to the quagga-users-l
/kc
On Sat, Sep 30, 2017 at 09:28:28PM -0400, Christopher Morrow said:
>ii quagga 0.99.22.4-3ubu i386 BGP/OSPF/RIP routing
>daemon
>
>interestingly enough that isn't crashlooping nor is it bouncing bgp
>sessions:
>192.168.100.100 4 MYASN 1642717 8864 0 0 0 2d23h32m
>672475
>
>and it's happily showing me the route even...
--
Ken Chase - math@sizone.org Guelph Canada
