commits July 2017

commits@lists.open-mesh.org

1 participants
1317 discussions

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Release-todo (7088db77)
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 7088db77771bf8de36893c96b0475fcede811a3e Author: Simon Wunderlich <sw(a)simonwunderlich.de> Date: Sun Mar 21 18:40:19 2010 +0000 doc: batman-adv/Release-todo >--------------------------------------------------------------- 7088db77771bf8de36893c96b0475fcede811a3e batman-adv/Release-todo.textile | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/batman-adv/Release-todo.textile b/batman-adv/Release-todo.textile index 893c13a2..44a09f18 100644 --- a/batman-adv/Release-todo.textile +++ b/batman-adv/Release-todo.textile @@ -9,9 +9,9 @@ This page contains a checklist of things that need to be done for a release. * [ ] make sure all code contains the release version strings * [ ] update copyright years (if needed) * [ ] remove dead code (if any) - * [ ] svn tag release - * [ ] change version strings inside the trunk - + * [ ] svn/git tag release + * [-] change version strings inside the trunk + * [ ] check against kernel versions '''Documentation'''

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Release-todo (67e23772)
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 67e23772648bf7e98d60293400b1f03b18341031 Author: Simon Wunderlich <sw(a)simonwunderlich.de> Date: Sun Mar 21 20:53:11 2010 +0000 doc: batman-adv/Release-todo >--------------------------------------------------------------- 67e23772648bf7e98d60293400b1f03b18341031 batman-adv/Release-todo.textile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/batman-adv/Release-todo.textile b/batman-adv/Release-todo.textile index 9f10c600..c869ae95 100644 --- a/batman-adv/Release-todo.textile +++ b/batman-adv/Release-todo.textile @@ -11,11 +11,11 @@ This page contains a checklist of things that need to be done for a release. * [x] remove dead code (if any) * [ ] svn/git tag release * [ ] change version strings inside the trunk - * [ ] check against kernel versions + * [x] check against kernel versions '''Documentation''' - * [ ] build changelog + * [x] build changelog * [ ] update README * [ ] write release announcement

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Download: update links for 0.2.1 release (53be6010)
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 53be601017109eaa9035b37e690ae8ee4de0f7a3 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Mon Mar 22 23:22:57 2010 +0000 doc: open-mesh/Download: update links for 0.2.1 release >--------------------------------------------------------------- 53be601017109eaa9035b37e690ae8ee4de0f7a3 open-mesh/Download.textile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/open-mesh/Download.textile b/open-mesh/Download.textile index 69f1d824..752eb4f6 100644 --- a/open-mesh/Download.textile +++ b/open-mesh/Download.textile @@ -4,8 +4,8 @@ We are currently working on different branches. To get the details about the dif We are offering sources and precompiled batmand binaries and packages for different platforms and for the [http://downloads.open-mesh.org/batman/stable/ stable] and the [http://downloads.open-mesh.org/batman/development/ development] branch. However, please use the stable branch for your public infrastructure unless you know exactly what you are doing and are prepared for the big unknown. A kernel module needs to be linked against the exact kernel headers you are using, therefore we are unable to provide precompiled binaries for batman-adv. === Download Released Source Code === - * The latest version of [wiki:batman-adv batman-adv] is [http://downloads.open-mesh.org/batman/stable/sources/batman-adv-kernelland/… batman-adv-kernelland-0.2.tar.gz] [http://downloads.open-mesh.org/batman/stable/sources/batman-adv-kernelland/… md5] [http://downloads.open-mesh.org/batman/stable/sources/batman-adv-kernelland/… sha1] [http://downloads.open-mesh.org/batman/stable/sources/batman-adv-kernelland/… asc] - * The latest version of batctl (management and control tool for batman-adv) is [http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-0.2.tar.… batctl-0.2.tar.gz] [http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-0.2.tar.… md5] [http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-0.2.tar.… sha1] [http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-0.2.tar.… asc] + * The latest version of [wiki:batman-adv batman-adv] is [http://downloads.open-mesh.org/batman/stable/sources/batman-adv-kernelland/… batman-adv-kernelland-0.2.1.tar.gz] [http://downloads.open-mesh.org/batman/stable/sources/batman-adv-kernelland/… md5] [http://downloads.open-mesh.org/batman/stable/sources/batman-adv-kernelland/… sha1] [http://downloads.open-mesh.org/batman/stable/sources/batman-adv-kernelland/… asc] + * The latest version of batctl (management and control tool for batman-adv) is [http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-0.2.1.ta… batctl-0.2.1.tar.gz] [http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-0.2.1.ta… md5] [http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-0.2.1.ta… sha1] [http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-0.2.1.ta… asc] * The latest stable version of batmand is [http://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.ta… batman-0.3.2.tar.gz] [http://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.ta… md5] [http://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.ta… sha1] [http://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.ta… asc] * The latest version of the vis server for the batmand (package not needed for batman-adv) is [http://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.gz vis-0.3.2.tar.gz] [http://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.g… md5] [http://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.g… sha1] [http://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.g… asc]

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Release-todo (89b9189f)
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 89b9189ffe415672307b896732a7ceed99bfb547 Author: Simon Wunderlich <sw(a)simonwunderlich.de> Date: Sun Mar 21 18:38:28 2010 +0000 doc: batman-adv/Release-todo >--------------------------------------------------------------- 89b9189ffe415672307b896732a7ceed99bfb547 batman-adv/Release-todo.textile | 32 ++++++++++++++++---------------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/batman-adv/Release-todo.textile b/batman-adv/Release-todo.textile index 70ea6b62..893c13a2 100644 --- a/batman-adv/Release-todo.textile +++ b/batman-adv/Release-todo.textile @@ -6,30 +6,30 @@ This page contains a checklist of things that need to be done for a release. '''Code''' - * [x] make sure all code contains the release version strings - * [x] update copyright years (if needed) - * [x] remove dead code (if any) - * [x] svn tag release - * [x] change version strings inside the trunk + * [ ] make sure all code contains the release version strings + * [ ] update copyright years (if needed) + * [ ] remove dead code (if any) + * [ ] svn tag release + * [ ] change version strings inside the trunk '''Documentation''' - * [x] build changelog - * [x] update README - * [x] write release announcement + * [ ] build changelog + * [ ] update README + * [ ] write release announcement '''Release''' - * [x] build package tar.gz (replace symlinks with real files) and generate checksums - * [x] build stable binary packages - * [x] move packages/checksums to ?? / create symlinks ?? - * [x] update download links in the trac downloads page - * [x] send release mail - * [x] update IRC channel topic + * [ ] build package tar.gz (replace symlinks with real files) and generate checksums + * [ ] build stable binary packages + * [ ] move packages/checksums to ?? / create symlinks ?? + * [ ] update download links in the trac downloads page + * [ ] send release mail + * [ ] update IRC channel topic '''Distributions''' - * [x] update openwrt package - * [x] inform batman package maintainer + * [ ] update openwrt package + * [ ] inform batman package maintainer

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Wiki (197963d8)
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 197963d82f54826031ce7c910bfbb3e0a8291877 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Mon Mar 22 04:22:30 2010 +0000 doc: batman-adv/Wiki >--------------------------------------------------------------- 197963d82f54826031ce7c910bfbb3e0a8291877 batman-adv/Wiki.textile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/batman-adv/Wiki.textile b/batman-adv/Wiki.textile index 36d0ba72..14c59583 100644 --- a/batman-adv/Wiki.textile +++ b/batman-adv/Wiki.textile @@ -16,7 +16,7 @@ Pros: * easy integration of attached networks (no manual HNA fiddling), just put the bat0 in the bridge with your other devices. You can for example build a roaming network of Access Points with this technique. * Not affected by your Firewall (but you can secure the payload traffic, of course) Cons: - * no gateway handling inside of B.A.T.M.A.N. (DHCP/IPv6 autoconf/static routes will work but B.A.T.M.A.N. won't help to choose the best gateway for you) + * ~~no gateway handling inside of B.A.T.M.A.N. (DHCP/IPv6 autoconf/static routes will work but B.A.T.M.A.N. won't help to choose the best gateway for you)~~ (the upcoming batman-adv 0.3 supports advanced gateway handling) === batctl (former battools) === Since the nodes participating in the B.A.T.M.A.N. Advanced switch are @@ -29,7 +29,7 @@ Further information can be found in the enclosed README file. === Userland vs Kernelland === The userland implementation of batman-advanced was a proof of concept implementation to verify that the concept is -working. Unfortunately, switching packets in userland is very expensive in terms of cycles, as each packet has to be +working. Unfortunately, switching packets in userland is very expensive in terms of CPU 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. The userland remains unmaintained and has been removed from the subversion repository.

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Release-todo (13d74f5a)
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 13d74f5a58017dfdb4c307b4800bd80378f77868 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Mon Mar 22 23:24:23 2010 +0000 doc: batman-adv/Release-todo >--------------------------------------------------------------- 13d74f5a58017dfdb4c307b4800bd80378f77868 batman-adv/Release-todo.textile | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/batman-adv/Release-todo.textile b/batman-adv/Release-todo.textile index 5f6afebc..3cb90e18 100644 --- a/batman-adv/Release-todo.textile +++ b/batman-adv/Release-todo.textile @@ -9,7 +9,7 @@ This page contains a checklist of things that need to be done for a release. * [x] make sure all code contains the release version strings * [x] update copyright years (if needed) * [x] remove dead code (if any) - * [ ] svn/git tag release + * [x] svn/git tag release * [x] change version strings inside the trunk * [x] check against kernel versions @@ -22,10 +22,10 @@ This page contains a checklist of things that need to be done for a release. '''Release''' - * [ ] build package tar.gz (replace symlinks with real files) and generate checksums + * [x] build package tar.gz (replace symlinks with real files) and generate checksums * [ ] build stable binary packages - * [ ] move packages/checksums to ?? / create symlinks ?? - * [ ] update download links in the trac downloads page + * [x] move packages/checksums to ?? / create symlinks ?? + * [x] update download links in the trac downloads page * [ ] send release mail * [ ] update IRC channel topic

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Gsoc2010-ideas: nah, Turing is only indirectly involved afaik (8eafc789)
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 8eafc789796c85a679207ec315bad9f33d20d0e5 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Wed Mar 10 20:03:42 2010 +0000 doc: open-mesh/Gsoc2010-ideas: nah, Turing is only indirectly involved afaik >--------------------------------------------------------------- 8eafc789796c85a679207ec315bad9f33d20d0e5 open-mesh/Gsoc2010-ideas.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/Gsoc2010-ideas.textile b/open-mesh/Gsoc2010-ideas.textile index e7ecca01..e27f099b 100644 --- a/open-mesh/Gsoc2010-ideas.textile +++ b/open-mesh/Gsoc2010-ideas.textile @@ -3,7 +3,7 @@ * Routing and networking knowledge in general * Programming language: C = Recommended and/or useful = -These things are not a prerequisite but might be very useful and/or have to be learned turing the GSoC anyway. +These things are not a prerequisite but might be very useful and/or have to be learned during the GSoC anyway. * [[http://www.kernel.org/doc/Documentation/CodingStyle Linux kernel coding style]] * Reading the documentation of the algorithms: [[http://gitorious.org/batman-adv-doc batman-adv-doc]] [[http://tools.ietf.org/html/draft-wunderlich-openmesh-manet-routing-00 batman-rfc-draft]] (used in the 'old' batmand) * Being able to use virtual machines for debugging (i.e. qemu)

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Release-todo (f49eaee5)
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 f49eaee5e848b9c5bea7900e49bcb95b711bec52 Author: Simon Wunderlich <sw(a)simonwunderlich.de> Date: Sun Mar 21 20:28:19 2010 +0000 doc: batman-adv/Release-todo >--------------------------------------------------------------- f49eaee5e848b9c5bea7900e49bcb95b711bec52 batman-adv/Release-todo.textile | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/batman-adv/Release-todo.textile b/batman-adv/Release-todo.textile index 44a09f18..9f10c600 100644 --- a/batman-adv/Release-todo.textile +++ b/batman-adv/Release-todo.textile @@ -6,11 +6,11 @@ This page contains a checklist of things that need to be done for a release. '''Code''' - * [ ] make sure all code contains the release version strings - * [ ] update copyright years (if needed) - * [ ] remove dead code (if any) + * [x] make sure all code contains the release version strings + * [x] update copyright years (if needed) + * [x] remove dead code (if any) * [ ] svn/git tag release - * [-] change version strings inside the trunk + * [ ] change version strings inside the trunk * [ ] check against kernel versions '''Documentation'''

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Gsoc2010-ideas: escape OpenStreetMap/OpenLayers, fix level of headings (c96925e7)
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 c96925e77194269f3ecaaa59fd8017745b2a3523 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Wed Mar 10 19:47:47 2010 +0000 doc: open-mesh/Gsoc2010-ideas: escape OpenStreetMap/OpenLayers, fix level of headings >--------------------------------------------------------------- c96925e77194269f3ecaaa59fd8017745b2a3523 open-mesh/Gsoc2010-ideas.textile | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/open-mesh/Gsoc2010-ideas.textile b/open-mesh/Gsoc2010-ideas.textile index e126a0be..e7ecca01 100644 --- a/open-mesh/Gsoc2010-ideas.textile +++ b/open-mesh/Gsoc2010-ideas.textile @@ -33,32 +33,32 @@ The traffic B.A.T.M.A.N. IV generates to discover the best path through the netw Fast moving nodes always have the problem of adjusting their routing information in time. They can choose to send more routing information, so that their environment can adjust to them but stationary nodes won't do the same and increase the mobile node's adaption time greatly. However, when a B.A.T.M.A.N. node detects that his local environment changed quickly he will enter the starvation mode. In this mode the node will actively try to confirm a working route as fast as possible by sending a "batman ping" to its new neighbors. Each B.A.T.M.A.N. neighbor will try to forward the message to its destination, once arrived there it will travel back. If the mobile node receives the reply it can change its route towards the new neighbor without waiting for normal OGM flooding as the route has been verified. The goal of this project is to implement the starving mode together with the "batman ping". -= Optimize multicast performance = +== Optimize multicast performance == '''Brief description:''' Avoid broadcasting multicast traffic to nodes not belonging to a certain multicast group. Multicast packets would have a great advantage especially in wireless mesh networks: The number of recipients of multicast packets (i.e. for zeroconf service announcements or audio/video streams) is a lot higher then with unicast packets. batman-adv currently handles multicast packets the same way as broadcast packets, they simply get flooded through the mesh network. Instead, those packets should be flooded on a subgraph containing the nodes of a certain multicast group and other connecting nodes only. -= Dynamic OGM intervals = +== Dynamic OGM intervals == '''Brief description:''' A batman-adv node shall select originator interval rates according to the dense and dynamics in its closer environment. Depending on the usage scenario, people can adjust the bandwidth being used for batman-adv's route finding algorithms. Usually people were advised to increase the originator interval if the mesh network is small but needs fast route refresh rates or to decrease it if the mesh network is mostly a static setup with a lot of nodes. It would be great if a batman-adv node could determine the dynamics of the mesh network it is currently participating in on its own so that this option would not have to be administrated from a person anymore. For instance in combination with the 'B.A.T.M.A.N. protocol overhead reduction' project, the local broadcasts could be automatically increased if there are not that many direct neighbors. -= More batctl ping/traceroute options = +== More batctl ping/traceroute options == '''Brief description:''' Add useful options for administrating a mesh network to batctl. batctl is the nicer frontend for configuration and debugging batman-adv. There are still some options that could be added like showing the MTU of hops with traceroute along a path to make it easier to spot MTU issues. Or outgoing interface selection to be able to manually probe the way and quality of an alternative path. Feature proposals that make the administration of a complex mesh network more easy are welcome. -= Live VIS in map = +== Live VIS in map == '''Brief description:''' Building tools that visualize the dot output of the vis server with additional gps coordinates on a map. -With every new technology, a bridge to non-technical people should be provided as well. batman-adv is being used in routers of every-day users, that do not have an insight in the B.A.T.M.A.N. routing protocol itself, nevertheless a good visualization can widely increase the acceptance of a new technology and get young people interested in it. batman-adv has a built in vis-server which produces a raw dot-file when activated. With the help of graphviz-tools, those dot-files can be rendered as graphs which are still more interesting for 'technical' people. It would be great to have a tool that maps the information provided by the dot-output and additional geo coordinates in Google-Maps or OpenStreetMap (OpenLayers) in realtime. Then 'normal' people could find out and solve dead zones without technical support all on their own without having to use fancy command line tools. This feature would be useful for anyone administrating (parts of) a mesh network. +With every new technology, a bridge to non-technical people should be provided as well. batman-adv is being used in routers of every-day users, that do not have an insight in the B.A.T.M.A.N. routing protocol itself, nevertheless a good visualization can widely increase the acceptance of a new technology and get young people interested in it. batman-adv has a built in vis-server which produces a raw dot-file when activated. With the help of graphviz-tools, those dot-files can be rendered as graphs which are still more interesting for 'technical' people. It would be great to have a tool that maps the information provided by the dot-output and additional geo coordinates in Google-Maps or !OpenStreetMap (!OpenLayers) in realtime. Then 'normal' people could find out and solve dead zones without technical support all on their own without having to use fancy command line tools. This feature would be useful for anyone administrating (parts of) a mesh network. -= Multiple interfaces per node support in Mesh3D = +== Multiple interfaces per node support in Mesh3D == '''Brief description:''' Adapting Mesh3D to handle the new visualization format features from current batman-adv. Mesh 3D is an application written in C and maintained by one of the batman-developers which is able draw a 3 dimensional graph from batman's vis output in dot-format. The latest additions in batman-adv's vis output that now features a differentiated visualization, in that interface connections between nodes are now being shown separately. This new format feature has not been ported to Mesh3D yet. Also a concept for visualizing overlapping links in Mesh3D would probably have to be planed (adding transparency to Mesh3D for instance). -= Multiple switch ports for redundancy = +== Multiple switch ports for redundancy == '''Brief description:''' Allow multiple bridge uplinks to wired networks It is often desired to have multiple uplinks to a (wired) switched network where the B.A.T.M.A.N. protocol is not used. This may be a data center or a core network where multiple or redundant connections are needed. However if the Mesh network device and Ethernet device are bridged on multiple nodes, bridge loops are created. Traditional measures like (R)STP don't help in this situation as they may disable the (good) Ethernet Links. A solution should be developed where we can use multiple (redundant) uplinks to the same core switch network while effectively avoiding switch loops. \ No newline at end of file

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Gsoc2010-ideas: correct smaller typographical errors (7446588d)
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 7446588d9ec192b9b8a30050a488a9fea49a96dd Author: Sven Eckelmann <sven(a)narfation.org> Date: Tue Mar 9 00:31:19 2010 +0000 doc: open-mesh/Gsoc2010-ideas: correct smaller typographical errors >--------------------------------------------------------------- 7446588d9ec192b9b8a30050a488a9fea49a96dd open-mesh/Gsoc2010-ideas.textile | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/open-mesh/Gsoc2010-ideas.textile b/open-mesh/Gsoc2010-ideas.textile index 17df3b55..85c68c72 100644 --- a/open-mesh/Gsoc2010-ideas.textile +++ b/open-mesh/Gsoc2010-ideas.textile @@ -16,7 +16,7 @@ These things are not a prerequisite but might be very useful and/or have to be l == link layer fragmentation / compression == '''Brief description:''' Introducing link-layer fragmentation and header compression to offer alternative packet overhead solutions. -Due to the packet encapsulation performed on each and every payload packet going through the mesh a small overhead is introduced. This overhead (24 bytes at the moment) must be dealt with by the admins deploying the batman-adv mesh. The most common solution is to increase the maximum packet size on all mesh interfaces to maintain the standard MTU of 1500 bytes on all client devices. While this works in most cases it does not work for everyone. Some devices / drivers don't support or allow bigger packets. Alternatively, each client has to reduce its MTU to 1476 bytes which is often not manageable. This project shall address the issue by either compressing the payload packets (e.g. VJ compression) and/or implement a leightweight link layer fragmentation and/or develop another solution. +Due to the packet encapsulation performed on each and every payload packet going through the mesh a small overhead is introduced. This overhead (24 bytes at the moment) must be dealt with by the admins deploying the batman-adv mesh. The most common solution is to increase the maximum packet size on all mesh interfaces to maintain the standard MTU of 1500 bytes on all client devices. While this works in most cases it does not work for everyone. Some devices / drivers don't support or allow bigger packets. Alternatively, each client has to reduce its MTU to 1476 bytes which is often not manageable. This project shall address the issue by either compressing the payload packets (e.g. VJ compression) and/or implement a lightweight link layer fragmentation and/or develop another solution. == forward error correction == '''Brief description:''' Forward error correction to avoid retransmissions in the mesh network. @@ -24,7 +24,7 @@ Due to the packet encapsulation performed on each and every payload packet going Wireless networks rely on a lossy transport medium - even under optimal conditions packets get lost and have to be retransmitted. This comes at an even greater cost since the air is a shared medium (only one participant can transmit data at any given time) retransmissions have a severe impact on the network's performance. In addition to the packets which have to travel over several hops towards their destination, higher layer protocols (e.g. TCP) expect ACK packets to travel back over the chain of connected mesh nodes otherwise the transmission starts anew. This project aims to avoid retransmissions by implementing a packet forward correction for the batman-adv payload packets. A parity packet would be injected into the packet flow which allows the receiving batman-adv node to calculate & deliver the lost packet without further retransmissions. The parity packet rate can by dynamically adjusted depending on the link quality towards the final destination. == B.A.T.M.A.N. protocol overhead reduction == -'''Brief description:''' Split the currently used OGM packets into two seperate types to reduce the amount of packets flooded in the neighborhood. +'''Brief description:''' Split the currently used OGM packets into two separate types to reduce the amount of packets flooded in the neighborhood. The traffic B.A.T.M.A.N. IV generates to discover the best path through the network is quite low compared to other protocols, but especially when B.A.T.M.A.N. has many single hop neighbors which rebroadcast each others OGMs we see room for improvements. The project shall optimize the flooding algorithm by splitting the originator message into two different message types. The OGM will remain but only be used to flood the TQ throughout the network. The new message type (a name needs to be found) will contain the link qualities of the single hop neighbors only. This message won't be rebroadcasted and just reaches the local neighborhood. These local message can be sent much more often than the global TQ messages and thus reduce the traffic [nearly just create a linear growth of traffic with more nodes in the local neighborhood instead of a squared amount]. @@ -41,22 +41,22 @@ Multicast packets would have a great advantage especially in wireless mesh netwo = Dynamic OGM intervals = '''Brief description:''' A batman-adv node shall select originator interval rates according to the dense and dynamics in its closer environment. -Depending on the usage scenario, people can adjust the bandwidth being used for batman-adv's route finding algorithms. Usually people were advised to increase the originator interval if the mesh network is small but needs fast route refresh rates or to decrease it if the mesh network is mostly a static setup with a lot of nodes. It would be great if a batman-adv node could determine the dynamics of the mesh network it is currently participating in on its own so that this option would not have to be adminstrated from a person anymore. For instance in combination with the 'B.A.T.M.A.N. protocol overhead reduction' project, the local broadcasts could be automatically increased if there are not that many direct neighbours. +Depending on the usage scenario, people can adjust the bandwidth being used for batman-adv's route finding algorithms. Usually people were advised to increase the originator interval if the mesh network is small but needs fast route refresh rates or to decrease it if the mesh network is mostly a static setup with a lot of nodes. It would be great if a batman-adv node could determine the dynamics of the mesh network it is currently participating on its own so that this option would not have to be administrated from a person anymore. For instance in combination with the 'B.A.T.M.A.N. protocol overhead reduction' project, the local broadcasts could be automatically increased if there are not that many direct neighbors. = More batctl ping/traceroute options = -'''Brief description:''' Add useful options for adminstrating a mesh network to batctl. +'''Brief description:''' Add useful options for administrating a mesh network to batctl. -batctl is the nicer fontend for configurating and debugging batman-adv. There are still some options that could be added like showing the MTU of hops with traceroute along a path to make it easier to spot MTU issues. Or outgoing interface selection to be able to manually probe the way and quality of an alternative path. Feature proposals that make the administration of a complex mesh network more easy are welcome. +batctl is the nicer frontend for configuration and debugging batman-adv. There are still some options that could be added like showing the MTU of hops with traceroute along a path to make it easier to spot MTU issues. Or outgoing interface selection to be able to manually probe the way and quality of an alternative path. Feature proposals that make the administration of a complex mesh network more easy are welcome. = Live VIS in map = -'''Brief description:''' Building tools that visualise the dot output of the vis server with additinal gps coordinates on a map. +'''Brief description:''' Building tools that visualize the dot output of the vis server with additional gps coordinates on a map. -With every new technology, a bridge to non-technical people should be provided as well. batman-adv is being used in routers of every-day users, that do not have an insight in the B.A.T.M.A.N. routing protocol itself, nevertheless a good visualisation can widely increase the acceptance of a new technology and get young people interested in it. batman-adv has a built in vis-server which produces a raw dot-file when activated. With the help of graphviz-tools, those dot-files can be rendered as graphs which are still more interesting for 'technical' people. It would be great to have a tool that maps the information provided by the dot-output and additional geo coordinates in Google-Maps or OpenStreetMap (OpenLayers) in realtime. Then 'normal' people could then find out and solve dead zones without technical support all on their own without having to be able to use fancy command line tools. This feature would be useful for anyone administrating (parts of) a mesh network. +With every new technology, a bridge to non-technical people should be provided as well. batman-adv is being used in routers of every-day users, that do not have an insight in the B.A.T.M.A.N. routing protocol itself, nevertheless a good visualization can widely increase the acceptance of a new technology and get young people interested in it. batman-adv has a built in vis-server which produces a raw dot-file when activated. With the help of graphviz-tools, those dot-files can be rendered as graphs which are still more interesting for 'technical' people. It would be great to have a tool that maps the information provided by the dot-output and additional geo coordinates in Google-Maps or OpenStreetMap (OpenLayers) in realtime. Then 'normal' people could then find out and solve dead zones without technical support all on their own without having to be able to use fancy command line tools. This feature would be useful for anyone administrating (parts of) a mesh network. = Multiple interfaces per node support in Mesh3D = -'''Brief description:''' Adapting Mesh3D to handle the new visualisation format features from current batman-adv. +'''Brief description:''' Adapting Mesh3D to handle the new visualization format features from current batman-adv. -Mesh 3D is an applicaton written in C and maintained by one of the batman-developers which is able draw a 3 dimensional graph from batman's vis output in dot-format. The latest additions in batman-adv's vis ouput that now features a differentiated visualisation, in that interface connections between nodes are now being shown seperately. This new format feature has not been ported to Mesh3D yet. Also a concept for visualising overlapping links in Mesh3D would probably have to be planed (adding transparency to Mesh3D for instance). +Mesh 3D is an application written in C and maintained by one of the batman-developers which is able draw a 3 dimensional graph from batman's vis output in dot-format. The latest additions in batman-adv's vis output that now features a differentiated visualization, in that interface connections between nodes are now being shown separately. This new format feature has not been ported to Mesh3D yet. Also a concept for visualizing overlapping links in Mesh3D would probably have to be planed (adding transparency to Mesh3D for instance). = Multiple switch ports for redundancy = '''Brief description:''' Allow multiple bridge uplinks to wired networks

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits July 2017