LISTSERV mailing list manager LISTSERV 16.0

Help for MICE-DISCUSS Archives


MICE-DISCUSS Archives

MICE-DISCUSS Archives


MICE-DISCUSS@LISTS.IPHOUSE.NET


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

MICE-DISCUSS Home

MICE-DISCUSS Home

MICE-DISCUSS  December 2017

MICE-DISCUSS December 2017

Subject:

Re: Attribute Length Error today

From:

Jeremy Lumby <[log in to unmask]>

Reply-To:

MICE Discuss <[log in to unmask]>

Date:

Fri, 8 Dec 2017 18:13:00 -0600

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (188 lines)

The route servers are dropping it, however I wonder if the error is being generated in the process of dropping it.

-----Original Message-----
From: MICE Discuss [mailto:[log in to unmask]] On Behalf Of Andrew Hoyos
Sent: Friday, December 08, 2017 6:03 PM
To: [log in to unmask]
Subject: Re: [MICE-DISCUSS] Attribute Length Error today

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.

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.

And yes, "set-bgp-prepend=0” on the inbound filter on the session is the correct way to handle a similar behavior to ‘no bgp enforce first-as’ in Tik world. This causes the MICE ASN to be removed from the AS Path.

--
Andrew Hoyos
[log in to unmask]



> On Dec 8, 2017, at 5:55 PM, Darin Steffl <[log in to unmask]> wrote:
> 
> It's possible it was sending default earlier and our consultant fixed it when he logged in between 1:27pm and 1:45pm. If someone wants to verify, that'd be great.
> 
> On Fri, Dec 8, 2017 at 5:48 PM, Jeremy Lumby <[log in to unmask]> wrote:
> I do not know much about how Mikrotik works.  I agree that the filters do not look like you are sending default, I was just seeing it from Andy's post. 
> 
>  
> 
> From: MICE Discuss [mailto:[log in to unmask]] On Behalf Of Darin Steffl
> Sent: Friday, December 08, 2017 5:39 PM
> 
> 
> To: [log in to unmask]
> Subject: Re: [MICE-DISCUSS] Attribute Length Error today
> 
>  
> 
> Looking at route filters right now and that I attached, I don't see that I'm advertising a default route unless I'm looking in the wrong spot. I did not setup any portion of the BGP as I know I'm not an expert or comfortable setting it up, thus why I hired a consultant to do it for me. They're a big Mikrotik consultant from Missouri. 
> 
>  
> 
> I only see us advertising 204.73.77.0/24, 162.255.252.0/22 in our route filters right now that I sent.
> 
>  
> 
>  
> 
>  
> 
> On Fri, Dec 8, 2017 at 5:29 PM, Jeremy Lumby <[log in to unmask]> wrote:
> 
> In looking at it, do you happen to know why you were sending a default route?  Has that been corrected?
> 
>  
> 
> From: MICE Discuss [mailto:[log in to unmask]] On Behalf Of Darin Steffl
> Sent: Friday, December 08, 2017 5:16 PM
> To: [log in to unmask]
> Subject: Re: [MICE-DISCUSS] Attribute Length Error today
> 
>  
> 
> Hey all,
> 
>  
> 
> I sent the following to my Mikrotik consultant who set this up for me and his response is below. Anyone familiar with Mikrotik that knows the easy way to do this? We have MICE filters setup but not sure the correct way to do this without messing anything up further. He had the route filters out of order in our Mikrotik which is why I wasn't seeing MICE traffic. Once he fixed that, we're now receiving 500+ mbps from MICE and its stable on our end. But if we're still sending incorrect route announcements, I want to fix that so I don't cause issues. I found two related forum posts on how to change this in my router but I have a couple MICE filters as shown in the attachment. Thanks
> 
>  
> 
> My cell is 507-261-7690
> 
>  
> 
>  
> 
> My email to consultant:
> 
> Under the technical page of their website http://micemn.net/technical.html I see the following note "Note that your BGP sessions to the route servers likely need no bgp enforce-first-as or similar. The route servers do not add the MICE AS to the AS path." A quick search of Mikrotik forums shows that the equivalent to this setting is to "set-bgp-prepend=0" for the MICE peer. I'm not sure of this so want clarification to see if we need to make this change in order for traffic to start going through MICE.
> 
> https://forum.mikrotik.com/viewtopic.php?t=55798
> 
> https://forum.mikrotik.com/viewtopic.php?t=43498
> 
>  
> 
>  
> 
> Consultant response:
> 
> Your MICE connection should have had traffic assuming that you were advertising your prefixes to them.  Their BGP session should not add their AS, so that should not matter.  You should not need to change that, I would have to look to see why you are not seeing traffic.
> 
>  
> 
>  
> 
> On Fri, Dec 8, 2017 at 4:55 PM, Andy Koch <[log in to unmask]> wrote:
> 
> On 08 December 2017 at 16:15:59, Justin Krejci wrote:
> > Yup
> >
> >
> > Dec  8 13:41:40.262 CST: %BGP-3-NOTIFICATION: sent to neighbor 206.108.255.1 3/11 (invalid or corrupt AS path) 3 bytes 400200
> > Dec  8 13:41:40.262 CST: BGP: 206.108.255.1 Bad attributes FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 002D 0200 0000 0E40 0101 0040 0200 4003 04CE 6CFF 5918 CC49 4D16 A2FF E8
> 
> 
> >From this UPDATE dump, this parser helps quite a bit to decode what is
> going on:  http://bgpaste.convergence.cx/
> 
> Looks like the AS_PATH was 0 bytes long, which is invalid and Frank's
> router did the only thing it knows to do on BGP errors - drop the session.
> 
> Further from the decode:
> The NEXT_HOP was 206.108.255.89
> And the Routes were 204.73.77.0/24, 162.255.252.0/22 and 0.0.0.0/0
> 
> Looks like Minnesota WiFi should check on their route announcements.
> 
> HTH,
> Andy
> 
> 
> 
> 
>  
> 
> --
> 
> Darin Steffl
> 
> Minnesota WiFi
> 
> www.mnwifi.com
> 
> 507-634-WiFi
> 
>  Like us on Facebook
> 
>  
> 
> To unsubscribe from the MICE-DISCUSS list, click the following link:
> http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
> 
>  
> 
> To unsubscribe from the MICE-DISCUSS list, click the following link:
> http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
> 
> 
> 
> 
>  
> 
> --
> 
> Darin Steffl
> 
> Minnesota WiFi
> 
> www.mnwifi.com
> 
> 507-634-WiFi
> 
>  Like us on Facebook
> 
>  
> 
> To unsubscribe from the MICE-DISCUSS list, click the following link:
> http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
> 
> 
> To unsubscribe from the MICE-DISCUSS list, click the following link:
> http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
> 
> 
> 
> 
> -- 
> Darin Steffl
> Minnesota WiFi
> www.mnwifi.com
> 507-634-WiFi
>  Like us on Facebook
> 
> To unsubscribe from the MICE-DISCUSS list, click the following link:
> http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
> 

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010

ATOM RSS1 RSS2



LISTS.IPHOUSE.NET

CataList Email List Search Powered by the LISTSERV Email List Manager