On Wed, Feb 19, 2014 at 11:30:36PM +0100, Antonio Quartulli wrote: > On 19/02/14 23:12, whangarei & opua wrote: > > Hi Antonio, > > > > have only a live environment, so only have access to my own router, but > > anyway, > > looks you aware of this issue... > > > > But I have seen no change of the TQ over the time ( up to 180 sec) on my > > side with my (maybe old) version of batman. > > Is it an new feature, or it is maybe not working like expected, in my > > old version? :( > > > > I think this is something that is part of batman-adv since the beginning > (somebody else can confirm this).
The routing protocol is known to have problems when a node suddenly disappears. A received OGM is what triggers updates to the metric. If you stop receiving OGMs the metric is no longer updated until the node is purged as dead. This for example causes problems with nomadic/mobile nodes. They can go around a corner, loss line of sight, but still be considered the best route until purged as dead. This design problem will be fixed with the BATMAN V. It has a second protocol which is used between one hop peers and should quickly detect if a peer has disappeared. Andrew
