The binding table needs to be updated when something changes on the
network. i.e., when connected nodes and links go up or down. There is
no explicit mechanism to guarantee the order of such events, as it has
always been assumed that a link or node cannot come back up before
all its pertaining bind
Rune, Erik,
If my hypothesis is correct, this patch, on top of Erik's two previous ones,
should solve the problem we are seeing with dropped name table bindings.
I am not completely sure my theory is the right one, and even if it is, it may
not be the whole truth. I wonder if there might be some
-discussion@lists.sourceforge.net; Parthasarathy Bhuvaragan;
Ying Xue; Richard Alpe; erik.hu...@gmail.com
Subject: Re: [tipc-discussion] [PATCH net-next 1/1] tipc: guarantee order of
network events to binding table
Rune, Erik,
If my hypothesis is correct, this patch, on top of Erik's two previous