This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/routing-wg@ripe.net/
[routing-wg] New on RIPE Labs: BGP Zombies
- Previous message (by thread): [routing-wg] New on RIPE Labs: BGP Zombies
- Next message (by thread): [routing-wg] New on RIPE Labs: 768k Day. Will it Happen? Did it Happen?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Wed Apr 24 17:25:36 CEST 2019
>> but does not explain the cases where we see stuck routes on devices >> which have no config changes for a loooong time (if you believe >> rancid). > > Well, in the scenario above, R1 would have the config change, but *on > R1* the route would be gone. A downstream router R2 would have seen > the initial UPDATE, but never received a withdraw - so R2 would claim > "I have it, and I have it from R1!" while R1 would claim "no such > prefix". so, could we look for a router where emile et alia found a stuck route and we have the rancid for the upstreams? randy
- Previous message (by thread): [routing-wg] New on RIPE Labs: BGP Zombies
- Next message (by thread): [routing-wg] New on RIPE Labs: 768k Day. Will it Happen? Did it Happen?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]