- mice-discuss - lists.micemn.net

Please Welcome SW MN Broadband to MICE!

by Jason Hanke

Name: Southwest MN Broadband Port: xe-0/0/12 (NP Remote) ASN: 25715 IPv4: 206.108.255.40/24 IPv6: 2001:504:27:0:0:6473::1/64 Peering Contact: support(a)mysmbs.com Route Server: Yes BFD: No Welcome aboard! -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

Dec. 13, 2017

Re: Attribute Length Error today

by Frank Bulk

Here’s a tweet to the list that Jay is referring to: https://twitter.com/JobSnijders/status/939280110607327232 Frank From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jason Hanke Sent: Saturday, December 9, 2017 7:01 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Attribute Length Error today it's time for secure route servers. Job sent out a list of ixp and quite a few of them are already doing rpki or irr filtering. On Dec 8, 2017 11:06 PM, "Richard Laager" <rlaager(a)wiktel.com<mailto:rlaager@wiktel.com>> wrote: Zero length is a subset of “doesn’t start with their AS”, so if we filter on that condition, hopefully we will catch that too. -- Richard > On Dec 8, 2017, at 23:04, Frank Bulk <fbulk(a)MYPREMIERONLINE.COM<mailto:fbulk@MYPREMIERONLINE.COM>> wrote: > > If the issue was that the AS PATH was zero length, can BIRD filter those out? > > Frank > > -----Original Message----- > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>] On Behalf Of Doug McIntyre > Sent: Friday, December 8, 2017 6:15 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> > Subject: Re: [MICE-DISCUSS] Attribute Length Error today > >> On Fri, Dec 08, 2017 at 06:03:21PM -0600, Andrew Hoyos wrote: >> The more important question - why didn’t the route servers drop that? I’d assume there should be inbound filters to drop bogons+default+$otherbadstuff. > > They do have filters for bogons + default route. > > I suspect bad AS attribute processing is part of what made it get leaked onwards. > The BIRD servers were logging that as well during this period. > >> On a larger scale, this sort of thing begs the question - do we need to have folks in some sort of isolated VLAN with test sessions to the route servers upon turnup? SIX does this, as well as others, I suspect to prevent these exact issues from happening. > > Possibly. > > > -- > Doug McIntyre <merlyn(a)iphouse.net<mailto:merlyn@iphouse.net>> > ~.~ ipHouse ~.~ > Network Engineer/Provisioning/Jack of all Trades > ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Dec. 12, 2017

Re: Super Bowl Change Freeze

by DeLong, Owen

If you aren’t yet peering with Akamai and would like to before this event starts streaming, please get your peering requests in to us soon. Don’t count on a route-server session to cover this. It is greatly preferable to peer directly with our router. Details are in peeringdb and we encourage you to peer both IPv4 and IPv6. Owen > On Dec 11, 2017, at 16:19 , Richard Laager <rlaager(a)WIKTEL.COM> wrote: > > As you have probably heard, the Super Bowl is being held in Minneapolis > on February 4. We discussed at UG 26 that it would be a good idea to > institute a change freeze for a few days to a week before. > > If you need to upgrade your port capacity or make other changes at MICE, > please plan to have those *complete* by January 26th. > > If it were me, I wouldn't even cut it that close. > > -- > Richard

Dec. 12, 2017

Super Bowl Change Freeze

by Richard Laager

As you have probably heard, the Super Bowl is being held in Minneapolis on February 4. We discussed at UG 26 that it would be a good idea to institute a change freeze for a few days to a week before. If you need to upgrade your port capacity or make other changes at MICE, please plan to have those *complete* by January 26th. If it were me, I wouldn't even cut it that close. -- Richard

Dec. 12, 2017

Re: Passive BFD support on Route-Server #1

by Doug McIntyre

On Mon, Dec 04, 2017 at 03:12:28PM -0600, Doug McIntyre wrote: >Just to close this project out, I'll set a schedule to get this done. > >On Monday, 12/11/2017 at 12:30AM, I'll turn on passive BFD on the MICE route >server #1 (206.108.255.1/ 2001:504:27::d1af:0:1) for all connections. This was completed. No complications as far as I can see. I'll let this config run for a week and schedule up the other route server. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Dec. 11, 2017

Re: Attribute Length Error today

by Andrew Hoyos

On Dec 9, 2017, at 7:00 PM, Jason Hanke <jayhanke(a)NEUTRALPATH.NET> wrote: > > it's time for secure route servers. Job sent out a list of ixp and quite a few of them are already doing rpki or irr filtering. I second this. IXPmanager makes this easy. > >> On Dec 8, 2017 11:06 PM, "Richard Laager" <rlaager(a)wiktel.com> wrote: >> Zero length is a subset of “doesn’t start with their AS”, so if we filter on that condition, hopefully we will catch that too. >> >> -- >> Richard >> >> > On Dec 8, 2017, at 23:04, Frank Bulk <fbulk(a)MYPREMIERONLINE.COM> wrote: >> > >> > If the issue was that the AS PATH was zero length, can BIRD filter those out? >> > >> > Frank >> > >> > -----Original Message----- >> > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug McIntyre >> > Sent: Friday, December 8, 2017 6:15 PM >> > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET >> > Subject: Re: [MICE-DISCUSS] Attribute Length Error today >> > >> >> On Fri, Dec 08, 2017 at 06:03:21PM -0600, Andrew Hoyos wrote: >> >> The more important question - why didn’t the route servers drop that? I’d assume there should be inbound filters to drop bogons+default+$otherbadstuff. >> > >> > They do have filters for bogons + default route. >> > >> > I suspect bad AS attribute processing is part of what made it get leaked onwards. >> > The BIRD servers were logging that as well during this period. >> > >> >> On a larger scale, this sort of thing begs the question - do we need to have folks in some sort of isolated VLAN with test sessions to the route servers upon turnup? SIX does this, as well as others, I suspect to prevent these exact issues from happening. >> > >> > Possibly. >> > >> > >> > -- >> > Doug McIntyre <merlyn(a)iphouse.net> >> > ~.~ ipHouse ~.~ >> > Network Engineer/Provisioning/Jack of all Trades >> > > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Dec. 10, 2017

Re: Attribute Length Error today

by Jason Hanke

it's time for secure route servers. Job sent out a list of ixp and quite a few of them are already doing rpki or irr filtering. On Dec 8, 2017 11:06 PM, "Richard Laager" <rlaager(a)wiktel.com> wrote: > Zero length is a subset of “doesn’t start with their AS”, so if we filter > on that condition, hopefully we will catch that too. > > -- > Richard > > > On Dec 8, 2017, at 23:04, Frank Bulk <fbulk(a)MYPREMIERONLINE.COM> wrote: > > > > If the issue was that the AS PATH was zero length, can BIRD filter those > out? > > > > Frank > > > > -----Original Message----- > > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of > Doug McIntyre > > Sent: Friday, December 8, 2017 6:15 PM > > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > > Subject: Re: [MICE-DISCUSS] Attribute Length Error today > > > >> On Fri, Dec 08, 2017 at 06:03:21PM -0600, Andrew Hoyos wrote: > >> The more important question - why didn’t the route servers drop that? > I’d assume there should be inbound filters to drop > bogons+default+$otherbadstuff. > > > > They do have filters for bogons + default route. > > > > I suspect bad AS attribute processing is part of what made it get leaked > onwards. > > The BIRD servers were logging that as well during this period. > > > >> On a larger scale, this sort of thing begs the question - do we need to > have folks in some sort of isolated VLAN with test sessions to the route > servers upon turnup? SIX does this, as well as others, I suspect to prevent > these exact issues from happening. > > > > Possibly. > > > > > > -- > > Doug McIntyre <merlyn(a)iphouse.net> > > ~.~ ipHouse ~.~ > > Network Engineer/Provisioning/Jack of all Trades > > >

Dec. 10, 2017

Re: Attribute Length Error today

by Richard Laager

Zero length is a subset of “doesn’t start with their AS”, so if we filter on that condition, hopefully we will catch that too. -- Richard > On Dec 8, 2017, at 23:04, Frank Bulk <fbulk(a)MYPREMIERONLINE.COM> wrote: > > If the issue was that the AS PATH was zero length, can BIRD filter those out? > > Frank > > -----Original Message----- > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug McIntyre > Sent: Friday, December 8, 2017 6:15 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: Re: [MICE-DISCUSS] Attribute Length Error today > >> On Fri, Dec 08, 2017 at 06:03:21PM -0600, Andrew Hoyos wrote: >> The more important question - why didn’t the route servers drop that? I’d assume there should be inbound filters to drop bogons+default+$otherbadstuff. > > They do have filters for bogons + default route. > > I suspect bad AS attribute processing is part of what made it get leaked onwards. > The BIRD servers were logging that as well during this period. > >> On a larger scale, this sort of thing begs the question - do we need to have folks in some sort of isolated VLAN with test sessions to the route servers upon turnup? SIX does this, as well as others, I suspect to prevent these exact issues from happening. > > Possibly. > > > -- > Doug McIntyre <merlyn(a)iphouse.net> > ~.~ ipHouse ~.~ > Network Engineer/Provisioning/Jack of all Trades >

Dec. 9, 2017

Re: Attribute Length Error today

by Frank Bulk

If the issue was that the AS PATH was zero length, can BIRD filter those out? Frank -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug McIntyre Sent: Friday, December 8, 2017 6:15 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Attribute Length Error today On Fri, Dec 08, 2017 at 06:03:21PM -0600, Andrew Hoyos wrote: >The more important question - why didn’t the route servers drop that? I’d assume there should be inbound filters to drop bogons+default+$otherbadstuff. They do have filters for bogons + default route. I suspect bad AS attribute processing is part of what made it get leaked onwards. The BIRD servers were logging that as well during this period. >On a larger scale, this sort of thing begs the question - do we need to have folks in some sort of isolated VLAN with test sessions to the route servers upon turnup? SIX does this, as well as others, I suspect to prevent these exact issues from happening. Possibly. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Dec. 9, 2017

Re: Attribute Length Error today

by Andrew Hoyos

> On Dec 8, 2017, at 6:14 PM, Doug McIntyre <merlyn(a)IPHOUSE.NET> wrote: > > On Fri, Dec 08, 2017 at 06:03:21PM -0600, Andrew Hoyos wrote: >> The more important question - why didn’t the route servers drop that? I’d assume there should be inbound filters to drop bogons+default+$otherbadstuff. > > They do have filters for bogons + default route. Cool. > I suspect bad AS attribute processing is part of what made it get leaked onwards. > The BIRD servers were logging that as well during this period. Gotcha, while extra work, would it be easy enough to add first hop AS path filters on sessions on the route servers? Or do these already exist as well? Without testing, I’m not sure if that even would have prevented this specific scenario, but it seems like one we should prevent in the future, somehow. -- Andrew Hoyos hoyosa(a)gmail.com

Dec. 9, 2017