Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2019-09-14,master
commit 7231bb5f5e3457478d5b38f04dc697f32455366f Author: Linus Lüssing linus.luessing@c0d3.blue Date: Fri May 3 23:09:23 2019 +0000
doc: batman-adv/Broadcast
7231bb5f5e3457478d5b38f04dc697f32455366f batman-adv/Broadcast.textile | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/batman-adv/Broadcast.textile b/batman-adv/Broadcast.textile index 8277cae..62107cb 100644 --- a/batman-adv/Broadcast.textile +++ b/batman-adv/Broadcast.textile @@ -12,11 +12,14 @@ The basic algorithm used by batman-adv is __classic flooding__. Here every node
To avoid frames looping around forever (a broadcast storm) an originating batman-adv node tags the frame with a sequence number which increases with every new broadcast frame this node transmits. The sequence number allows other nodes to detect whether it received a frame before. Such duplicates will then simply be ignored.
- h2. Interface Type: WiFi vs. Others
In 802.11 based wireless networks broadcast transmissions have one specific downside compared to unicast: While for unicast transmissions a missing frame is detected and retransmitted ("ARQ":https://en.wikipedia.org/wiki/Automatic_repeat_request).
+To compensate for that batman-adv (re-)broadcasts a frame on a wireless interface not just once but three times when classic flooding is used. + +Furthermore, for the second and third broadcast a delay of 5ms is applied for each to increase the probability that one of the broadcasts arrives. + h2. Gateway Feature: DHCP Optimizations
todo