commits September 2019

commits@lists.open-mesh.org

1 participants
279 discussions

[doc] backup-redmine/2019-09-14, master: doc: batman-adv/Extended-isolation (f26f264)
by postmaster＠open-mesh.org 15 Sep '19

15 Sep '19

1 0

[doc] backup-redmine/2019-09-14, master: doc: batman-adv/Broadcast (4a4bd87)
by postmaster＠open-mesh.org 15 Sep '19

15 Sep '19

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2019-09-14,master >--------------------------------------------------------------- commit 4a4bd87e411c0ebe9a98239a091415c1a7bf3b6e Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Fri May 3 23:47:39 2019 +0000 doc: batman-adv/Broadcast >--------------------------------------------------------------- 4a4bd87e411c0ebe9a98239a091415c1a7bf3b6e batman-adv/Broadcast.textile | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/batman-adv/Broadcast.textile b/batman-adv/Broadcast.textile index edec10e..2d2299b 100644 --- a/batman-adv/Broadcast.textile +++ b/batman-adv/Broadcast.textile @@ -1,8 +1,7 @@ h1. Broadcasts in B.A.T.M.A.N. Advanced - -!broadcast.png! __A node broadcasting through the mesh__ +!broadcast.png! Broadcasting is a method in computer networks to distribute a packet to all available nodes. batman-adv supports broadcast via its __classic flooding__ algorithm.

1 0

[doc] backup-redmine/2019-09-14, master: doc: batman-adv/Broadcast (e3deb26)
by postmaster＠open-mesh.org 15 Sep '19

15 Sep '19

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2019-09-14,master >--------------------------------------------------------------- commit e3deb26ae6f7b634d0baf33be588b24d5584d6fb Author: Linus Lüssing <linus.luessing(a)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.

1 0

[doc] backup-redmine/2019-09-14, master: doc: batman-adv/Broadcast (04bb1a1)
by postmaster＠open-mesh.org 15 Sep '19

15 Sep '19

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2019-09-14,master >--------------------------------------------------------------- commit 04bb1a155e11e89aba825167343e77361fb37e2b Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Tue May 7 09:50:34 2019 +0000 doc: batman-adv/Broadcast >--------------------------------------------------------------- 04bb1a155e11e89aba825167343e77361fb37e2b batman-adv/Broadcast.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/Broadcast.textile b/batman-adv/Broadcast.textile index 5871c6d..d853b26 100644 --- a/batman-adv/Broadcast.textile +++ b/batman-adv/Broadcast.textile @@ -54,7 +54,7 @@ h3. I.III) Single Neighbor: Is Previous Sender _A node avoiding to echo back to its forwarder_ -* If an interface has just one neighbor and it matches the originator that forwarded this OGM2 or broadcast packet to us, then no broadcast is necessary. +* If an interface has just one neighbor and it matches the originator that forwarded this broadcast packet to us, then no broadcast is necessary. We can avoid echoing a packet back to the originator node (not just neighor) it was forwarded from.

1 0

[doc] backup-redmine/2019-09-14, master: doc: batman-adv/broadcast.png (c303940)
by postmaster＠open-mesh.org 15 Sep '19

15 Sep '19

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2019-09-14,master >--------------------------------------------------------------- commit c3039400ccc638cc4ea4e82d49c8801f90e018a8 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Fri May 3 21:16:33 2019 +0000 doc: batman-adv/broadcast.png >--------------------------------------------------------------- c3039400ccc638cc4ea4e82d49c8801f90e018a8 batman-adv/broadcast.png | Bin 0 -> 8197 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/batman-adv/broadcast.png b/batman-adv/broadcast.png new file mode 100644 index 0000000..bdeb9dc Binary files /dev/null and b/batman-adv/broadcast.png differ

1 0

[doc] backup-redmine/2019-09-14, master: doc: batman-adv/Network-wide-multi-link-optimization: don't reference deprecated debugfs files (417730d)
by postmaster＠open-mesh.org 15 Sep '19

15 Sep '19

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2019-09-14,master >--------------------------------------------------------------- commit 417730d13615310d256d8f6b073a369100597b26 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sun Mar 3 18:22:19 2019 +0000 doc: batman-adv/Network-wide-multi-link-optimization: don't reference deprecated debugfs files >--------------------------------------------------------------- 417730d13615310d256d8f6b073a369100597b26 .../Network-wide-multi-link-optimization.textile | 25 +--------------------- 1 file changed, 1 insertion(+), 24 deletions(-) diff --git a/batman-adv/Network-wide-multi-link-optimization.textile b/batman-adv/Network-wide-multi-link-optimization.textile index e15f59e..4ada8fb 100644 --- a/batman-adv/Network-wide-multi-link-optimization.textile +++ b/batman-adv/Network-wide-multi-link-optimization.textile @@ -78,7 +78,7 @@ h2. Debug information There is an implementation based on the description above currently pending for review. It offers some debugging facilities: -The default originator table can be found at its original place, using ''batctl o'' or the debugfs file /sys/kernel/debug/batman_adv/bat0/originators. The following examples represents the topology shown in the top of the page, debug information obtained on node B, using OpenWRT and virtual machines: +The default originator table can be found at its original place, using ''batctl o''. The following examples represents the topology shown in the top of the page, debug information obtained on node B, using OpenWRT and virtual machines: <pre> root@OpenWrt:/# batctl o @@ -92,29 +92,6 @@ fe:f0:00:00:04:01 0.520s (234) fe:f1:00:00:03:01 [ eth1]: fe:f1:00:00: fe:f0:00:00:01:01 0.920s (255) fe:f1:00:00:01:01 [ eth1]: fe:f1:00:00:01:01 (255) fe:f0:00:00:01:01 (254) </pre> -The individual tables per interface can be found in the respective folders which have been added as part of this patchset: - -<pre> -root@OpenWrt:/# cat /sys/kernel/debug/batman_adv/eth0/originators -[B.A.T.M.A.N. adv master-b82b9b2, IF/MAC: eth0/fe:f0:00:00:02:01 (bat0 BATMAN_IV)] - Originator last-seen (#/255) Nexthop [outgoingIF]: Potential nexthops ... -fe:f1:00:00:03:01 0.170s (255) fe:f1:00:00:03:01 [ eth1]: fe:f1:00:00:03:01 (255) -fe:f1:00:00:01:01 0.510s (253) fe:f1:00:00:01:01 [ eth1]: fe:f1:00:00:01:01 (253) -fe:f0:00:00:05:01 0.660s (222) fe:f1:00:00:03:01 [ eth1]: fe:f0:00:00:03:01 (198) fe:f1:00:00:03:01 (222) -fe:f0:00:00:03:01 0.560s (252) fe:f1:00:00:03:01 [ eth1]: fe:f1:00:00:03:01 (252) fe:f0:00:00:03:01 (240) -fe:f0:00:00:04:01 0.250s (240) fe:f1:00:00:03:01 [ eth1]: fe:f1:00:00:03:01 (240) fe:f0:00:00:03:01 (211) -fe:f0:00:00:01:01 0.850s (255) fe:f1:00:00:01:01 [ eth1]: fe:f1:00:00:01:01 (255) fe:f0:00:00:01:01 (238) -root@OpenWrt:/# cat /sys/kernel/debug/batman_adv/eth1/originators -[B.A.T.M.A.N. adv master-b82b9b2, IF/MAC: eth1/fe:f1:00:00:02:01 (bat0 BATMAN_IV)] - Originator last-seen (#/255) Nexthop [outgoingIF]: Potential nexthops ... -fe:f1:00:00:03:01 0.880s (240) fe:f1:00:00:03:01 [ eth1]: fe:f1:00:00:03:01 (240) -fe:f1:00:00:01:01 0.250s (239) fe:f1:00:00:01:01 [ eth1]: fe:f1:00:00:01:01 (239) -fe:f0:00:00:05:01 0.340s (211) fe:f1:00:00:03:01 [ eth1]: fe:f0:00:00:03:01 (210) fe:f1:00:00:03:01 (211) -fe:f0:00:00:03:01 0.260s (253) fe:f0:00:00:03:01 [ eth0]: fe:f1:00:00:03:01 (240) fe:f0:00:00:03:01 (253) -fe:f0:00:00:04:01 0.010s (225) fe:f0:00:00:03:01 [ eth0]: fe:f1:00:00:03:01 (224) fe:f0:00:00:03:01 (225) -fe:f0:00:00:01:01 0.510s (255) fe:f0:00:00:01:01 [ eth0]: fe:f1:00:00:01:01 (240) fe:f0:00:00:01:01 (255) -</pre> - Comparing to the original topology, it shows that for destination E (fe:f0:00:00:05:01) when packets come in on 2.4 GHz (eth0, first table), they are preferably forwarded to C (fe:f1:00:00:03:01 ) on 5 GHz (eth1). When packets are received on 5 GHz (eth1), there is not much difference because at node B or at node C, the same interface must be used. Therefore in the second table for node E (fe:f0:00:00:05:01) the two choices have pretty much the same TQ values (210 and 211).

1 0

[doc] backup-redmine/2019-09-14, master: doc: batman-adv/Broadcast (6201460)
by postmaster＠open-mesh.org 15 Sep '19

15 Sep '19

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2019-09-14,master >--------------------------------------------------------------- commit 62014609c4ed6c00273259539a064e9d34b5ef4d Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Fri May 3 23:34:34 2019 +0000 doc: batman-adv/Broadcast >--------------------------------------------------------------- 62014609c4ed6c00273259539a064e9d34b5ef4d batman-adv/Broadcast.textile | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/batman-adv/Broadcast.textile b/batman-adv/Broadcast.textile index 62107cb..3733a63 100644 --- a/batman-adv/Broadcast.textile +++ b/batman-adv/Broadcast.textile @@ -14,12 +14,14 @@ To avoid frames looping around forever (a broadcast storm) an originating batman 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). +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. 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. +Last but not least 802.11 broadcasts are usually performed at the lowest Wifi bitrate. If a high broadcast throughput is needed, it is therefore usually recommended to increase the Wifi rate for multicast transmissions in the wifi driver. + h2. Gateway Feature: DHCP Optimizations todo

1 0

[doc] backup-redmine/2019-09-14, master: doc: batman-adv/Broadcast (80d94bc)
by postmaster＠open-mesh.org 15 Sep '19

15 Sep '19

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2019-09-14,master >--------------------------------------------------------------- commit 80d94bc24a5153deb86289c574956b777e0f4aa9 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Tue May 7 09:49:48 2019 +0000 doc: batman-adv/Broadcast >--------------------------------------------------------------- 80d94bc24a5153deb86289c574956b777e0f4aa9 batman-adv/Broadcast.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/Broadcast.textile b/batman-adv/Broadcast.textile index 920de22..5871c6d 100644 --- a/batman-adv/Broadcast.textile +++ b/batman-adv/Broadcast.textile @@ -44,7 +44,7 @@ h3. I.II) Single Neighbor: Is Originator _Three nodes with a single neighbor per interface each_ -* If an interface has just one neighbor and it matches the OGM2 or broadcast packets originator address, then no broadcast is necessary. +* If an interface has just one neighbor and it matches the broadcast packet's originator address, then no broadcast is necessary. We can avoid echoing a packet back to the node it originally came from.

1 0

[doc] backup-redmine/2019-09-14, master: doc: batman-adv/Noflood-broadcast-prevention (541095e)
by postmaster＠open-mesh.org 15 Sep '19

15 Sep '19

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2019-09-14,master >--------------------------------------------------------------- commit 541095e78966f6da47905bccb616f77979b8096a Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Sat May 4 04:08:46 2019 +0000 doc: batman-adv/Noflood-broadcast-prevention >--------------------------------------------------------------- 541095e78966f6da47905bccb616f77979b8096a batman-adv/Noflood-broadcast-prevention.textile | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/batman-adv/Noflood-broadcast-prevention.textile b/batman-adv/Noflood-broadcast-prevention.textile index 8ccdccd..fb5bff7 100644 --- a/batman-adv/Noflood-broadcast-prevention.textile +++ b/batman-adv/Noflood-broadcast-prevention.textile @@ -49,3 +49,12 @@ The first ebtables command makes sure that link-local IPv6 multicast is never ma The second ebtables rule marks any IPv6 multicast frame which is not a link-local one. For instance multicast packets with a global destination scope. batman-adv will then drop such multicast packets with a global destination scope if for example it is unable to distribute it via individual unicast transmissions and would fall back to broadcast flooding. + +h2. Crucial Multicast + +Here is a list of packet types which utilize multicast and which are essential to establish IP communication. Unless you know exactly what you are doing you usually should __not__ set a noflood-mark on such packets. + +* __ARP:__ IPv4 address resolution +* __DHCP:__ IPv4/IPv6 address assignment +* __ICMPv6:__ esp. IPv6 address resolution (but many more) +* __IGMP:__ multicast listener announcements \ No newline at end of file

1 0

[doc] backup-redmine/2019-09-14, master: doc: batman-adv/Noflood-broadcast-prevention (e32f796)
by postmaster＠open-mesh.org 15 Sep '19

15 Sep '19

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2019-09-14,master >--------------------------------------------------------------- commit e32f796cd4a803f45b4fd8ea2125f8c7db764c0c Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Sat May 4 03:55:41 2019 +0000 doc: batman-adv/Noflood-broadcast-prevention >--------------------------------------------------------------- e32f796cd4a803f45b4fd8ea2125f8c7db764c0c batman-adv/Noflood-broadcast-prevention.textile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/batman-adv/Noflood-broadcast-prevention.textile b/batman-adv/Noflood-broadcast-prevention.textile index 4ca7744..8ccdccd 100644 --- a/batman-adv/Noflood-broadcast-prevention.textile +++ b/batman-adv/Noflood-broadcast-prevention.textile @@ -35,10 +35,10 @@ __Preventing flooding of routeable IPv6 multicast:__ <pre> $ batctl noflood_mark 0x4/0x4 # VALUE/MASK $ ebtables -A FORWARD --logical-in br0 -o bat0 \ - -p IPv6 --ip6-dst ff02::/64 \ + -p IPv6 --ip6-dst ff02::/ff0f:: \ -j ACCEPT $ ebtables -A FORWARD --logical-in br0 -o bat0 \ - -p IPv6 --ip6-dst ! ff02::/64 \ + -p IPv6 --ip6-dst ! ff02::/ff0f:: \ -j mark --set-mark 0x4 --mark-target ACCEPT </pre>

1 0

← Newer
1
...
10
11
12
13
14
15
16
...
28
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits September 2019