Hey,
Yes we thought about that too (actually that was my first idea), but this might lead to inconsitency as not all hosts will get an update when a node moves but only those nodes which are on the way. Furthermore the packet reading (and cache updating) increases latency to forwarding. A solution might be to increase the rate in which batman-packets are sent (because then host announcement goes with them), or create a new packet type for announcement and send these more often. Both brings us much more noise in the mesh. I wonder if having a wifi-mesh is good for (hard?) real-time applications. Even reassociating to a new access point might take a few seconds (scanning & finding), or there is packet loss if you get out of the range from the previous ap until your wifi card changes to another AP.
Regards Simon
On Fri, Sep 14, 2007 at 03:11:35PM +0800, 唐鼎 wrote:
hi! but 1 second delay is too long to some real-time applications. i have look insight the batman-adv code. caching source host's mac and originater's mac when batman node forwards a packet maybe is better way