Bugzilla – Bug 1052
olsr::RoutingProtocol::LinkTupleUpdated incorrect detection of asymetric link with multiple interface nodes
Last modified: 2011-02-16 14:21:01 EST
olsr::RoutingProtocol::LinkTupleUpdated considers a link to a neighbor asymetric if any link to the neighbor is asymetric. However, it should consider the neighbor symetric if there is at least one symjetric link to it. The current code works as expected only when not using multiple interfaces.
RFC 3626 sect. 8.1:
If the neighbor has any associated link tuple which
indicates a symmetric link (i.e., with L_SYM_time >=
current time), then
N_status is set to SYM
else N_status is set to NOT_SYM
This problem was reported in .
Created attachment 1035 [details]
I didn't test it per se, but will this do?
(In reply to comment #1)
> Created attachment 1035 [details]
> I didn't test it per se, but will this do?
Yes, it sounds like it fixes the problem. And at least doesn't seem to break any regression tests. Feel free to commit.
user: Lalith Suresh <firstname.lastname@example.org>
date: Wed Feb 16 19:09:58 2011 +0000
summary: Bug 1052 - olsr::RoutingProtocol::LinkTupleUpdated incorrect detection of asymmetric link with multiple interface node