Repository : ssh://git@open-mesh.org/doc

On branches: backup-redmine/2019-09-14,master

commit e3deb26ae6f7b634d0baf33be588b24d5584d6fb Author: Linus Lüssing linus.luessing@c0d3.blue Date: Sat May 4 00:32:30 2019 +0000

doc: batman-adv/Broadcast

e3deb26ae6f7b634d0baf33be588b24d5584d6fb batman-adv/Broadcast.textile | 3 +++ 1 file changed, 3 insertions(+)

diff --git a/batman-adv/Broadcast.textile b/batman-adv/Broadcast.textile index 1275f14..b6f93b1 100644 --- a/batman-adv/Broadcast.textile +++ b/batman-adv/Broadcast.textile @@ -13,6 +13,9 @@ To avoid frames looping around forever (a broadcast storm) an originating batman

h2. Interface Type: WiFi vs. Others

+__A broadcast frame transmitted three times__ +!bcast-3x.png! + 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) a broadcast transmission is performed only once, with no acknowledgements.

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.