> Certainly did and it upset a lot of RouterOS devices.
Really? Like that Cisco bug from 2009? Would a bgp-as-path-length
<https://wiki.mikrotik.com/wiki/Manual:Routing/Routing_filters> filter have
helped on these devices?
Also, just to make it clear, RFC4893 <https://tools.ietf.org/html/rfc4893>
reserves AS23456 to represent 4-byte ASNs on BGP speakers which don’t support
them.
I’m interested in why this AS path is being logged as it is:
Did someone decide to actually prepend that reserved ASN?
Does the device logging this path not support 4-byte ASNs?
Or is there a router somewhere stripping the NEW_AS_PATH attribute?
_______________________________________________
AusNOG mailing list
[email protected]
http://lists.ausnog.net/mailman/listinfo/ausnog
