commits July 2017

commits@lists.open-mesh.org

1 participants
1317 discussions

[doc] backup-redmine/2017-07-13, master: doc: batmand/RoutingVodoo (dd04d995)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit dd04d995810389398fa1fdeabc27aaa656c3fcae Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Mar 26 23:35:59 2011 +0000 doc: batmand/RoutingVodoo >--------------------------------------------------------------- dd04d995810389398fa1fdeabc27aaa656c3fcae batmand/RoutingVodoo.textile | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/batmand/RoutingVodoo.textile b/batmand/RoutingVodoo.textile index dee0ccbe..621bd4c4 100644 --- a/batmand/RoutingVodoo.textile +++ b/batmand/RoutingVodoo.textile @@ -1,5 +1,4 @@ - -h2. Getting behind the routing vodoo +h1. Getting behind the routing vodoo With version 0.3 batman became "policy routing" support and thus can use special routing functions provided by the Linux kernel. @@ -7,7 +6,7 @@ With version 0.3 batman became "policy routing" support and thus can use special This document explains its purpose and tries to point out why batman is doing it. Please keep in mind: Normally, you wont have to to anything about it ! Batman will take care of all the routing work but it might prove helpful to understand what batman does and why. ;-) -*Routing tables* +h2. Routing tables Linux provides much more routing tables than just the one you can see with the "route" command. Batman makes use of the feature to spread its routing entries over 4 routing tables. To find out which routing tables are used issue "batmand -i" and watch out for the "rt_table" information: @@ -34,7 +33,7 @@ The "route" command provides access to routing table 254. To see or manipulate t ip route ls table 66 -*Routing rules* +h2. Routing rules Additionally to more routing tables, Linux offers to set routing rules which opens the possibility to control the packet flow. A rule can be based on certain criteria as source IP / destination IP / incoming interface / etc and will always target a routing table. When a new packet comes in, the kernel will follow the rules from the smallest available rule number until a rule is matched. Then the kernel jumps to the routing table which is pointed to by the rule and tries to find a routing entry there. If nothing is found the routing table will be left and the kernel proceeds with the next rule. Issue "batmand -i" to get the rule numbers used by batman: @@ -69,7 +68,7 @@ The next rule means: All packets should go through our "network" (HNA) table. The last rule is similar to the first rule but the kernel will jump to our "unreachable" table. -*What is the purpose of all this ?* +h2. What is the purpose of all this ? * Batman can clearly seperate hosts from announced networks. With a simple lookup you can see whether a node is announced or runs batman. * It allows you and batman to easily delete all batman related table entries because the batman tables are well known and distinct.

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Contribute (73a0fea4)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/BranchesExplained (ce8a78d5)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit ce8a78d573e6343304d976d5b9f5ad55426c32d3 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Mar 26 23:24:08 2011 +0000 doc: open-mesh/BranchesExplained >--------------------------------------------------------------- ce8a78d573e6343304d976d5b9f5ad55426c32d3 open-mesh/BranchesExplained.textile | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/open-mesh/BranchesExplained.textile b/open-mesh/BranchesExplained.textile index 2b3a1744..9d986536 100644 --- a/open-mesh/BranchesExplained.textile +++ b/open-mesh/BranchesExplained.textile @@ -2,7 +2,7 @@ h1. Branches Explained The batman project that started with a basic protocol and a single userspace routing daemon, attracted quite some attention over the years which led to many new ideas and concepts meant to improve the project. These ideas often resulted in proof-of-concept "branches" of which some turned out to be impractical and disappeared but others came to stay. As a consequence different names were created to distinguish these concepts as the name "batman" became a broader term for everything around the project. This page aims to shed some light on all these different names to make it easier to understand the differences. -h3. numbers, numbers +h2. numbers, numbers Whenever Roman numerals (as III or IV) are mentioned they refer to the version of B.A.T.M.A.N.'s routing algorithm and thus describe how the routing information are flooded and how they are handled to make the best routing decision possible. @@ -11,7 +11,7 @@ Arabic numerals are used to distinguish the implementation's version. Next to th Example: batmand 0.2 uses the B.A.T.M.A.N. III routing algorithm. -h3. batmand +h2. batmand The batman userspace daemon has been the first implementation of the B.A.T.M.A.N. routing protocol. In the early stages of the project it allowed us to easily experiment with the design of the protocol but also to be used in real world deployments. It operates on layer 3 (IP layer) and offers everything you would expect from a standard routing daemon. Check our [[UserDocs|docs]] section if you want to learn more about is capabilities. @@ -21,7 +21,7 @@ At the moment the batman daemon lacks development power (this branch is unmainta -h3. BMX +h2. BMX Initially, the BMX branch was used to implement and test new features and concepts to overcome certain limitations of the routing algorithm. It started on the code base of batmand 0.3 but, over time, developed into a completely different direction, so that a re-integration became impossible. @@ -31,7 +31,7 @@ Today, it is an independent project hosted at http://www.bmx6.net. -h3. batman-adv +h2. batman-adv Early 2007 some developers started experimenting with the idea of routing on layer 2 (Ethernet layer) instead of layer 3. As only little knowledge about routing on this low level was available at that time, a first prototype was developed, operating in userspace in form of a daemon but already using layer 2. To differentiate from the layer 3 routing daemon the suffix "adv" (spoken: advanced) was chosen - the batman-adv userspace daemon was born. It uses the routing algorithm of batman 0.3, but instead of sending UDP packets and manipulating routing tables, it provides a virtual network interface and transparently transports packets on its own. @@ -42,7 +42,7 @@ To understand the implications of routing on layer 2, the [[batman-adv|batman-ad -h3. batctl +h2. batctl As batman-adv operates in kernelland a handy tool to manage the module and debug the network became necessary. The batctl tool was created to fill that gap and, since then, has become a valuable companion of batman-adv.

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Contribute (d9f75867)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit d9f75867a899de2a0f2dd9d998f2433802e0cd3a Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Mar 26 23:26:50 2011 +0000 doc: open-mesh/Contribute >--------------------------------------------------------------- d9f75867a899de2a0f2dd9d998f2433802e0cd3a open-mesh/Contribute.textile | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/open-mesh/Contribute.textile b/open-mesh/Contribute.textile index a3445e44..4af71fa0 100644 --- a/open-mesh/Contribute.textile +++ b/open-mesh/Contribute.textile @@ -7,7 +7,7 @@ If you like this project and you want to take part and/or give something back, h -h3. Reporting Bugs +h2. Reporting Bugs If you find a bug, please see if the problem is already known in the by Reading the Tickets: @@ -32,7 +32,7 @@ Please add as much information as possible. In particular interesting are: * your guess what triggered the problem. ;) -h3. Documentation / Feedback +h2. 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: @@ -47,19 +47,19 @@ Write an article about your experience with B.A.T.M.A.N. and have it published h 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. -h3. Research +h2. 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. -h3. Development +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. -h3. Submitting patches +h2. Submitting patches If you intend to send us patches, please consider the following guidelines: @@ -67,12 +67,12 @@ 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. See the "timeline":http://www.open-mesh.org/timeline for more examples. +* 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). * Patches against the batman-adv master branch must be formated using <pre> -git format-patch -M --patience --src-prefix=a/batman-adv/ --dst-prefix=b/batman-adv/ $BASECOMMIT +git format-patch -M --patience $BASECOMMIT </pre> * An exemplary good submission you may want to look at can be found here: https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2009-December/002033.html

1 0

[doc] backup-redmine/2017-07-13, master: doc: batmand/BerlinExperience (4e32db25)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit 4e32db253d86690e3d95c1934c574c6fb5683524 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Mar 26 23:23:09 2011 +0000 doc: batmand/BerlinExperience >--------------------------------------------------------------- 4e32db253d86690e3d95c1934c574c6fb5683524 batmand/BerlinExperience.textile | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/batmand/BerlinExperience.textile b/batmand/BerlinExperience.textile index 966a0b63..3f672a96 100644 --- a/batmand/BerlinExperience.textile +++ b/batmand/BerlinExperience.textile @@ -1,7 +1,7 @@ -= B.A.T.M.A.N. in Berlin = +h1. B.A.T.M.A.N. in Berlin -The first experimental setups using the B.A.T.M.A.N. routing protocol daemon have actually started just in parallel with the advent of the first available implementation. -This was also due to the fact that in 2005 most of the dedicated B.A.T.M.A.N. developers lived in Berlin and always wanted to develop a protocol out of practical experience instead of theory and paper work. + +The first experimental setups using the B.A.T.M.A.N. routing protocol daemon have actually started just in parallel with the advent of the first available implementation. This was also due to the fact that in 2005 most of the dedicated B.A.T.M.A.N. developers lived in Berlin and always wanted to develop a protocol out of practical experience instead of theory and paper work. Since then the number of nodes running B.A.T.M.A.N. and OLSR in parallel have constantly grown and the first mesh-node administrators have now started to run a B.A.T.M.A.N.-only stack. @@ -9,7 +9,7 @@ Today, the routing table typically lists entries to about 50 other B.A.T.M.A.N. The following links provide a collection to miscellaneous insides to various Berlin-B.A.T.M.A.N. setups. - * B.A.T.M.A.N. at the Emmaus-Kirchturm, Lausitzer Platz and other nodes administrated by Lui are accessible via portforwarding at http://freifunk.schmudde.com/ - * Backgound about the B.A.T.M.A.N. initiative at hyperactive Freifunk Berlin Nord Ost community ( http://www.freifunk-bno.de/ ) is provided at http://www.freifunk-bno.de/content/view/67/28/ and http://www.freifunk-bno.de/component/option,com_smf/Itemid,88/topic,26.0/ - * Another initiative launching B.A.T.M.A.N. only setup at the Boxhagener Platz in Berlin Friedrichshain is documented here: http://florianschmoelz.wordpress.com/tag/batman/ +* B.A.T.M.A.N. at the Emmaus-Kirchturm, Lausitzer Platz and other nodes administrated by Lui are accessible via portforwarding at http://freifunk.schmudde.com/ +* Backgound about the B.A.T.M.A.N. initiative at hyperactive Freifunk Berlin Nord Ost community ( http://www.freifunk-bno.de/ ) is provided at http://www.freifunk-bno.de/content/view/67/28/ and http://www.freifunk-bno.de/component/option,com_smf/Itemid,88/topic,26.0/ +* Another initiative launching B.A.T.M.A.N. only setup at the Boxhagener Platz in Berlin Friedrichshain is documented here: http://florianschmoelz.wordpress.com/tag/batman/

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Download (5ceab4ed)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/BranchesExplained (790111a5)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Tweaking (ceb5bae2)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Contribute (587c4373)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Building-with-openwrt (09b8bf11)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits July 2017