Re: Long BGP AS paths

2017-10-02 Thread Tim Evens
Yikes, my bad. In the CSV file it didn't seem so large. I setup a dashboard where you can browse the longest as paths for the selected time period. check out demo-rv.snas.io:3000/dashboard/db/top-as-paths?orgId=2 [3]. Change the time range to see those longer paths. They are no longer current in

Re: Long BGP AS paths

2017-10-01 Thread Tim Evens
Looks like attachments do not work in the mailer. See below, a bit ugly, but it's CSV so you should be able to cut/paste it to check it out. timestamp,as_path_length,as_path 2017-09-29 22:26:40.00,568, 2518 2914 174 262206 262206 262197 262197 262197 262197 262197 262197 262197 262197

Re: Long BGP AS paths

2017-10-01 Thread Scott Weeks
> Nowhere in the BGP RFCs it says it is okay for the > software to crash. :: we could send a community to signal that it's ok :: to crash Call it the ECB. (Evil Crash Bit). ;-) scott

Re: Long BGP AS paths

2017-10-01 Thread Randy Bush
> Nowhere in the BGP RFCs it says it is okay for the software to crash. we could send a community to signal that it's ok to crash randy

Re: Long BGP AS paths

2017-10-01 Thread William Herrin
On Sun, Oct 1, 2017 at 1:06 PM, Kelly Dowd wrote: > On Sun, Oct 1, 2017 at 12:29 AM, William Herrin 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

Re: Long BGP AS paths

2017-10-01 Thread Tim Evens
The outliers are >100. Based on several peering points, <= 60 should be fine. See attached CSV file that shows the top 120 distinct AS Paths seen for the past month. Looks like 55644 likes to prepend a lot which is pushing the length above 50. --Tim On 01.10.2017 09:16, marcel.duregards---

Re: Long BGP AS paths

2017-10-01 Thread Jon Lewis
On Sun, 1 Oct 2017, sth...@nethelp.no wrote: Could you list which prefix(es) you saw were being announced with these long AS paths? 186.177.184.0/23 - still being announced with 533 occurrences of 262197 in the AS path. aut-num: AS262197 owner: MILLICOM CABLE COSTA RICA S.A.

Re: Long BGP AS paths

2017-10-01 Thread sthaug
> Could you list which prefix(es) you saw were being announced with these > long AS paths? 186.177.184.0/23 - still being announced with 533 occurrences of 262197 in the AS path. Steinar Haug, Nethelp consulting, sth...@nethelp.no

Re: Long BGP AS paths

2017-10-01 Thread Mark Price
Hi Bill, Could you list which prefix(es) you saw were being announced with these long AS paths? Mark On Sat, Sep 30, 2017 at 6:29 PM, William Herrin wrote: > To the chucklehead who started announcing a 2200+ byte AS path yesterday > around 18:27 EDT, I beg of you: STOP.

Re: Long BGP AS paths

2017-10-01 Thread marcel.duregards--- via NANOG
What would be a recommended value for a maximum as-path filter ? 50 ? On the DFZ I've only 11 prefixes longer than 30 as-path, so for safety I would also assume 50 as a max is well enough. Any advice ? Regards, - Marcel On 01.10.2017 00:29, William Herrin wrote: > To the chucklehead who

Re: Long BGP AS paths

2017-09-30 Thread William Herrin
On Sat, Sep 30, 2017 at 6:34 PM, Ken Chase wrote: > The quagga thread I read specifically indicates that some (most?) versions > don't > accept the {n,m} regexp repeat format. Thus the regexps as long as the > path you want to filter... :/ > Howdy, If it was configured with

Re: Long BGP AS paths

2017-09-30 Thread Job Snijders
On Sat, 30 Sep 2017 at 15:33, William Herrin 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 >

Re: Long BGP AS paths

2017-09-30 Thread Ken Chase
The quagga thread I read specifically indicates that some (most?) versions don't accept the {n,m} regexp repeat format. Thus the regexps as long as the path you want to filter... :/ ..or upgrade. /kc On Sat, Sep 30, 2017 at 06:29:36PM -0400, William Herrin said: >To the chucklehead who