On Oct 27, 10:46, Sean Donelan <SEAN@SDG.DRA.COM> wrote:
still listening to, and re-announcing the route? Was it the old cisco bug, where routes sometimes get stuck in the route table due to dropping the withdrawl?
Yes. The leak (through 1800) was fixed rather quickly, but the routes stuck. The fact that many (most?) of them were more specific routes made the whole thing as "eventful" as it was; normally, selection by path length means that leaks like that don't have any particular effect. Hence, you actually had three things go wrong at the same time: 1) Wrong filtering. 2) More specific routes. 3) The routes stuck after withdrawal. -- ------ ___ --- Per G. Bilse, Director Network Eng & Ops ----- / / / __ ___ _/_ ---- EUnet Communications Services B.V. ---- /--- / / / / /__/ / ----- Singel 540, 1017 AZ Amsterdam, NL --- /___ /__/ / / /__ / ------ tel: +31 20 5305333, fax: +31 20 6224657 --- ------- 24hr emergency number: +31 20 421 0865 --- Connecting Europe since AS286 --- http://www.EU.net e-mail: bilse at domain