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 <(507)%20261-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
