Hi all, incidentally I noticed that with the modification that introduced the 'NOT_BEST_NEXT_HOP' flag only OGM coming from best next hop neighbour are forwarded in case of multi-hop originators.
The problem is that in the routing code it is forwarded only the first OGM received with a fresh sequence number (that could be received from a sub-optimal router).
This means that if the OGM from best next hop neighbour is not received as the first OGM, it is not forwarded and I think this can be a problem.
Maybe it can be better to maintain also an index of the last FORWARDED sequence number instead of checking the last RECEIVED sequence number.
Regards
-- Daniele Furlan
Hi,
incidentally I noticed that with the modification that introduced the 'NOT_BEST_NEXT_HOP' flag only OGM coming from best next hop neighbour are forwarded in case of multi-hop originators.
The problem is that in the routing code it is forwarded only the first OGM received with a fresh sequence number (that could be received from a sub-optimal router).
This means that if the OGM from best next hop neighbour is not received as the first OGM, it is not forwarded and I think this can be a problem.
Maybe it can be better to maintain also an index of the last FORWARDED sequence number instead of checking the last RECEIVED sequence number.
do you mind sending a patch for this ? That would make it easier to understand what you have in mind.
Regards, Marek
b.a.t.m.a.n@lists.open-mesh.org
-
Daniele Furlan -
Marek Lindner