Ondrej Zajicek <santiago@crfreenet.org> writes:
On Mon, Apr 30, 2018 at 05:15:19PM +0200, Toke Høiland-Jørgensen wrote:
When a Babel node restarts, it loses its sequence number, which can cause its routes to be rejected by peers until the state is cleared out by other nodes in the network (which can take on the order of minutes).
There are two ways to fix this: Having stable storage to keep the sequence number across restarts, or picking a different router ID each time.
This implements the latter, by introducing a new option that will cause Bird to pick a random router ID every time it starts up. This avoids the problem at the cost of not having stable router IDs in the network.
Merged with some minor changes (option renamed to 'randomize router id', no router ID change when changed during reconfiguration).
Also note that when tested on my VM test setup, all router IDs were generated with the same value due to way how random() is initialized in BIRD. Fixed that with a further commit.
Great, thanks! :) -Toke