commits July 2017

commits@lists.open-mesh.org

1 participants
1317 discussions

Start a nNew thread

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

14 Jul '17

1 0

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

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batmand/Why-starting-batman (b49fc902)
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 b49fc902371b481bde6e742008f8d7d9707fb31d Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Wed Jul 8 11:47:58 2009 +0000 doc: batmand/Why-starting-batman >--------------------------------------------------------------- b49fc902371b481bde6e742008f8d7d9707fb31d batmand/Why-starting-batman.textile | 44 +++++++++++++++++++++++++++++++++++++ 1 file changed, 44 insertions(+) diff --git a/batmand/Why-starting-batman.textile b/batmand/Why-starting-batman.textile new file mode 100644 index 00000000..bc5830dc --- /dev/null +++ b/batmand/Why-starting-batman.textile @@ -0,0 +1,44 @@ + += Why starting B.A.T.M.A.N. ? = [[BR]] + +Often, we are asked why we dropped OLSR in favor of B.A.T.M.A.N. [[BR]] +To explain the initial motivation in those days to start developing a new [[BR]] +routing protocol optimized for lossy networks, we have summarized some [[BR]] +of those reasons in the following list in no particular order. [[BR]] + + * The OLSR protocol as specified in RFC 3626 was not completely [[BR]] + functional in practical scenarios. Tests in 2004 (namely at the [[BR]] + Wizards of OS conference) showed several issues like routing [[BR]] + tables taking a long time to build up and taking no time to break [[BR]] + down again, routing loops and flapping routes. We are not aware [[BR]] + of any mesh network installation in the field that runs the [[BR]] + protocol according to RFC3626 in a productive environment. If you [[BR]] + do, please let us know. [[BR]] + + * The OLSR protocol belongs to the family of link state routing [[BR]] + protocols which calculates a full routing path to all other [[BR]] + nodes in the network. All routing decisions rely on the fact [[BR]] + that every node has (mostly) the same information at any given [[BR]] + time. The more those information differ between the nodes in a [[BR]] + network, the probability of things like routing loops increases. [[BR]] + In our point of view, it is rather difficult to keep such [[BR]] + information synchronized in lossy environments like wireless [[BR]] + mesh networks, in that the effort needed for synchronisation [[BR]] + increases exponentially with each node. [[BR]] + + * The OLSR daemon as it is today (the one which can be [[BR]] + downloaded from www.olsr.org; we will further reference it just [[BR]] + as "OLSR daemon") comes with a lot of extensions / changes [[BR]] + (e.g. the default config disables most of the RFC3626 features as [[BR]] + MPR and enables ETX, !FishEye, etc) that alter the behaviour of [[BR]] + the routing protocol completely (compared to RFC 3626). [[BR]] + Those extensions have been developed by an active community [[BR]] + (Thomas Lopatic & Elektra and the OLSR-NG project later on). [[BR]] + Therefore the OLSR daemon today is not comparable with the [[BR]] + initial OLSR protocol at all, as many things which had been [[BR]] + specified in the RFC 3626 have been modified. Again, [[BR]] + because of our personal experiences, those extensions help [[BR]] + to decrease the problems inherited by the link state algorithm but are [[BR]] + unable to solve it which led to our decision, that it might be better [[BR]] + to try a different approach. [[BR]] +

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Contribute (0585b687)
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 0585b68710eb31b2cf24ed0a5b461ee33108b1bb Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Sat Jul 11 18:02:32 2009 +0000 doc: open-mesh/Contribute >--------------------------------------------------------------- 0585b68710eb31b2cf24ed0a5b461ee33108b1bb open-mesh/Contribute.textile | 34 ++++++++++++++++++++++++++++------ 1 file changed, 28 insertions(+), 6 deletions(-) diff --git a/open-mesh/Contribute.textile b/open-mesh/Contribute.textile index 7d21a3ed..008c665e 100644 --- a/open-mesh/Contribute.textile +++ b/open-mesh/Contribute.textile @@ -1,11 +1,15 @@ = 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 [wiki:MailingList Mailing List]. You can always contact us via [wiki:IRC IRC]. +Thanks for using B.A.T.M.A.N.! If you have suggestions, comments, want to tell us [[BR]] +about your experiences or discuss problems the best thing is always to use the [[BR]] +[wiki:MailingList Mailing List]. You can always contact us via [wiki: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: +If you like this project and you want to take part and/or give something back, [[BR]] +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 [https://dev.open-mesh.org/batman/report Reading the Tickets]. If not, please [https://dev.open-mesh.org/batman/newticket add a new Ticket]. +If you find a bug, please see if the problem is already known in the by [https://dev.open-mesh.org/batman/report Reading the Tickets]. [[BR]] +If not, please [https://dev.open-mesh.org/batman/newticket add a new Ticket]. Please add as much information as possible. In particular interesting are: @@ -33,10 +37,28 @@ There's lots of people that want to know about B.A.T.M.A.N. - help us to spread === 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. +B.A.T.M.A.N. gives much room for research, especially the layer 2 implementation in the [[BR]] +kernel. Get in touch with us to share your ideas. If you write papers we are happy to [[BR]] +publish them here or link to your page. If you are looking for the right topic or [[BR]] +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 [wiki:MailingList mailing list] to get integrated. We also hand out SVN access to people that want to get involved. +You looked in the code ? Fixed bugs ? Added a cool new function ? Integrated B.A.T.M.A.N.[[BR]] +in a distribution ? Don't hesitate to let us and others know! We can avoid duplicated [[BR]] +work by publishing it here or linking to your page. Patches are always welcome and can [[BR]] +be posted on the [wiki:MailingList mailing list] to get integrated. We also hand out SVN [[BR]] +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. + * The mails subject will become the first line in the commit message. The body [[BR]] + contains the longer patch description and the patch (unified format) itself. [[BR]] + Please also specify the target branch (e.g. [batman], [batctl], etc) at the [[BR]] + beginning of the subject line. See the [http://www.open-mesh.org/timeline timeline] for more examples. + * Add a "Signed-off-by: Your Name <you @ example.com>" line to the commit [[BR]] + message to make the ownership of the patch clear.

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Filing: categorizing the userdocs (c75fd9e2)
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 c75fd9e2e6913452609d58acce6578c7deb9dcda Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Sat Jul 11 18:36:18 2009 +0000 doc: open-mesh/Filing: categorizing the userdocs >--------------------------------------------------------------- c75fd9e2e6913452609d58acce6578c7deb9dcda open-mesh/Filing.textile | 30 +++++++++++++++++++++++------- 1 file changed, 23 insertions(+), 7 deletions(-) diff --git a/open-mesh/Filing.textile b/open-mesh/Filing.textile index d5f2082e..bdea5e1a 100644 --- a/open-mesh/Filing.textile +++ b/open-mesh/Filing.textile @@ -1,17 +1,33 @@ === Some documents that might help you: === + +==== B.A.T.M.A.N. concepts ==== + * [wiki:BATMANConcept B.A.T.M.A.N. Concept] - get an overview about B.A.T.M.A.N.'s main concepts + * [http://tools.ietf.org/html/draft-wunderlich-openmesh-manet-routing-00 B.A.T.M.A.N. RFC Draft] - a draft explaining the routing algorithm used in batman 0.2 + * [http://www.open-mesh.org/batman/doc/batman-status.pdf B.A.T.M.A.N. Status] - read about the B.A.T.M.A.N. (June 2007) + + +==== Using the B.A.T.M.A.N. daemon (layer 3) ==== + * [wiki:RoutingVodoo Getting behind the routing vodoo] - learn about the B.A.T.M.A.N. routing table manipulation * [wiki:InternetTuning InternetTuning] - get information how B.A.T.M.A.N. handles internet access and what features it offers * [wiki:DebugOutput Understanding the debug output] - documentation that helps you to understand the debug output * [wiki:VisualizeMesh Visualizing the network] - this document explains how to get fancy graphics of the batman mesh * [wiki:AnnouncingNetworks Announcing networks] - learn how to announce and / or revoke HNA on the fly - * [wiki:Coredump How to get a coredump] - documentation about coredump configuration & retrieval - * [wiki:batman-adv B.A.T.M.A.N. Advanced] - information about the Layer 2 version of B.A.T.M.A.N. - * [http://wiki.hskflashcards.com/index.php?page=B.A.T.M.A.N.+Advanced+on+OpenW… B.A.T.M.A.N. Advanced on OpenWRT] - a tutorial for using B.A.T.M.A.N. Advanced on OpenWRT - * [wiki:the-olsr-story The OLSR story] - this text explains the roots of B.A.T.M.A.N. (Dec 2006) - * [http://tools.ietf.org/html/draft-wunderlich-openmesh-manet-routing-00 B.A.T.M.A.N. RFC Draft] - a draft explaining the routing algorithm used in batman 0.2 + * [http://downloads.open-mesh.org/batman/development/sources/batmand_0.4-alpha… B.A.T.M.A.N. man page] - read the current batman man page online * [http://www.open-mesh.org/batman/doc/batmand_howto.pdf B.A.T.M.A.N. HowTo] - how to compile, install and run batman 0.2 - * [http://www.open-mesh.org/batman/doc/batman-status.pdf B.A.T.M.A.N. Status] - read about the B.A.T.M.A.N. (June 2007) - * [http://downloads.open-mesh.org/batman/development/sources/batmand_0.3.2-bet… B.A.T.M.A.N. man page] - read the current batman man page online * [http://downloads.open-mesh.org/batman/misc/cccamp07-B.A.T.M.A.N._-_Better_A… CCCamp 2007 talk (video)] - Elektra and Marek explain the batman routing algorithm and features of batmand + + +==== Using B.A.T.M.A.N. advanced (layer 2) ==== + + * [wiki:batman-adv B.A.T.M.A.N. Advanced] - information about the Layer 2 version of B.A.T.M.A.N. + * [http://wiki.hskflashcards.com/index.php?page=B.A.T.M.A.N.+Advanced+on+OpenW… B.A.T.M.A.N. Advanced on OpenWRT] - a tutorial for using B.A.T.M.A.N. Advanced on OpenWRT * [http://downloads.open-mesh.org/batman/misc/24C3-Wireless_Kernel_Tweaking.mkv Wireless Kernel Tweaking (video)] - Introduction to batman-advanced by Marek and Simon (also available at [http://video.google.de/videoplay?docid=1355876033101731617 google video]) + + +==== Misc ==== + + * [wiki:Coredump How to get a coredump] - documentation about coredump configuration & retrieval + * [wiki:the-olsr-story The OLSR story] - this text explains the roots of B.A.T.M.A.N. (Dec 2006) +

1 0

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

14 Jul '17

1 0

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

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/BranchesExplained: mark userspace obsolete (a0ba197f)
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 a0ba197fe6ac3cf2409aaeb2f6c4350305601261 Author: Simon Wunderlich <sw(a)simonwunderlich.de> Date: Fri Jun 12 22:58:10 2009 +0000 doc: open-mesh/BranchesExplained: mark userspace obsolete >--------------------------------------------------------------- a0ba197fe6ac3cf2409aaeb2f6c4350305601261 open-mesh/BranchesExplained.textile | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/open-mesh/BranchesExplained.textile b/open-mesh/BranchesExplained.textile index 0d603142..d9148545 100644 --- a/open-mesh/BranchesExplained.textile +++ b/open-mesh/BranchesExplained.textile @@ -23,14 +23,16 @@ Maintainer: Marek Lindner, Simon Wunderlich In April 2007 batman advanced (residing in user space) came to light. 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. It builds a switch of all your nodes and enables you to run any Layer 3 (and Ethernet Layer 2) protocols, like IPv4, IPv6, DHCP, IPX.., on top of it. -Due to the testing we realized that the layer 2 proof of concept implementation in user space suffered from many performance problems. In late 2007 we ported our layer 2 implementation to kernel space in form of a kernel modul. +Due to the testing we realized that the layer 2 proof of concept implementation in user space suffered from many performance problems. In late 2007 we ported our layer 2 implementation to kernel space in form of a kernel module. -=== [wiki:batman-adv batman-adv-userspace] === -Maintainer: Simon Wunderlich, Marek Lindner +=== [wiki:batman-adv batman-adv-userspace] (obsolete)=== +Maintainer: unmaintained batman advanced userspace was the first implementation of the batman-advanced idea, used as proof of concept. However the virtual interface in userspace imposed a significant overhead for low-end wireless access points, so we decided to re-implement batman-advanced as kernel module which is now batman-adv-kernelland. + + === [wiki:batman-adv battools] === Maintainer: Andreas Langer -The battools are a set of debugging tools which work together with our layer 2 implementation (user space and kernel land). You can use them to debug the mesh which proved to be difficult without them. +The battools are a set of debugging tools which work together with our layer 2 implementation. You can use them to debug the mesh which proved to be difficult without them.

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Wiki (b091dbeb)
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 b091dbeb89dc4e4cc008340de38e0515a12fc154 Author: Simon Wunderlich <sw(a)simonwunderlich.de> Date: Fri Jun 12 22:59:42 2009 +0000 doc: batman-adv/Wiki >--------------------------------------------------------------- b091dbeb89dc4e4cc008340de38e0515a12fc154 batman-adv/Wiki.textile | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/batman-adv/Wiki.textile b/batman-adv/Wiki.textile index 6cf92ffd..e5960be4 100644 --- a/batman-adv/Wiki.textile +++ b/batman-adv/Wiki.textile @@ -31,8 +31,7 @@ The userland implementation of batman-advanced was a proof of concept implementa working. Unfortunately, switching packets in userland is very expensive in terms of cycles, as each packet has to be read() and write() to the kernel and back, which limits the sustainable bandwidth especially on low-end devices. To have good support for these devices as well, we implemented batman-adv as a kernel driver, which is now the -preferred version. It can be controlled via the /proc file system and works transparently, offering the same service -and being compatible to the userland version. +preferred version. It can be controlled via the /proc file system and works transparently. The userland remains unmaintained and has been removed from the subversion repository. === Documentation ===

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/BranchesExplained: better remove userland and move info into kernelland part... (ff5c2cbc)
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 ff5c2cbcdc48c82780a0ce3c41d9b6c62def475f Author: Simon Wunderlich <sw(a)simonwunderlich.de> Date: Fri Jun 12 23:02:12 2009 +0000 doc: open-mesh/BranchesExplained: better remove userland and move info into kernelland part... >--------------------------------------------------------------- ff5c2cbcdc48c82780a0ce3c41d9b6c62def475f open-mesh/BranchesExplained.textile | 9 +-------- 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/open-mesh/BranchesExplained.textile b/open-mesh/BranchesExplained.textile index d9148545..519f02f9 100644 --- a/open-mesh/BranchesExplained.textile +++ b/open-mesh/BranchesExplained.textile @@ -23,14 +23,7 @@ Maintainer: Marek Lindner, Simon Wunderlich In April 2007 batman advanced (residing in user space) came to light. 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. It builds a switch of all your nodes and enables you to run any Layer 3 (and Ethernet Layer 2) protocols, like IPv4, IPv6, DHCP, IPX.., on top of it. -Due to the testing we realized that the layer 2 proof of concept implementation in user space suffered from many performance problems. In late 2007 we ported our layer 2 implementation to kernel space in form of a kernel module. - -=== [wiki:batman-adv batman-adv-userspace] (obsolete)=== -Maintainer: unmaintained - -batman advanced userspace was the first implementation of the batman-advanced idea, used as proof of concept. However the virtual interface in userspace imposed a significant overhead for low-end wireless access points, so we decided to re-implement batman-advanced as kernel module which is now batman-adv-kernelland. - - +Batman advanced was first implemented in userspace as proof of concept. However the virtual interface in userspace imposed a significant overhead for low-end wireless access points, so we decided to re-implement batman-advanced as kernel module which is now batman-adv-kernelland. === [wiki:batman-adv battools] === Maintainer: Andreas Langer

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits July 2017