On 08 December 2017 at 16:15:59, Justin Krejci wrote:
> Dec 8 13:41:40.262 CST: %BGP-3-NOTIFICATION: sent to neighbor 184.108.40.206 3/11 (invalid or corrupt AS path) 3 bytes 400200
> Dec 8 13:41:40.262 CST: BGP: 220.127.116.11 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 18.104.22.168
And the Routes were 22.214.171.124/24, 126.96.36.199/22 and 0.0.0.0/0
Looks like Minnesota WiFi should check on their route announcements.