RE: Small full BGP table capable router with low power consumption

2017-12-22 Thread Adam Greene
Hey Steve (or anyone else), How much RAM are you running on your 4431? We have a similar application and are trying to figure out whether to order a 4431 with the default 4GB RAM, or upgrade it proactively to 8GB to support the full BGP table. Thanks, Adam -Original Message- From: NAN

Re: AS PATH limits

2017-12-22 Thread Ken Chase
And again this morn at 08:35:19 EST (13:35 UTC). I dont have access to the router that fed us the long route, so I cant tell what it was (since we never consumed it before barfing). Let's hope for no more over holiday season... /kc On Fri, Oct 13, 2017 at 05:02:42PM -0400, Ken Chase said: > I

Re: AS PATH limits

2017-12-22 Thread Nick Hilliard
What router software version are you running that barfs on long as-paths? Nick Ken Chase wrote: > And again this morn at 08:35:19 EST (13:35 UTC). I dont have access to the > router that fed us the long route, so I cant tell what it was (since we never > consumed it before barfing). > > Let's ho

Re: AS PATH limits

2017-12-22 Thread Ken Chase
quagga 0.99.22.4, yes i need to upgrade, as my other router on 0.99.23.1 seems ok. now coordinating with customers to get it upgraded is a different issue. /kc On Fri, Dec 22, 2017 at 05:40:28PM +, Nick Hilliard said: >What router software version are you running that barfs on long as-path

Weekly Routing Table Report

2017-12-22 Thread Routing Analysis Role Account
This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG, CaribNOG TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG, IRNOG and the RIPE Routing WG. Daily listings are sen

Re: AS PATH limits

2017-12-22 Thread Mike Tancsa
On 12/22/2017 12:46 PM, Ken Chase wrote: > quagga 0.99.22.4, yes i need to upgrade, as my other > router on 0.99.23.1 seems ok. now coordinating with > customers to get it upgraded is a different issue. Will that version of quagga not support a filter list? e.g neighbor 38.xx.yy.zz filter-list ma

Re: AS PATH limits

2017-12-22 Thread William Herrin
On Fri, Dec 22, 2017 at 12:40 PM, Nick Hilliard wrote: > What router software version are you running that barfs on long as-paths? > Hi Nick, Versions of quagga up until the very most recent release corrupt the transmission of routes with very long AS paths. They add up the packet length wrong.

Re: AS PATH limits

2017-12-22 Thread Nick Hilliard
William Herrin wrote: > The AS path lengths we're talking about are unreasonable. "unreasonable" is a peculiar word to use here :-) It's the internet and you can't expect other people not to do silly things from time to time. This is a known problem and it isn't even the first time it's been dis

Re: AS PATH limits

2017-12-22 Thread Nick Hilliard
Ken Chase wrote: > quagga 0.99.22.4, yes i need to upgrade, as my other > router on 0.99.23.1 seems ok. All unpatched versions of quagga between 0.99.2 and 1.2.2 are affected. Nick

Re: AS PATH limits

2017-12-22 Thread William Herrin
On Fri, Dec 22, 2017 at 5:45 PM, Nick Hilliard wrote: > William Herrin wrote: > > The AS path lengths we're talking about are unreasonable. > > "unreasonable" is a peculiar word to use here :-) > > It's the internet and you can't expect other people not to do silly > things from time to time. Th

Re: AS PATH limits

2017-12-22 Thread Scott Weeks
--- b...@herrin.us wrote: From: William Herrin Well, that's a brilliant platitude, but what do you do when it breaks over and over until the other guy upgrades? --- Filter that network out of your tables until it's fixed? :) scott

Re: AS PATH limits

2017-12-22 Thread Ken Chase
Push harder on upgrading. "Dec 30" is my earliest window I got from my customer after previously pushing with previous events (didnt help that Cogent said "yeah we agree these are silly, we'll be filtering more aggressively" -- this time it snuck in from the less busy side of our network). It's no

Re: AS PATH limits

2017-12-22 Thread Nick Hilliard
William Herrin wrote: > On Fri, Dec 22, 2017 at 5:45 PM, Nick Hilliard wrote: > If you've been hit with a known service-affecting problem that can > easily recur without warning and which will be service affecting if it > hits again, common sense suggests that it would be a good idea t

Re: Waste will kill ipv6 too

2017-12-22 Thread Jima
On 2017-12-21 08:58, Christopher Morrow wrote: On Thu, Dec 21, 2017 at 10:16 AM, Jason Iannone wrote: M&A plays into this too. By my calculations, CenturyLink controls at least 17 million /48s. How many sites does CenturyLink provide service to? I'm gonna go out on a limb and say it's not 1

Re: AS PATH limits

2017-12-22 Thread Ken Chase
Ive found some other stuff that's totally busted, but screw those who havent patched their systems. We should not help them at all as knowlegeable stewards of big chunks of bandwidth, we should just write stuff about how silly they are instead: https://www.usenix.org/system/files/conference/woot1

Re: AS PATH limits

2017-12-22 Thread William Herrin
On Fri, Dec 22, 2017 at 5:57 PM, Scott Weeks wrote: > Well, that's a brilliant platitude, but what do you do > when it breaks over and over until the other guy upgrades? > --- > > > Filter that network out of your tables until it's fixed? :) Good

Re: AS PATH limits

2017-12-22 Thread Nick Hilliard
Ken Chase wrote: > (And I'd fix it _right now_, but it's at my major customer's > discretion. ok, so this is a customer management problem. If this is the only customer on that router, then ok, if they want to continue putting themselves at risk of service loss, I guess that would be their concer