commits

commits@lists.open-mesh.org

1 participants
12379 discussions

[doc] main: Merge branch 'backup-redmine/2023-11-04' (e3cf2301)
by postmaster＠open-mesh.org 04 Nov '23

04 Nov '23

Repository : ssh://git@diktynna/doc On branch : main >--------------------------------------------------------------- commit e3cf23012fcace9753b4d33e61d1752dca2bf4d3 Merge: b75ae92a e6ca019e Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Nov 4 09:46:04 2023 +0100 Merge branch 'backup-redmine/2023-11-04' >--------------------------------------------------------------- e3cf23012fcace9753b4d33e61d1752dca2bf4d3 batman-adv/Feature-History.rst | 3 +++ open-mesh/Contribute.rst | 7 ++++--- open-mesh/MailingList.rst | 2 ++ 3 files changed, 9 insertions(+), 3 deletions(-) diff --cc batman-adv/Feature-History.rst index 0dfaa958,00000000..aeae7fc9 mode 100644,000000..100644 --- a/batman-adv/Feature-History.rst +++ b/batman-adv/Feature-History.rst @@@ -1,83 -1,0 +1,86 @@@ +.. SPDX-License-Identifier: GPL-2.0 + +Feature History +=============== + +- **AP Isolation** + + - Initial support: 2011.4.0 + - Extended AP Isolation: v2014.1.0 + +- **BLA** + + - Initial support: v2011.0.0 + - BLA v2: v2012.2.0 + - Enabled by default: v2015.1 + - Detection of complex bridge loops: v2016.2 + +- **Bonding** + + - v2010.1.0 + +- **Broadcast** + + - 3x broadcast: v0.2 + - Retransmissions only on wireless: v2013.3.0 + - Broadcast Avoidances: v2016.5 + +- **DAT** + + - Initial support: v2013.0.0 + - DHCP-ACK snooping: v2019.1 + - Before timeout refreshing: v2019.2 + +- **Fragmentation** + + - Initial support: v2010.2.0 + - Fragmentation v2: v2014.0.0 + +- **Gateway Feature** + + - Initial support: v2011.0.0 + +- **Interface Alternating** + + - Initial support: v2010.1.0 + - Interface Alternating v2: v2014.1.0 + +- **Multicast Optimizations** + + - Multicast TT + TVLV support: v2014.2.0 + - Bridge support: v2016.3 + - Multicast-to-multi-unicast: v2019.2 ++ - Preliminary routable IPv6 multicast address support: v2019.3 ++ - Full, MRD based routable IPv4/IPv6 multicast address support: v2021.2 + +- **Network Coding** + + - v2013.2.0 + +- **BATMAN IV** + + - v0.1 + +- **BATMAN V** + + - OGMv2 / ELP / Throughput metric: v2016.1 ++ - WLAN TX bitrate fallback: v2020.0 + +- **TT** + + - Initial support: 2011.3.0 + - Speedy Join: v2012.4.0 + +- **TVLV support (compat 15):** + + - v2014.0.0 + +- **Vis** + + - removed in: v2014.0.0 + +- **Misc:** + + - Hop-penalty 15 -> 30: v2014.4.0 (and in v2012.2.0? how much?) + - Multiple mesh interfaces: v2010.2.0 + - Netlink: v2016.3 (+ v2016.4, v2016.5, …) diff --cc open-mesh/Contribute.rst index 882c764a,00000000..25ea077d mode 100644,000000..100644 --- a/open-mesh/Contribute.rst +++ b/open-mesh/Contribute.rst @@@ -1,124 -1,0 +1,125 @@@ +.. SPDX-License-Identifier: GPL-2.0 + +How to Contribute +================= + +Thanks for using B.A.T.M.A.N.! If you have suggestions, comments, want +to tell us about your experiences or discuss problems the best thing is +always to use the :doc:`Mailing List <MailingList>` You can always contact +us via :doc:`IRC <IRC>`. + +If you like this project and you want to take part and/or give something +back, here is a short list of starting points: + +Reporting Bugs +-------------- + +If you find a bug, please see if the problem is already known in the by +Reading the Tickets: + +- for `batman-adv </projects/batman-adv/issues>`__ +- for `batctl </projects/batctl/issues>`__ +- for `alfred </projects/alfred/issues>`__ +- for `batmand </projects/batmand/issues>`__ +- for `vis </projects/vis/issues>`__ + +If not, please add a new Ticket: + +- for `batman-adv </projects/batman-adv/issues/new>`__ +- for `batctl </projects/batctl/issues/new>`__ +- for `alfred </projects/alfred/issues/new>`__ +- for `batmand </projects/batmand/issues/new>`__ +- for `vis </projects/vis/issues/new>`__ + +Please add as much information as possible. In particular interesting +are: + +- Which branch (batman, batctl, batman-adv) +- Which version (0.X, git revision number) +- kernel version, distribution (and version) +- machine type (PC, Linksys WRT, Fon, NS2, ...) +- command line parameters used +- iptables/firewall rules +- :doc:`get a coredump </batmand/Coredump>` if you experience a segfault +- your guess what triggered the problem. ;) + +Documentation / Feedback +------------------------ + +Write an article about your experience with B.A.T.M.A.N. and have it +published here or ask us to link to your site: + +- How did you find us ? +- How does you setup look like ? +- Where are you building your mesh ? +- What problems did you encounter ? +- How did you debug / solve them ? +- What did you like / not like ? +- How can B.A.T.M.A.N. improve ? + +There's lots of people that want to know about B.A.T.M.A.N. - help us to +spread the word! You also can create a wiki account and improve the +documentation. + +Research +-------- + +B.A.T.M.A.N. gives much room for research, especially the layer 2 +implementation in the kernel. Get in touch with us to share your ideas. +If you write papers we are happy to publish them here or link to your +page. If you are looking for the right topic or mentorship feel free to +contact us. We have more ideas than time to implement them. + +Development +----------- + +You looked in the code ? Fixed bugs ? Added a cool new function ? +Integrated B.A.T.M.A.N. in a distribution ? Don't hesitate to let us and +others know! We can avoid duplicated work by publishing it here or +linking to your page. Patches are always welcome and can be posted on +the :doc:`mailing list <MailingList>` to get integrated. We also hand out +git access to people that want to get involved. + +Submitting patches +------------------ + +If you intend to send us patches, please consider the following +guidelines: + +* Prefer small & digestible over long "all in one" patches. +* No MIME, no links, no compression, no attachments. Just plain text + (patches are to be sent inline). +* Patches sent to the mailing list should include "PATCH" in the + subject to make it easier to distinguish between patches and + discussions. +* The mail's subject will become the first line in the commit message. + The body contains the longer patch description and the patch (unified + format) itself. Please also specify the target branch (e.g. batctl, + batman-adv, etc) at the beginning of the subject line. +* Add a "Signed-off-by: Your Name <you(a)example.com>" line to the patch + message to make the ownership of the patch clear. +* Patches for B.A.T.M.A.N. Advanced need to follow the linux kernel + coding style closely (use checkpatch.pl to verify your patch) as well as + the linux "how to submit patches" guidelines (search for the term + SubmitPatches to find thorough documentation). +* Check it using static analysis tools like + `sparse <https://sparse.wiki.kernel.org/>`__ (cgcc) and + `cppcheck <http://cppcheck.sourceforge.net/>`__ +* Patches against the batman-adv main branch must be formatted using + - :: ++ :: + + git format-patch $BASECOMMIT + ++ or an equivalent tool (like ``b4``) ++ +- README, manpage and sysfs-class-net-\* must be updated together with + the related source change +- Add or update kerneldoc to functions and structures you add or + modify. +- batman-adv changes affecting batctl have to be send with the batctl + patches in the same patchset - - it is recommended to use \`git send-email\` to send the mails to the - mailinglist ++- it is recommended to use `b4 <https://b4.docs.kernel.org/>`__ to send the patch mails to the mailinglist - but plain ``git send-email`` is also fine. +- An exemplary good submission you may want to look at can be found + here: + https://patchwork.open-mesh.org/project/b.a.t.m.a.n./patch/1261051915-13960… diff --cc open-mesh/MailingList.rst index 24783d58,00000000..47268237 mode 100644,000000..100644 --- a/open-mesh/MailingList.rst +++ b/open-mesh/MailingList.rst @@@ -1,18 -1,0 +1,20 @@@ +.. SPDX-License-Identifier: GPL-2.0 + +Mailing List +============ + +You can subscribe to our Mailing Lists +`here <https://lists.open-mesh.org/>`__. You can also send an E-Mail +without subscription to b.a.t.m.a.n(a)lists.open-mesh.org, but keep in +mind that this message will have to be accepted manually (and this can +take some time). + +*Note*: HTML email will be rejected - just plain text is allowed (this +cuts the rate of SPAM mails dramatically). + ++And please follow the `Mailing list etiquette <https://subspace.kernel.org/etiquette.html>`__. ++ +Old messages can be read in the `B.A.T.M.A.N. +archives <https://lists.open-mesh.org/mailman3/hyperkitty/list/b.a.t.m.a.n@lists.open…>`__. +Or via the various subscription (or mirror) methods from +`lore.kernel.org <https://lore.kernel.org/batman>`__

1 0

[doc] backup-redmine/2023-11-04,main: doc: batman-adv/Feature-History (f6b403ee)
by postmaster＠open-mesh.org 04 Nov '23

04 Nov '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-11-04,main >--------------------------------------------------------------- commit f6b403eefbfb3e199c5f4ca9f0f9e2c62189e0b9 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Tue Oct 31 04:14:46 2023 +0000 doc: batman-adv/Feature-History >--------------------------------------------------------------- f6b403eefbfb3e199c5f4ca9f0f9e2c62189e0b9 batman-adv/Feature-History.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/Feature-History.textile b/batman-adv/Feature-History.textile index 41ae11dd..15b4aa00 100644 --- a/batman-adv/Feature-History.textile +++ b/batman-adv/Feature-History.textile @@ -31,7 +31,7 @@ h1. Feature History ** Bridge support: v2016.3 ** Multicast-to-multi-unicast: v2019.2 ** Preliminary routable IPv6 multicast support: v2019.3 -** Full, MRD based routable IPv4/IPv6 multicast address support +** Full, MRD based routable IPv4/IPv6 multicast address support: v2021.2 * *Network Coding* ** v2013.2.0 * *BATMAN IV*

1 0

[doc] backup-redmine/2023-11-04,main: doc: batman-adv/Feature-History (e6ca019e)
by postmaster＠open-mesh.org 04 Nov '23

04 Nov '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-11-04,main >--------------------------------------------------------------- commit e6ca019e36cd1f138d11fa7e8cf31b33089beb56 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Tue Oct 31 04:30:40 2023 +0000 doc: batman-adv/Feature-History >--------------------------------------------------------------- e6ca019e36cd1f138d11fa7e8cf31b33089beb56 batman-adv/Feature-History.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/Feature-History.textile b/batman-adv/Feature-History.textile index c0dbfbce..ff83b0c1 100644 --- a/batman-adv/Feature-History.textile +++ b/batman-adv/Feature-History.textile @@ -38,7 +38,7 @@ h1. Feature History ** v0.1 * *BATMAN V* ** OGMv2 / ELP / Throughput metric: v2016.1 -** WiFi TX bitrate fallback: v2020.0 +** WLAN TX bitrate fallback: v2020.0 * *TT* ** Initial support: 2011.3.0 ** Speedy Join: v2012.4.0

1 0

[doc] backup-redmine/2023-11-04,main: doc: batman-adv/Feature-History (86ef1747)
by postmaster＠open-mesh.org 04 Nov '23

04 Nov '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-11-04,main >--------------------------------------------------------------- commit 86ef1747ae04e8a0a2ce4bfa641905be97032400 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Tue Oct 31 04:16:47 2023 +0000 doc: batman-adv/Feature-History >--------------------------------------------------------------- 86ef1747ae04e8a0a2ce4bfa641905be97032400 batman-adv/Feature-History.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/Feature-History.textile b/batman-adv/Feature-History.textile index 15b4aa00..6ddf3099 100644 --- a/batman-adv/Feature-History.textile +++ b/batman-adv/Feature-History.textile @@ -30,7 +30,7 @@ h1. Feature History ** Multicast TT + TVLV support: v2014.2.0 ** Bridge support: v2016.3 ** Multicast-to-multi-unicast: v2019.2 -** Preliminary routable IPv6 multicast support: v2019.3 +** Preliminary routable IPv6 multicast address support: v2019.3 ** Full, MRD based routable IPv4/IPv6 multicast address support: v2021.2 * *Network Coding* ** v2013.2.0

1 0

[doc] backup-redmine/2023-11-04,main: doc: open-mesh/Contribute (97d1925d)
by postmaster＠open-mesh.org 04 Nov '23

04 Nov '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-11-04,main >--------------------------------------------------------------- commit 97d1925d84c68b117ba0a1f5b51d2745a2d26d72 Author: Sven Eckelmann <sven(a)narfation.org> Date: Mon Oct 30 16:16:04 2023 +0000 doc: open-mesh/Contribute >--------------------------------------------------------------- 97d1925d84c68b117ba0a1f5b51d2745a2d26d72 open-mesh/Contribute.textile | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/open-mesh/Contribute.textile b/open-mesh/Contribute.textile index 12702da5..5e2994b8 100644 --- a/open-mesh/Contribute.textile +++ b/open-mesh/Contribute.textile @@ -62,7 +62,6 @@ h2. Development You looked in the code ? Fixed bugs ? Added a cool new function ? Integrated B.A.T.M.A.N. in a distribution ? Don't hesitate to let us and others know! We can avoid duplicated work by publishing it here or linking to your page. Patches are always welcome and can be posted on the [[MailingList|mailing list]] to get integrated. We also hand out git access to people that want to get involved. - h2. Submitting patches @@ -75,15 +74,11 @@ If you intend to send us patches, please consider the following guidelines: * Add a "Signed-off-by: Your Name <you(a)example.com>" line to the patch message to make the ownership of the patch clear. * Patches for B.A.T.M.A.N. Advanced need to follow the linux kernel coding style closely (use checkpatch.pl to verify your patch) as well as the linux "how to submit patches" guidelines (search for the term SubmitPatches to find thorough documentation). * Check it using static analysis tools like "sparse":https://sparse.wiki.kernel.org/ (cgcc) and "cppcheck":http://cppcheck.sourceforge.net/ -* Patches against the batman-adv main branch must be formatted using -<pre> +* Patches against the batman-adv main branch must be formatted using <pre> git format-patch $BASECOMMIT -</pre> +</pre> or an equivalent tool (like <code>b4</code>) * README, manpage and sysfs-class-net-* must be updated together with the related source change * Add or update kerneldoc to functions and structures you add or modify. * batman-adv changes affecting batctl have to be send with the batctl patches in the same patchset -* it is recommended to use `git send-email` to send the mails to the mailinglist +* it is recommended to use "b4":https://b4.docs.kernel.org/ to send the patch mails to the mailinglist - but plain `git send-email` is also fine. * An exemplary good submission you may want to look at can be found here: https://patchwork.open-mesh.org/project/b.a.t.m.a.n./patch/1261051915-13960… \ No newline at end of file - - -

1 0

[doc] backup-redmine/2023-11-04,main: doc: batman-adv/Feature-History (7af03fb8)
by postmaster＠open-mesh.org 04 Nov '23

04 Nov '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-11-04,main >--------------------------------------------------------------- commit 7af03fb8c19a40d395fc029c782aa4c0a4d9886d Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Tue Oct 31 04:14:18 2023 +0000 doc: batman-adv/Feature-History >--------------------------------------------------------------- 7af03fb8c19a40d395fc029c782aa4c0a4d9886d batman-adv/Feature-History.textile | 2 ++ 1 file changed, 2 insertions(+) diff --git a/batman-adv/Feature-History.textile b/batman-adv/Feature-History.textile index d624eef4..41ae11dd 100644 --- a/batman-adv/Feature-History.textile +++ b/batman-adv/Feature-History.textile @@ -30,6 +30,8 @@ h1. Feature History ** Multicast TT + TVLV support: v2014.2.0 ** Bridge support: v2016.3 ** Multicast-to-multi-unicast: v2019.2 +** Preliminary routable IPv6 multicast support: v2019.3 +** Full, MRD based routable IPv4/IPv6 multicast address support * *Network Coding* ** v2013.2.0 * *BATMAN IV*

1 0

[doc] backup-redmine/2023-11-04,main: doc: batman-adv/Feature-History (1d0e9355)
by postmaster＠open-mesh.org 04 Nov '23

04 Nov '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-11-04,main >--------------------------------------------------------------- commit 1d0e93557199ec0676765a5dfc3e7bb5d6b51958 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Tue Oct 31 04:30:13 2023 +0000 doc: batman-adv/Feature-History >--------------------------------------------------------------- 1d0e93557199ec0676765a5dfc3e7bb5d6b51958 batman-adv/Feature-History.textile | 1 + 1 file changed, 1 insertion(+) diff --git a/batman-adv/Feature-History.textile b/batman-adv/Feature-History.textile index 6ddf3099..c0dbfbce 100644 --- a/batman-adv/Feature-History.textile +++ b/batman-adv/Feature-History.textile @@ -38,6 +38,7 @@ h1. Feature History ** v0.1 * *BATMAN V* ** OGMv2 / ELP / Throughput metric: v2016.1 +** WiFi TX bitrate fallback: v2020.0 * *TT* ** Initial support: 2011.3.0 ** Speedy Join: v2012.4.0

1 0

[doc] backup-redmine/2023-11-04,main: doc: open-mesh/News-draft: 2023.3 draft (2f6be58c)
by postmaster＠open-mesh.org 04 Nov '23

04 Nov '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-11-04,main >--------------------------------------------------------------- commit 2f6be58c3ddef2299b997967f7a4902230ba8c9e Author: Sven Eckelmann <sven(a)narfation.org> Date: Mon Oct 30 15:36:09 2023 +0000 doc: open-mesh/News-draft: 2023.3 draft >--------------------------------------------------------------- 2f6be58c3ddef2299b997967f7a4902230ba8c9e open-mesh/News-draft.textile | 61 ++++++++++++++++++++++++-------------------- 1 file changed, 33 insertions(+), 28 deletions(-) diff --git a/open-mesh/News-draft.textile b/open-mesh/News-draft.textile index 06fec3ff..a99a8db0 100644 --- a/open-mesh/News-draft.textile +++ b/open-mesh/News-draft.textile @@ -1,32 +1,35 @@ -h1. DRAFT: Batman-adv 2023.2 released +h1. DRAFT: Batman-adv 2023.3 released -Aug 4th, 2023. Today the B.A.T.M.A.N. team publishes the August 2023 update to batman-adv! Alfred now allows to send data via unix socket to a primary server when none of the interfaces is ready. Also several bug fixes and code cleanups are included in this version. +Nov 15th, 2023. Today the B.A.T.M.A.N. team publishes the November 2023 update to batman-adv! batman-adv is no longer warning about an MTU reduction when the soft-interfaces already has a reduced MTU. Also several bug fixes and code cleanups are included in this version. As the kernel module always depends on the Linux kernel it is compiled against, it does not make sense to provide binaries on our website. As usual, you will find the signed tarballs in our download section: -https://downloads.open-mesh.org/batman/releases/batman-adv-2023.2/ +https://downloads.open-mesh.org/batman/releases/batman-adv-2023.3/ h2. Thanks Thanks to all people sending in patches: -* Marek Lindner <mareklindner(a)neomailbox.ch> -* Remi Pommarel <repk(a)triplefau.lt> * Simon Wunderlich <sw(a)simonwunderlich.de> * Sven Eckelmann <sven(a)narfation.org> -* Vladislav Efanov <VEfanov(a)ispras.ru> +* YueHaibing <yuehaibing(a)huawei.com> h2. batman-adv <pre> $ git describe origin/main -v2023.1-13-g67f427d8 -$ range=v2023.1..v2023.1-13-g67f427d8 +v2023.2-9-g5fecd4a3 +$ range=v2023.2..v2023.2-9-g5fecd4a3 $ git shortlog --email --no-merges "${range}" $ git log --no-merges "${range}"|grep -e '$Reported\|Tested\|Acked\|Reviewed-by\|Co-authored-by$-by'|sed 's/.*:/*/'|sort|uniq +Sven Eckelmann <sven(a)narfation.org> (6): + +YueHaibing <yuehaibing(a)huawei.com> (1): + batman-adv: Remove unused declarations + features ======== @@ -39,41 +42,43 @@ new kernel version coding style cleanup/refactoring ================================ + batman-adv: Remove unused declarations + batman-adv: Avoid magic value for minimum MTU + batman-adv: Drop unused function batadv_gw_bandwidth_set + batman-adv: Keep batadv_netlink_notify_* static + batman-adv: Drop per algo GW section class code + various ======= - batman-adv: compat: Use native kstrtox.h for 5.10.185 + batman-adv: Check hardif MTU against runtime MTU + bugfixes ======== - batman-adv: Do not get eth header before batadv_check_management_packet - batman-adv: Trigger events for auto adjusted MTU - batman-adv: Don't increase MTU when set by user - batman-adv: Broken sync while rescheduling delayed work + batman-adv: Hold rtnl lock during MTU update via netlink + -2023.2 (2023-08-04) +2023.3 (2023-11-15) =================== -* support latest kernels (4.14 - 6.5) +* support latest kernels (4.14 - 6.7) +* coding style cleanups and refactoring +* only warn about too small MTU when soft interfaces wasn't already reduced * bugs squashed: - - avoid potential invalid memory access when processing ELP/OGM2 packets - - drop pending DAT worker when interface shuts down - - inform network stack about automatically adjusted MTUs - - keep user defined MTU limit when MTU is recalculated - - fix packet memory leak when sending OGM2 via inactive interfaces - - fix TT memory leak for roamed back clients + - Hold rtnl lock during MTU update via netlink </pre> h2. batctl <pre> $ git describe origin/main -v2023.1-1-g2cfb13e -$ range=v2023.1..v2023.1-1-g2cfb13e +v2023.2-1-g5b72033 +$ range=v2023.2..v2023.2-1-g5b72033 $ git shortlog --email --no-merges "${range}" $ git log --no-merges "${range}"|grep -e '$Reported\|Tested\|Acked\|Reviewed-by\|Co-authored-by$-by'|sed 's/.*:/*/'|sort|uniq @@ -94,7 +99,7 @@ bugfixes -2023.2 (2023-08-04) +2023.3 (2023-11-15) =================== * (no changes) @@ -105,18 +110,18 @@ h2. alfred <pre> $ git describe origin/main -v2023.1-2-g94b3c4b -$ range=v2023.1..v2023.1-2-g94b3c4b +v2023.2-1-ge51f93a +$ range=v2023.2..v2023.2-1-ge51f93a $ git shortlog --email --no-merges "${range}" $ git log --no-merges "${range}"|grep -e '$Reported\|Tested\|Acked\|Reviewed-by\|Co-authored-by$-by'|sed 's/.*:/*/'|sort|uniq -2023.2 (2023-08-04) +2023.3 (2023-11-15) =================== -* receive data with valid source on unix sock without active interface +* (no changes) </pre>

1 0

[doc] backup-redmine/2023-11-04,main: doc: open-mesh/MailingList (9063177f)
by postmaster＠open-mesh.org 04 Nov '23

04 Nov '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-11-04,main >--------------------------------------------------------------- commit 9063177fcc471e2d8c4eccf6290d90ebe51cc51d Author: Sven Eckelmann <sven(a)narfation.org> Date: Tue Oct 24 19:30:10 2023 +0000 doc: open-mesh/MailingList >--------------------------------------------------------------- 9063177fcc471e2d8c4eccf6290d90ebe51cc51d open-mesh/MailingList.textile | 2 ++ 1 file changed, 2 insertions(+) diff --git a/open-mesh/MailingList.textile b/open-mesh/MailingList.textile index 6f55f6a2..7812b93a 100644 --- a/open-mesh/MailingList.textile +++ b/open-mesh/MailingList.textile @@ -4,4 +4,6 @@ You can subscribe to our Mailing Lists "here":https://lists.open-mesh.org/. You +Note+: HTML email will be rejected - just plain text is allowed (this cuts the rate of SPAM mails dramatically). +And please follow the "Mailing list etiquette":https://subspace.kernel.org/etiquette.html + Old messages can be read in the "B.A.T.M.A.N. archives":https://lists.open-mesh.org/mailman3/hyperkitty/list/b.a.t.m.a.n@lists.open-mesh.org/. Or via the various subscription (or mirror) methods from "lore.kernel.org":https://lore.kernel.org/batman

1 0

[doc] main: Merge branch 'backup-redmine/2023-11-04' (ea40aa33)
by postmaster＠open-mesh.org 04 Nov '23

04 Nov '23

Repository : ssh://git@diktynna/doc On branch : main >--------------------------------------------------------------- commit ea40aa33ab785d4bd8c12a362d57753b8e673abc Merge: b75ae92a e6ca019e Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Nov 4 09:46:04 2023 +0100 Merge branch 'backup-redmine/2023-11-04' >--------------------------------------------------------------- ea40aa33ab785d4bd8c12a362d57753b8e673abc batman-adv/Feature-History.rst | 3 +++ open-mesh/Contribute.rst | 5 +++-- open-mesh/MailingList.rst | 2 ++ 3 files changed, 8 insertions(+), 2 deletions(-) diff --cc batman-adv/Feature-History.rst index 0dfaa958,00000000..aeae7fc9 mode 100644,000000..100644 --- a/batman-adv/Feature-History.rst +++ b/batman-adv/Feature-History.rst @@@ -1,83 -1,0 +1,86 @@@ +.. SPDX-License-Identifier: GPL-2.0 + +Feature History +=============== + +- **AP Isolation** + + - Initial support: 2011.4.0 + - Extended AP Isolation: v2014.1.0 + +- **BLA** + + - Initial support: v2011.0.0 + - BLA v2: v2012.2.0 + - Enabled by default: v2015.1 + - Detection of complex bridge loops: v2016.2 + +- **Bonding** + + - v2010.1.0 + +- **Broadcast** + + - 3x broadcast: v0.2 + - Retransmissions only on wireless: v2013.3.0 + - Broadcast Avoidances: v2016.5 + +- **DAT** + + - Initial support: v2013.0.0 + - DHCP-ACK snooping: v2019.1 + - Before timeout refreshing: v2019.2 + +- **Fragmentation** + + - Initial support: v2010.2.0 + - Fragmentation v2: v2014.0.0 + +- **Gateway Feature** + + - Initial support: v2011.0.0 + +- **Interface Alternating** + + - Initial support: v2010.1.0 + - Interface Alternating v2: v2014.1.0 + +- **Multicast Optimizations** + + - Multicast TT + TVLV support: v2014.2.0 + - Bridge support: v2016.3 + - Multicast-to-multi-unicast: v2019.2 ++ - Preliminary routable IPv6 multicast address support: v2019.3 ++ - Full, MRD based routable IPv4/IPv6 multicast address support: v2021.2 + +- **Network Coding** + + - v2013.2.0 + +- **BATMAN IV** + + - v0.1 + +- **BATMAN V** + + - OGMv2 / ELP / Throughput metric: v2016.1 ++ - WLAN TX bitrate fallback: v2020.0 + +- **TT** + + - Initial support: 2011.3.0 + - Speedy Join: v2012.4.0 + +- **TVLV support (compat 15):** + + - v2014.0.0 + +- **Vis** + + - removed in: v2014.0.0 + +- **Misc:** + + - Hop-penalty 15 -> 30: v2014.4.0 (and in v2012.2.0? how much?) + - Multiple mesh interfaces: v2010.2.0 + - Netlink: v2016.3 (+ v2016.4, v2016.5, …) diff --cc open-mesh/Contribute.rst index 882c764a,00000000..c0aadf54 mode 100644,000000..100644 --- a/open-mesh/Contribute.rst +++ b/open-mesh/Contribute.rst @@@ -1,124 -1,0 +1,125 @@@ +.. SPDX-License-Identifier: GPL-2.0 + +How to Contribute +================= + +Thanks for using B.A.T.M.A.N.! If you have suggestions, comments, want +to tell us about your experiences or discuss problems the best thing is +always to use the :doc:`Mailing List <MailingList>` You can always contact +us via :doc:`IRC <IRC>`. + +If you like this project and you want to take part and/or give something +back, here is a short list of starting points: + +Reporting Bugs +-------------- + +If you find a bug, please see if the problem is already known in the by +Reading the Tickets: + +- for `batman-adv </projects/batman-adv/issues>`__ +- for `batctl </projects/batctl/issues>`__ +- for `alfred </projects/alfred/issues>`__ +- for `batmand </projects/batmand/issues>`__ +- for `vis </projects/vis/issues>`__ + +If not, please add a new Ticket: + +- for `batman-adv </projects/batman-adv/issues/new>`__ +- for `batctl </projects/batctl/issues/new>`__ +- for `alfred </projects/alfred/issues/new>`__ +- for `batmand </projects/batmand/issues/new>`__ +- for `vis </projects/vis/issues/new>`__ + +Please add as much information as possible. In particular interesting +are: + +- Which branch (batman, batctl, batman-adv) +- Which version (0.X, git revision number) +- kernel version, distribution (and version) +- machine type (PC, Linksys WRT, Fon, NS2, ...) +- command line parameters used +- iptables/firewall rules +- :doc:`get a coredump </batmand/Coredump>` if you experience a segfault +- your guess what triggered the problem. ;) + +Documentation / Feedback +------------------------ + +Write an article about your experience with B.A.T.M.A.N. and have it +published here or ask us to link to your site: + +- How did you find us ? +- How does you setup look like ? +- Where are you building your mesh ? +- What problems did you encounter ? +- How did you debug / solve them ? +- What did you like / not like ? +- How can B.A.T.M.A.N. improve ? + +There's lots of people that want to know about B.A.T.M.A.N. - help us to +spread the word! You also can create a wiki account and improve the +documentation. + +Research +-------- + +B.A.T.M.A.N. gives much room for research, especially the layer 2 +implementation in the kernel. Get in touch with us to share your ideas. +If you write papers we are happy to publish them here or link to your +page. If you are looking for the right topic or mentorship feel free to +contact us. We have more ideas than time to implement them. + +Development +----------- + +You looked in the code ? Fixed bugs ? Added a cool new function ? +Integrated B.A.T.M.A.N. in a distribution ? Don't hesitate to let us and +others know! We can avoid duplicated work by publishing it here or +linking to your page. Patches are always welcome and can be posted on +the :doc:`mailing list <MailingList>` to get integrated. We also hand out +git access to people that want to get involved. + +Submitting patches +------------------ + +If you intend to send us patches, please consider the following +guidelines: + +* Prefer small & digestible over long "all in one" patches. +* No MIME, no links, no compression, no attachments. Just plain text + (patches are to be sent inline). +* Patches sent to the mailing list should include "PATCH" in the + subject to make it easier to distinguish between patches and + discussions. +* The mail's subject will become the first line in the commit message. + The body contains the longer patch description and the patch (unified + format) itself. Please also specify the target branch (e.g. batctl, + batman-adv, etc) at the beginning of the subject line. +* Add a "Signed-off-by: Your Name <you(a)example.com>" line to the patch + message to make the ownership of the patch clear. +* Patches for B.A.T.M.A.N. Advanced need to follow the linux kernel + coding style closely (use checkpatch.pl to verify your patch) as well as + the linux "how to submit patches" guidelines (search for the term + SubmitPatches to find thorough documentation). +* Check it using static analysis tools like + `sparse <https://sparse.wiki.kernel.org/>`__ (cgcc) and + `cppcheck <http://cppcheck.sourceforge.net/>`__ +* Patches against the batman-adv main branch must be formatted using + +:: + + git format-patch $BASECOMMIT + ++ or an equivalent tool (like ``b4``) ++ +- README, manpage and sysfs-class-net-\* must be updated together with + the related source change +- Add or update kerneldoc to functions and structures you add or + modify. +- batman-adv changes affecting batctl have to be send with the batctl + patches in the same patchset - - it is recommended to use \`git send-email\` to send the mails to the - mailinglist ++- it is recommended to use `b4 <https://b4.docs.kernel.org/>`__ to send the patch mails to the mailinglist - but plain ``git send-email`` is also fine. +- An exemplary good submission you may want to look at can be found + here: + https://patchwork.open-mesh.org/project/b.a.t.m.a.n./patch/1261051915-13960… diff --cc open-mesh/MailingList.rst index 24783d58,00000000..47268237 mode 100644,000000..100644 --- a/open-mesh/MailingList.rst +++ b/open-mesh/MailingList.rst @@@ -1,18 -1,0 +1,20 @@@ +.. SPDX-License-Identifier: GPL-2.0 + +Mailing List +============ + +You can subscribe to our Mailing Lists +`here <https://lists.open-mesh.org/>`__. You can also send an E-Mail +without subscription to b.a.t.m.a.n(a)lists.open-mesh.org, but keep in +mind that this message will have to be accepted manually (and this can +take some time). + +*Note*: HTML email will be rejected - just plain text is allowed (this +cuts the rate of SPAM mails dramatically). + ++And please follow the `Mailing list etiquette <https://subspace.kernel.org/etiquette.html>`__. ++ +Old messages can be read in the `B.A.T.M.A.N. +archives <https://lists.open-mesh.org/mailman3/hyperkitty/list/b.a.t.m.a.n@lists.open…>`__. +Or via the various subscription (or mirror) methods from +`lore.kernel.org <https://lore.kernel.org/batman>`__

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits