Problem at AS6218 perhaps ? (of course if this is the result of some random corruption that can't be relied on... )
Anyone else see anything ?
Dave Curado wrote:
Another note on this, I wasn't able to stop the updates with a filter-list... perhaps because the AS path is problematic. I had to use a distribute list instead, listing each of the networks that 6218 is aggregating for...
Yeah. Had that same problem when talking with one of my upstreams...
Not sure if this affects anyone else or not, but:
access-list 21 deny 206.53.128.0 0.0.3.255 access-list 21 deny 206.53.128.0 0.0.0.255 access-list 21 deny 206.53.129.0 0.0.0.255 access-list 21 deny 206.53.130.0 0.0.0.255 access-list 21 deny 206.53.131.0 0.0.0.255 access-list 21 deny 206.148.144.0 0.0.3.255 access-list 21 deny 206.190.224.0 0.0.0.255 access-list 21 permit any
You're missing 207.142/20 and 207.142.32/19 from that list. At least.. they were being aggregated by 6218 earlier tonight from my vantage point. Regards, Andrew -- Andrew Bangs, Network Engineering Manager, Demon Internet Ltd andrewb@demon.net http://www.demon.net/ http://www.demon.nl/ Network Engineering: +44 (0)181 371 1204 networks@demon.net