Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
stale border router does not get replaced #12210
When playing around with border routers I noticed some strange behavior: An offline border router is retained for an unknown time. Even resetting a node does not get it to use the new border router as the old border router information is still being advertised by neighboring nodes.
I am not sure if this is to spec as the border router live time is indeed exceptionally high. But this seems more like a bug as it makes roaming nodes impossible. Even worse, a roaming node could 'pollute' other nodes with an unreachable border router, making them ignore a border router that is reachable.
I think the solution could be to check if a border router is reachable before considering border router information valid or to drop existing border router information if a 'fresh' border router becomes available.
This makes me wonder, is is possible to protect against rogue border routers?
Steps to reproduce the issue
The RIOT border Router should now announce it's prefix.
After some time, the new border router should be used as the old border router is not reachable anymore.
The old border router will be used for the next ~45 days
some more information:
I also tried with