[196063] in North American Network Operators' Group
Re: Long BGP AS paths
daemon@ATHENA.MIT.EDU (Job Snijders)
Sat Sep 30 19:02:51 2017
X-Original-To: nanog@nanog.org
In-Reply-To: <CAP-guGVE2J2ik7brqs=apDoKZA3mmJZLdfF5zk+BRbkLa+=png@mail.gmail.com>
From: Job Snijders <job@instituut.net>
Date: Sat, 30 Sep 2017 22:44:54 +0000
To: William Herrin <bill@herrin.us>, "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Sat, 30 Sep 2017 at 15:33, William Herrin <bill@herrin.us> wrote:
> To the chucklehead who started announcing a 2200+ byte AS path yesterday
> around 18:27 EDT, I beg of you: STOP. You've triggered a bug in Quagga
> that's present in all versions released in the last decade. Your
> announcement causes routers based on Quagga to send a malformed update to
> their neighbors, collapsing the entire BGP session. Every 30 seconds or so.
>
> For everyone else: please consider filtering BGP announcements with
> stupidly long AS paths.
Nowhere in the BGP RFCs it says it is okay for the software to crash. Bugs
happen. You patch and move on. :-)
>
