commits January 2023

commits@lists.open-mesh.org

1 participants
283 discussions

[doc] backup-redmine/2023-01-14,main: doc: batman-adv/Multicast-Packet-Type (536eaa0c)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 536eaa0c5147e3a4ed7bfac5cf6deb6b6d4bb7cf Author: Linus L��ssing <linus.luessing(a)c0d3.blue> Date: Mon Dec 26 15:06:13 2022 +0000 doc: batman-adv/Multicast-Packet-Type >--------------------------------------------------------------- 536eaa0c5147e3a4ed7bfac5cf6deb6b6d4bb7cf batman-adv/Multicast-Packet-Type.textile | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/batman-adv/Multicast-Packet-Type.textile b/batman-adv/Multicast-Packet-Type.textile index d48136c7..10dbd5f5 100644 --- a/batman-adv/Multicast-Packet-Type.textile +++ b/batman-adv/Multicast-Packet-Type.textile @@ -138,12 +138,16 @@ h3. -Fragmentation / MTUs:- -> Workaround C): We require a 1280 bytes MTU on all hard interfaces and only then set the multicast packet type capability flag. -h3. Adding a sequence number? / How to avoid loops with tracker marking later? +h3. -Adding a sequence number? / How to avoid loops with tracker marking later?- -When later implementing a split control <-> data plane as originally envisioned, by allowing to send a multicast packet with only the tracker TVLV, without data. And caching this information to fill a multicast routing table. And then allowing to send a multicast packet without the tracker TVLV afterwards, there is the following issue: +-When later implementing a split control <-> data plane as originally envisioned, by allowing to send a multicast packet with only the tracker TVLV, without data. And caching this information to fill a multicast routing table. And then allowing to send a multicast packet without the tracker TVLV afterwards, there is the following issue:- -When first a path is marked through the tracker TVLV, then paths change due to OGM updates. And then a tracker packet marks such new paths then the merger of both the old and newly tracker marked paths could create routing loops, as the old path is not automatically invalidated. +-When first a path is marked through the tracker TVLV, then paths change due to OGM updates. And then a tracker packet marks such new paths then the merger of both the old and newly tracker marked paths could create routing loops, as the old path is not automatically invalidated.- -Solution: +-Solution:- -Don't mark paths. Instead use the tracker TVLV to fill a cache with the mcast/dests lists and assign a hash to this information. Then later send the multicast data with a TVLV containing only this hash instead of the full mcast/dests list. Therefore a specific list of destinations is still maintained and routing decisions still happen on the go, loopfree, instead of trying to a maintain a loopfree, adjacent multicast routing table. \ No newline at end of file +-Don't mark paths. Instead use the tracker TVLV to fill a cache with the mcast/dests lists and assign a hash to this information. Then later send the multicast data with a TVLV containing only this hash instead of the full mcast/dests list. Therefore a specific list of destinations is still maintained and routing decisions still happen on the go, loopfree, instead of trying to a maintain a loopfree, adjacent multicast routing table.- + +--- + +-> Don't add a sequence number, we don't need it now. And a new hashing/caching TVLV described above should work fine later. \ No newline at end of file

1 0

[doc] backup-redmine/2023-01-14,main: doc: batman-adv/Multicast-Packet-Type (7f9b61e8)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 7f9b61e804df15d882e9ea738cbc8981aea074dd Author: Linus L��ssing <linus.luessing(a)c0d3.blue> Date: Mon Dec 26 14:57:09 2022 +0000 doc: batman-adv/Multicast-Packet-Type >--------------------------------------------------------------- 7f9b61e804df15d882e9ea738cbc8981aea074dd batman-adv/Multicast-Packet-Type.textile | 22 +++++++++------------- 1 file changed, 9 insertions(+), 13 deletions(-) diff --git a/batman-adv/Multicast-Packet-Type.textile b/batman-adv/Multicast-Packet-Type.textile index f39888ae..f5daa29d 100644 --- a/batman-adv/Multicast-Packet-Type.textile +++ b/batman-adv/Multicast-Packet-Type.textile @@ -85,21 +85,17 @@ Signalizes that: # This node is capable of receiving, parsing and forwarding a batman-adv multicast packet with a multicast tracker TVLV. # All hard interfaces of this node have an MTU of at least 1280. -h2. Implementation Tasks +h2. Limitations -*All nodes:* -* Signalize Multicast Packet capability to other nodes (add flag to BATADV_TVLV_MCAST) +* Neither the BATMAN IV nor BATMAN V routing algorithm can currently perform path MTU discovery. And the batman-adv fragmentation is not yet capable of handling this new batman-adv packet type, nor is it capable of reassembling per hop. Therefore the easy solution for now is to require an interface MTU of at least 1280 bytes on each active hard interface. 1280 bytes is also the IPv6 minimum MTU, so this makes it already less likely to be undercut in practice. +* If the payload data's size together with the number destination nodes is too large, so if the final batman-adv multicast packet would exceed 1280 bytes (excluding the outter ethernet frame), then the batman-adv multicast packet type cannot/will not be used. Example limits: +** 2 destination nodes: 1222 bytes ethernet frame size +** 8 destination nodes: 1186 bytes ethernet frame size +** 32 destination nodes: 1030 bytes ethernet frame size +** 128 destination nodes: 454 bytes ethernet frame size +** 196 destination nodes: 46 bytes ethernet frame size (= minimum ethernet frame size without a VLAN) -*Forwarding Nodes:* -* Parse Multicast Packet Type, potentially split multicast packet if multiple next hops to forward to - -*Receiving Nodes:* -* Decapsulate: Remove batman-adv multicast packet header, forward to upper interface (bat0) - -*Originating Nodes:* -# Check if all (optimization: on path) batman-adv originators support Multicast Packet Capability -# If yes, further check if number of batman-adv multicast per IP multicast packet is smaller than multicast fanout setting. So calculate MTU - sizeof(_Data_) - sizeof(multicast-packet-header) and divide by number of destinations (check Translation Table). If it exceeds multicast fanout then bail out and fall back to broadcast flooding. Otherwise continue: -# +If such a limitation is reached then batman-adv will either fallback to multicast via multiple batman-adv unicast packes. Or if that is not possible either, to classic flooding. h2. Open questions, known issues, TODOs

1 0

[doc] backup-redmine/2023-01-14,main: doc: batman-adv/Multicast-Packet-Type (ba2dd9e5)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit ba2dd9e56abe8d57b82b1c8a3697deb8abf59bef Author: Linus L��ssing <linus.luessing(a)c0d3.blue> Date: Thu Dec 22 20:53:58 2022 +0000 doc: batman-adv/Multicast-Packet-Type >--------------------------------------------------------------- ba2dd9e56abe8d57b82b1c8a3697deb8abf59bef batman-adv/Multicast-Packet-Type.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/Multicast-Packet-Type.textile b/batman-adv/Multicast-Packet-Type.textile index a76ef537..ca556c03 100644 --- a/batman-adv/Multicast-Packet-Type.textile +++ b/batman-adv/Multicast-Packet-Type.textile @@ -55,7 +55,7 @@ MCAST Tracker TVLV: +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | TVLV Type | TVLV Version | TVLV Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | [padding] | #Num Dests (N) | + | #Num Dests (N) | [padding] | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Dest 1 ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

1 0

[doc] backup-redmine/2023-01-14,main: doc: open-mesh/Download: switch to non-controversy git branch names (ac7f96e3)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit ac7f96e3842fbdd9be30b718c3f94ec2b838867d Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Dec 17 13:32:57 2022 +0000 doc: open-mesh/Download: switch to non-controversy git branch names >--------------------------------------------------------------- ac7f96e3842fbdd9be30b718c3f94ec2b838867d open-mesh/Download.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/Download.textile b/open-mesh/Download.textile index bf12d24a..736cecad 100644 --- a/open-mesh/Download.textile +++ b/open-mesh/Download.textile @@ -2,7 +2,7 @@ h1. Download B.A.T.M.A.N. We are currently working on different branches. To get the details about the differences of these branches, see our [[BranchesExplained|Branches Explained page]]. -Please use the maint branch for your public infrastructure unless you know exactly what you are doing and are prepared for the big unknown. +Please use the stable branch for your public infrastructure unless you know exactly what you are doing and are prepared for the big unknown. h2. Download Released Source Code

1 0

[doc] backup-redmine/2023-01-14,main: doc: batman-adv/Multicast-Packet-Type (75c81462)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 75c814627e8928800b1f675e86bb7c47f4d466a3 Author: Linus L��ssing <linus.luessing(a)c0d3.blue> Date: Tue Dec 20 15:26:12 2022 +0000 doc: batman-adv/Multicast-Packet-Type >--------------------------------------------------------------- 75c814627e8928800b1f675e86bb7c47f4d466a3 batman-adv/Multicast-Packet-Type.textile | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/batman-adv/Multicast-Packet-Type.textile b/batman-adv/Multicast-Packet-Type.textile index 58fd81dd..a76ef537 100644 --- a/batman-adv/Multicast-Packet-Type.textile +++ b/batman-adv/Multicast-Packet-Type.textile @@ -74,10 +74,9 @@ MCAST Tracker TVLV: * #Num Dests: Number of destinations (originator MAC addresses) * [padding]: Optional, only present if #Num Dests are even, to make Tracker TVLV 4 byte aligned (to make encapsulated IP packets 4 byte aligned) - -h4. Preparations for Multicast Tracker Packets (future enhancements) - -The fields _Tracker-ID_ and _MCAST Address_ will not be used in the initial implementation of the batman-adv multicast packet type. But they are in preparation for the future enhancements where control and data plane can be separated. That is where batman-adv multicast packets can also be send without _Data_ (_Multicast Tracker Packets_) and the destinations are cached on nodes on the path. And then further batman-adv multicast packets could be send with _Data_ but with a zero length TVLV, so without the destination addresses. +h4. -Preparations for Multicast Tracker Packets (future enhancements) +- +-The fields _Tracker-ID_ and _MCAST Address_ will not be used in the initial implementation of the batman-adv multicast packet type. But they are in preparation for the future enhancements where control and data plane can be separated. That is where batman-adv multicast packets can also be send without _Data_ (_Multicast Tracker Packets_) and the destinations are cached on nodes on the path. And then further batman-adv multicast packets could be send with _Data_ but with a zero length TVLV, so without the destination addresses.- h2. Implementation Tasks

1 0

[doc] backup-redmine/2023-01-14,main: doc: batman-adv/Multicast-Packet-Type (41be84ca)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 41be84cab8408a28ee7476629f665a67d57c9ac7 Author: Linus L��ssing <linus.luessing(a)c0d3.blue> Date: Mon Dec 26 14:29:39 2022 +0000 doc: batman-adv/Multicast-Packet-Type >--------------------------------------------------------------- 41be84cab8408a28ee7476629f665a67d57c9ac7 batman-adv/Multicast-Packet-Type.textile | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) diff --git a/batman-adv/Multicast-Packet-Type.textile b/batman-adv/Multicast-Packet-Type.textile index ca556c03..f39888ae 100644 --- a/batman-adv/Multicast-Packet-Type.textile +++ b/batman-adv/Multicast-Packet-Type.textile @@ -25,7 +25,7 @@ For more details see: h2. Technical Specification -MCAST packet type header: +h3. MCAST packet type header <pre><code> 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 @@ -48,7 +48,7 @@ MCAST packet type header: * Data: Encapsulated ethernet frame with 2 byte alignment (to make IP packets 4 byte aligned) -MCAST Tracker TVLV: +h3. MCAST Tracker TVLV <pre><code> 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 @@ -74,9 +74,16 @@ MCAST Tracker TVLV: * #Num Dests: Number of destinations (originator MAC addresses) * [padding]: Optional, only present if #Num Dests are even, to make Tracker TVLV 4 byte aligned (to make encapsulated IP packets 4 byte aligned) -h4. -Preparations for Multicast Tracker Packets (future enhancements) -- --The fields _Tracker-ID_ and _MCAST Address_ will not be used in the initial implementation of the batman-adv multicast packet type. But they are in preparation for the future enhancements where control and data plane can be separated. That is where batman-adv multicast packets can also be send without _Data_ (_Multicast Tracker Packets_) and the destinations are cached on nodes on the path. And then further batman-adv multicast packets could be send with _Data_ but with a zero length TVLV, so without the destination addresses.- +h3. OGM Multicast TVLV flags + +The following flag is added to the [[Multicast-optimizations-tech#Multicast-TVLV|MCAST flags]] in the multicast TVLV of an OGM: + +h4. BATADV_MCAST_HAVE_MC_PTYPE_CAPA (Bit 5): + +Signalizes that: + +# This node is capable of receiving, parsing and forwarding a batman-adv multicast packet with a multicast tracker TVLV. +# All hard interfaces of this node have an MTU of at least 1280. h2. Implementation Tasks

1 0

[doc] backup-redmine/2023-01-14,main: doc: batman-adv/Multicast-Packet-Type (5b7be596)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 5b7be596e1e6268f2a74f2fe301580d5fa129dcd Author: Linus L��ssing <linus.luessing(a)c0d3.blue> Date: Tue Dec 20 15:25:41 2022 +0000 doc: batman-adv/Multicast-Packet-Type >--------------------------------------------------------------- 5b7be596e1e6268f2a74f2fe301580d5fa129dcd batman-adv/Multicast-Packet-Type.textile | 34 +++++++++++++++----------------- 1 file changed, 16 insertions(+), 18 deletions(-) diff --git a/batman-adv/Multicast-Packet-Type.textile b/batman-adv/Multicast-Packet-Type.textile index e1b9cab9..58fd81dd 100644 --- a/batman-adv/Multicast-Packet-Type.textile +++ b/batman-adv/Multicast-Packet-Type.textile @@ -32,13 +32,11 @@ MCAST packet type header: +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Type | Version | TTL | reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | (Anonymous) Originator / MCAST Tracker-ID ... | - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | ... | TVLV length | + | TVLV length | MCAST Tracker TVLV ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-| - | MCAST Tracker TVLV ... | + | ... | Data ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-| - | Data ... | + | ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ </code></pre> @@ -46,8 +44,8 @@ MCAST packet type header: * Version: 15 * TTL: * reserved: 0x00 -* (Anonymous) Originator / Tracker-ID: 6 random bytes per (orig-addr, mcast-addr) tuple * TVLV length: +* Data: Encapsulated ethernet frame with 2 byte alignment (to make IP packets 4 byte aligned) MCAST Tracker TVLV: @@ -55,27 +53,27 @@ MCAST Tracker TVLV: <pre><code> 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | TVLV Type | TVLV Version | TVLV Length | - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | MCAST Address ... | + | TVLV Type | TVLV Version | TVLV Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | ... | VID | + | [padding] | #Num Dests (N) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | #Num Dests (N) | Dest 1 ... | + | Dest 1 ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | ... | + | ... | Dest 2 ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Dest 2 ... | + | ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | ... | ... | + | ... | Dest N ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Dest N ... | - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | ... | [padding] | + | ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ </code></pre> -* TVLV Type: +* TVLV Type: 0x07 +* TVLV Version: 1 +* #Num Dests: Number of destinations (originator MAC addresses) +* [padding]: Optional, only present if #Num Dests are even, to make Tracker TVLV 4 byte aligned (to make encapsulated IP packets 4 byte aligned) + h4. Preparations for Multicast Tracker Packets (future enhancements)

1 0

[doc] backup-redmine/2023-01-14,main: doc: batman-adv/Building-with-openwrt: switch to non-controversy git branch names (0ce6163e)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 0ce6163e4970fd070ee994970215cc70fbb19347 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Dec 17 13:28:19 2022 +0000 doc: batman-adv/Building-with-openwrt: switch to non-controversy git branch names >--------------------------------------------------------------- 0ce6163e4970fd070ee994970215cc70fbb19347 batman-adv/Building-with-openwrt.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/Building-with-openwrt.textile b/batman-adv/Building-with-openwrt.textile index 8b6446a0..990f04e6 100644 --- a/batman-adv/Building-with-openwrt.textile +++ b/batman-adv/Building-with-openwrt.textile @@ -172,7 +172,7 @@ Kernel modules ---> h2. Building from a different branch -The developer package offers a convenient way to select another branch to build from. This is particularly useful for testing features that have not been merged into the master branch yet. Simply enter the branch or git tag you wish to build in the Openwrt build menu. +The developer package offers a convenient way to select another branch to build from. This is particularly useful for testing features that have not been merged into the main branch yet. Simply enter the branch or git tag you wish to build in the Openwrt build menu. h2. Kernel crash debug

1 0

[doc] backup-redmine/2023-01-14,main: doc: batman-adv/Tweaking: switch to non-controversy git branch names (502d987d)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 502d987db823697cc6f6423b1727aa1ec3576351 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Dec 17 13:28:04 2022 +0000 doc: batman-adv/Tweaking: switch to non-controversy git branch names >--------------------------------------------------------------- 502d987db823697cc6f6423b1727aa1ec3576351 batman-adv/Tweaking.textile | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/batman-adv/Tweaking.textile b/batman-adv/Tweaking.textile index 841b4c97..1e5a0ff1 100644 --- a/batman-adv/Tweaking.textile +++ b/batman-adv/Tweaking.textile @@ -104,7 +104,7 @@ h3. bridge loop avoidance Available since: batman-adv 2012.2.0 (if bridge loop avoidance has been compiled-in) In bridged LAN setups it is advisable to enable the bridge loop avoidance in order to avoid broadcast loops that can bring the entire LAN to a standstill. The [[Bridge-loop-avoidance|bridge loop avoidance page]] explains the bridge loop problematic in greater detail as well as the batman-adv approach to address it. -It is necessary to activate the bridge loop avoidance at compile time before you can use this feature (consult "the README.external file":https://git.open-mesh.org/batman-adv.git/blob/refs/heads/master:/README.external to learn how to set the compile option). +It is necessary to activate the bridge loop avoidance at compile time before you can use this feature (consult "the README.external file":https://git.open-mesh.org/batman-adv.git/blob/refs/heads/main:/README.external to learn how to set the compile option). <pre> batctl meshif bat0 bridge_loop_avoidance @@ -116,7 +116,7 @@ h3. distributed ARP table Available since: batman-adv 2013.0.0 When enabled the distributed ARP table forms a mesh-wide ARP cache that helps non-mesh clients to get ARP responses much more reliably and without much delay. A comprehensive documentation has been made available in our wiki. One document focuses on the [[batman-adv:DistributedARPTable|general DAT concept]] whereas the second document is about the [[DistributedArpTable-technical|technical details & implementation specifics]]. -It is necessary to activate the distributed ARP table at compile time before you can use this feature (consult "the README.external file":https://git.open-mesh.org/batman-adv.git/blob/refs/heads/master:/README.external to learn how to set the compile option). +It is necessary to activate the distributed ARP table at compile time before you can use this feature (consult "the README.external file":https://git.open-mesh.org/batman-adv.git/blob/refs/heads/main:/README.external to learn how to set the compile option). <pre> batctl meshif bat0 distributed_arp_table @@ -192,7 +192,7 @@ h3. log level Available since: batman-adv 2010.1.0 -The standard warning and error messages which help to setup & operate batman-adv are sent to the kernel log. However, batman-adv also offers extended logs that can be used to understand and/or debug the routing protocol. Keep in mind that it is necessary to activate debugging at compile time before you can use these facilities (consult "the README.external file":https://git.open-mesh.org/batman-adv.git/blob/refs/heads/master:/README.external to learn how to set the compile option). Per default, the logging is deactivated (log level: 0). +The standard warning and error messages which help to setup & operate batman-adv are sent to the kernel log. However, batman-adv also offers extended logs that can be used to understand and/or debug the routing protocol. Keep in mind that it is necessary to activate debugging at compile time before you can use these facilities (consult "the README.external file":https://git.open-mesh.org/batman-adv.git/blob/refs/heads/main:/README.external to learn how to set the compile option). Per default, the logging is deactivated (log level: 0). <pre> batctl meshif bat0 loglevel @@ -224,7 +224,7 @@ h3. network coding Available since: batman-adv 2013.2.0 When enabled network coding increases the WiFi throughput by combining multiple frames into a single frame, thus reducing the needed air time. A comprehensive documentation has been made available in our wiki. One document focuses on the [[batman-adv:NetworkCoding|general network coding concept]] whereas the second document is about the [[NetworkCoding-technical|technical details & implementation specifics]]. Our download section also contains recorded network coding talks. -It is necessary to activate network coding at compile time before you can use this feature (consult "the README.external file":https://git.open-mesh.org/batman-adv.git/blob/refs/heads/master:/README.external to learn how to set the compile option). +It is necessary to activate network coding at compile time before you can use this feature (consult "the README.external file":https://git.open-mesh.org/batman-adv.git/blob/refs/heads/main:/README.external to learn how to set the compile option). <pre> batctl meshif bat0 network_coding

1 0

[doc] backup-redmine/2023-01-14,main: doc: batman-adv/Understand-your-batman-adv-network: switch to non-controversy git branch names (52dbcbfd)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 52dbcbfd977af5e4b43838345af5a59f7c2214ac Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Dec 17 13:27:19 2022 +0000 doc: batman-adv/Understand-your-batman-adv-network: switch to non-controversy git branch names >--------------------------------------------------------------- 52dbcbfd977af5e4b43838345af5a59f7c2214ac batman-adv/Understand-your-batman-adv-network.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/Understand-your-batman-adv-network.textile b/batman-adv/Understand-your-batman-adv-network.textile index 0dcc5cec..e573c6b6 100644 --- a/batman-adv/Understand-your-batman-adv-network.textile +++ b/batman-adv/Understand-your-batman-adv-network.textile @@ -357,7 +357,7 @@ Traditional network debugging tools based on the ICMP protocol such as ping or t h2. Logging -Batman-adv offers extended logging to understand & debug the routing protocol internals. After you activated debugging +tracing at compile time (instructions can be found in "the README file":https://git.open-mesh.org/batman-adv.git/blob/refs/heads/master:/README.external ) and the appropriate log level has been set (read about the log levels [[tweaking|here]]) you can retrieve the logs by simply reading the 'log' file: +Batman-adv offers extended logging to understand & debug the routing protocol internals. After you activated debugging +tracing at compile time (instructions can be found in "the README file":https://git.open-mesh.org/batman-adv.git/blob/refs/heads/main:/README.external ) and the appropriate log level has been set (read about the log levels [[tweaking|here]]) you can retrieve the logs by simply reading the 'log' file: <pre> $ batctl ll all

1 0

← Newer
1
2
3
4
5
6
7
8
9
...
29
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits January 2023