commits July 2017

commits@lists.open-mesh.org

1 participants
1317 discussions

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

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Gsoc2010-ideas: revert removed "in" (a57c6c75)
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 a57c6c75c97b5668a786c7904f18f8be8ec9b5fa Author: Sven Eckelmann <sven(a)narfation.org> Date: Wed Mar 10 19:43:55 2010 +0000 doc: open-mesh/Gsoc2010-ideas: revert removed "in" >--------------------------------------------------------------- a57c6c75c97b5668a786c7904f18f8be8ec9b5fa 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 1ffb37d6..e126a0be 100644 --- a/open-mesh/Gsoc2010-ideas.textile +++ b/open-mesh/Gsoc2010-ideas.textile @@ -41,7 +41,7 @@ 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 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. +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 = '''Brief description:''' Add useful options for administrating a mesh network to batctl.

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Gsoc2010-ideas: adding ideas list for the GSoC 2010 (107b362e)
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 107b362e4ec446685ab421e7bc968f567170178a Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Tue Mar 9 00:20:08 2010 +0000 doc: open-mesh/Gsoc2010-ideas: adding ideas list for the GSoC 2010 >--------------------------------------------------------------- 107b362e4ec446685ab421e7bc968f567170178a open-mesh/Gsoc2010-ideas.textile | 64 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 64 insertions(+) diff --git a/open-mesh/Gsoc2010-ideas.textile b/open-mesh/Gsoc2010-ideas.textile new file mode 100644 index 00000000..17df3b55 --- /dev/null +++ b/open-mesh/Gsoc2010-ideas.textile @@ -0,0 +1,64 @@ += Requirements for students = + * Excited interest in Mesh networking technologies + * 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. + * [[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) + * Being able to install a mesh network with OpenWRT and batman-adv + * Kernel coding experiences (especially with how to handle and avoid memory management/race conditions/deadlocks) + * monitoring packet flow (using tcpdump / wireshark + [[http://gitorious.org/wireshark-batman-plugins/wireshark-batman-adv wireshark-batman-adv dissector]] + += Ideas = + +== 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. + +== forward error correction == +'''Brief description:''' Forward error correction to avoid retransmissions in the mesh network. + +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. + +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]. + +== B.A.T.M.A.N. protocol convergence speed == +'''Brief description:''' Implement a fast changing environment detection algorithm to let mobile nodes adapt to their new surroundings faster. + +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 = +'''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 = +'''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. + += More batctl ping/traceroute options = +'''Brief description:''' Add useful options for adminstrating 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. + += Live VIS in map = +'''Brief description:''' Building tools that visualise the dot output of the vis server with additinal 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. + += Multiple interfaces per node support in Mesh3D = +'''Brief description:''' Adapting Mesh3D to handle the new visualisation 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). + += 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: nah, Turing is only indirectly involved afaik (1c39d6ed)
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 1c39d6edb0228c3602f153bd7a27185837a03695 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 >--------------------------------------------------------------- 1c39d6edb0228c3602f153bd7a27185837a03695 open-mesh/Gsoc2010-ideas.textile | 92 ++++++++++++++++++++++++++-------------- 1 file changed, 59 insertions(+), 33 deletions(-) diff --git a/open-mesh/Gsoc2010-ideas.textile b/open-mesh/Gsoc2010-ideas.textile index e27f099b..3bad2e65 100644 --- a/open-mesh/Gsoc2010-ideas.textile +++ b/open-mesh/Gsoc2010-ideas.textile @@ -1,64 +1,90 @@ -= Requirements for students = - * Excited interest in Mesh networking technologies - * Routing and networking knowledge in general - * Programming language: C -= Recommended and/or useful = + +h1. Requirements for students + +* Excited interest in Mesh networking technologies +* Routing and networking knowledge in general +* Programming language: C + +h1. Recommended and/or useful + 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) - * Being able to install a mesh network with OpenWRT and batman-adv - * Kernel coding experiences (especially with how to handle and avoid memory management/race conditions/deadlocks) - * monitoring packet flow (using tcpdump / wireshark + [[http://gitorious.org/wireshark-batman-plugins/wireshark-batman-adv wireshark-batman-adv dissector]] +* [[Linux kernel coding style]] +* Reading the documentation of the algorithms: [[batman-adv-doc"httpgitoriousorgbatman-adv-doc] ["batman-rfc-draft]] (used in the 'old' batmand) +* Being able to use virtual machines for debugging (i.e. qemu) +* Being able to install a mesh network with [[OpenWRT]] and batman-adv +* Kernel coding experiences (especially with how to handle and avoid memory management/race conditions/deadlocks) +* monitoring packet flow (using tcpdump / wireshark + [[wireshark-batman-adv dissector]] + + +h1. Ideas + -= Ideas = -== link layer fragmentation / compression == -'''Brief description:''' Introducing link-layer fragmentation and header compression to offer alternative packet overhead solutions. +h2. 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 lightweight link layer fragmentation and/or develop another solution. -== forward error correction == -'''Brief description:''' Forward error correction to avoid retransmissions in the mesh network. + +h2. forward error correction + +*Brief description:* Forward error correction to avoid retransmissions in the mesh network. 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 separate types to reduce the amount of packets flooded in the neighborhood. + +h2. B.A.T.M.A.N. protocol overhead reduction + +*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]. -== B.A.T.M.A.N. protocol convergence speed == -'''Brief description:''' Implement a fast changing environment detection algorithm to let mobile nodes adapt to their new surroundings faster. + +h2. B.A.T.M.A.N. protocol convergence speed + +*Brief description:* Implement a fast changing environment detection algorithm to let mobile nodes adapt to their new surroundings faster. 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 == -'''Brief description:''' Avoid broadcasting multicast traffic to nodes not belonging to a certain multicast group. + +h2. 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 == -'''Brief description:''' A batman-adv node shall select originator interval rates according to the dense and dynamics in its closer environment. + +h2. 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 == -'''Brief description:''' Add useful options for administrating a mesh network to batctl. + +h2. 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 == -'''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. +h2. Live VIS in map -== Multiple interfaces per node support in Mesh3D == -'''Brief description:''' Adapting Mesh3D to handle the new visualization format features from current batman-adv. +*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. + + +h2. 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 == -'''Brief description:''' Allow multiple bridge uplinks to wired networks + +h2. 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/Emulation: Allow > 9 instances (98419130)
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 984191300661e17ab844f55d2263a58358d9964c Author: Sven Eckelmann <sven(a)narfation.org> Date: Sun Feb 14 00:18:48 2010 +0000 doc: open-mesh/Emulation: Allow > 9 instances >--------------------------------------------------------------- 984191300661e17ab844f55d2263a58358d9964c open-mesh/Emulation.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/Emulation.textile b/open-mesh/Emulation.textile index f2ba27f9..5bcbc9b1 100644 --- a/open-mesh/Emulation.textile +++ b/open-mesh/Emulation.textile @@ -28,7 +28,7 @@ Furthermore, to allow automatic network device setup on boot i'm using the follo # kill default openwrt network config NUM=$(ifconfig eth0| grep HWaddr | sed 's/:01[\n\ ]*$//' | sed 's/.*://'| sed 's/[\n\ ].*//') -ifconfig eth1 inet 192.168.${NUM}.2 up +ifconfig eth1 inet 192.168.$((0x$NUM)).2 up ifconfig br-lan down brctl delbr br-lan

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Wiki: renaming B.A.T.M.A.N. to batman-daemon to refer to the layer 3 implementation and not the protocol idea itself (8f03d9b5)
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 8f03d9b5ab25e04b31ee38a8adb7aae0f46812b0 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Fri Feb 26 17:45:02 2010 +0000 doc: batman-adv/Wiki: renaming B.A.T.M.A.N. to batman-daemon to refer to the layer 3 implementation and not the protocol idea itself >--------------------------------------------------------------- 8f03d9b5ab25e04b31ee38a8adb7aae0f46812b0 batman-adv/Wiki.textile | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/batman-adv/Wiki.textile b/batman-adv/Wiki.textile index 7982e7e5..36d0ba72 100644 --- a/batman-adv/Wiki.textile +++ b/batman-adv/Wiki.textile @@ -1,13 +1,13 @@ = batman-advanced = Batman-advanced is a new approach to wireless networking which -does no longer operate on the IP basis. Unlike B.A.T.M.A.N, which exchanges +does no longer operate on the IP basis. Unlike the layer 3 batman-daemon, which exchanges information using UDP packets and sets routing tables, batman-advanced operates on ISO/OSI Layer 2 only and uses and routes (or better: bridges) Ethernet Frames. It emulates a virtual network switch of all nodes participating. Therefore all nodes appear to be link local, thus all higher operating protocols won't be affected -by any changes within the network. You can run almost any protocol above B.A.T.M.A.N. -Advanced, prominent examples are: IPv4, IPv6, DHCP, IPX. +by any changes within the network. You can run almost any protocol above B.A.T.M.A.N.-Advanced, +prominent examples are: IPv4, IPv6, DHCP, IPX. === Pros and Cons === Pros:

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Download (bdf3f461)
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 bdf3f4615993042b1b56db2acda99519e6588987 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Fri Feb 26 06:57:25 2010 +0000 doc: open-mesh/Download >--------------------------------------------------------------- bdf3f4615993042b1b56db2acda99519e6588987 open-mesh/Download.textile | 35 +++++++++++++++++++++++------------ 1 file changed, 23 insertions(+), 12 deletions(-) diff --git a/open-mesh/Download.textile b/open-mesh/Download.textile index 0b0b3a5d..a77c6d79 100644 --- a/open-mesh/Download.textile +++ b/open-mesh/Download.textile @@ -1,13 +1,13 @@ = Download B.A.T.M.A.N. = We are currently working on different branches. To get the details about the differences of these branches, see our [wiki:BranchesExplained Branches Explained page]. -We are offering sources and precompiled 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. +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 stable B.A.T.M.A.N. is batman-0.3.2''': [http://downloads.open-mesh.net/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 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] * 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 stable version of batmand is [http://downloads.open-mesh.net/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 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] If you find any bugs, please [wiki:Contribute let us know]! @@ -15,24 +15,35 @@ If you find any bugs, please [wiki:Contribute let us know]! === Subversion Repository Access === You can check out our SVN repository and the various batman branches - * upcoming B.A.T.M.A.N. 0.4.0 branch: [[BR]]''{{{svn co http://downloads.open-mesh.org/svn/batman/trunk/batman/}}}'' - * Visualization server for B.A.T.M.A.N.: check out the complete repository, cd into vis (we're using symlinks here ...): [[BR]]''{{{svn co http://downloads.open-mesh.org/svn/batman/trunk/}}}'' - * B.A.T.M.A.N. experimental (BMX) branch: [[BR]]''{{{svn co http://downloads.open-mesh.org/svn/batman/trunk/batman-experimental/}}}'' * [wiki:batman-adv B.A.T.M.A.N. advanced]: [[BR]]''{{{svn co http://downloads.open-mesh.org/svn/batman/trunk/batman-adv-kernelland/}}}'' * batctl (for B.A.T.M.A.N. advanced): check out the complete repository, cd into batctl (we're using symlinks here ...): [[BR]]''{{{svn co http://downloads.open-mesh.org/svn/batman/trunk/}}}'' * complete repository: [[BR]]''{{{svn co http://downloads.open-mesh.org/svn/batman/trunk/}}}'' + * upcoming B.A.T.M.A.N. 0.4.0 branch '''(maintainer needed!)''': [[BR]]''{{{svn co http://downloads.open-mesh.org/svn/batman/trunk/batman/}}}'' + * Visualization server for B.A.T.M.A.N.: check out the complete repository, cd into vis (we're using symlinks here ...): [[BR]]''{{{svn co http://downloads.open-mesh.org/svn/batman/trunk/}}}'' + * B.A.T.M.A.N. experimental (BMX) branch: [[BR]]''{{{svn co http://downloads.open-mesh.org/svn/batman/trunk/batman-experimental/}}}'' + +=== Git Repository Access === +Since we started integrating the batman-adv kernel module into the mainline Linux tree, we also maintain a git repository which contains the batman-adv maintenance and Linux integration branches. More information can be found [wiki:UsingBatmanGit on our git page]. + + +=== batman-adv in the Linux tree === + +Since linux 2.6.33 batman-adv is part of the official linux tree. You can build batman-adv along with your linux binary by simply selecting batman-adv in the Linux drivers section. If you use an older kernel or want to have access to the latest features you can checkout our SVN or git repository which still are backward compatible until 2.6.20. + +It follows an overview about which linux version contains which batman-adv, so that you easily can pick the compatible batctl packages: + * linux 2.6.33 => batman-adv 0.2 (get batctl 0.2 from [http://downloads.open-mesh.org/batman/stable/sources/batctl/ here]) === Debian === Use apt-get (or any other dpkg frontend of choice) to install B.A.T.M.A.N. onto your debian machine. Following packages are available: - * [http://packages.debian.org/sid/batmand batmand] - batman 0.3 - * [http://packages.debian.org/sid/batman-adv-source batman-adv-source] - batman-advanced kernel module source (installable via [http://packages.debian.org/sid/module-assistant module-assistant]) - * [http://packages.debian.org/sid/batman-adv-dkms batman-adv-dkms] - batman-advanced kernel module dkms package to build new modules dynamically (half-automatic) - * [http://packages.debian.org/sid/batctl batctl] - batctl + * [http://packages.debian.org/sid/batmand batmand] - batman 0.3.2 + * [http://packages.debian.org/sid/batman-adv-source batman-adv-source] - batman-advanced kernel 0.2 module source (installable via [http://packages.debian.org/sid/module-assistant module-assistant]) + * [http://packages.debian.org/sid/batman-adv-dkms batman-adv-dkms] - batman-advanced kernel module 0.2 dkms package to build new modules dynamically (half-automatic) + * [http://packages.debian.org/sid/batctl batctl] - batctl 0.2 -=== Download precompiled Binaries === +=== Download precompiled binaries for batmand === There are various pre-compiled binaries available: * [http://downloads.open-mesh.org/batman/stable/binaries/wrt-freifunk/batmand_… mipsel OpenWRT/Whiterussian Freifunk] @@ -48,6 +59,6 @@ There are various pre-compiled binaries available: === Building OpenWRT packages === -B.A.T.M.A.N. is also included in OpenWRT as a package. Download the extra package feed, link the batman folder into your main OpenWRT svn directory and use "make menuconfig" to select the B.A.T.M.A.N. flavor you intend to use. This enables you to integrate B.A.T.M.A.N. seamlessly in your builds. +B.A.T.M.A.N. is also included in OpenWRT as a package. Download the extra package feed, link the batman folder into your main OpenWRT svn directory and use "make menuconfig" to select the B.A.T.M.A.N. flavor you intend to use. This enables you to integrate B.A.T.M.A.N. seamlessly into your builds. More information about how to build the OpenWRT toolchain is available [http://wiki.openwrt.org/OpenWrtDocs/BuildingKamikazeHowTo here].

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Download: trying to make the usually mutual exclusive character of batmand and batman-adv a little clearer (11c8da3c)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/News-archive (96fa0168)
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 96fa016896b2c407d3d00da03ad9efa82174a992 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Tue Mar 2 16:06:58 2010 +0000 doc: open-mesh/News-archive >--------------------------------------------------------------- 96fa016896b2c407d3d00da03ad9efa82174a992 open-mesh/News-archive.textile | 1 + 1 file changed, 1 insertion(+) diff --git a/open-mesh/News-archive.textile b/open-mesh/News-archive.textile index 5828f4e3..9a40a45a 100644 --- a/open-mesh/News-archive.textile +++ b/open-mesh/News-archive.textile @@ -6,6 +6,7 @@ This page contains the links to previous news posts for archiving puposes. [[BR]] === 2009 === + * '''23.Oct. 2009''' [wiki:2009-10-23-batman-goes-mainline Batman goes mainline] * '''13.Jun. 2009''' [wiki:2009-06-13-batman-0-3-2-release Batman 0.3.2 released] * '''19.Apr. 2009''' [wiki:2009-04-19-wbm2009-aftermath WirelessBattleMesh2009] * '''25.Jan. 2009''' [wiki:2009-01-25-batman-0-3-1-release Batman 0.3.1 released]

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/WikiStart (f944da74)
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 f944da74e7114536df191400ea14009b74e24fab Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Tue Mar 2 16:07:49 2010 +0000 doc: open-mesh/WikiStart >--------------------------------------------------------------- f944da74e7114536df191400ea14009b74e24fab open-mesh/WikiStart.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/WikiStart.textile b/open-mesh/WikiStart.textile index 660abb39..2795c78b 100644 --- a/open-mesh/WikiStart.textile +++ b/open-mesh/WikiStart.textile @@ -5,11 +5,11 @@ = B.A.T.M.A.N. = B.A.T.M.A.N. (better approach to mobile ad-hoc networking) is a routing protocol for multi-hop ad-hoc mesh networks. This is the main development website, we have source code, binary packages, documentation and further information available: == News == + * '''02.Mar. 2010''' [wiki:2010-03-02-batman-at-wbmv3 B.A.T.M.A.N. at WBMv3] * '''26.Dec. 2009''' [wiki:2009-12-26-retrospect-batman-in-2009 Retrospect 2009] * '''18.Dec. 2009''' [wiki:2009-12-18-batman-v-outlook B.A.T.M.A.N. V outlook] * '''18.Nov. 2009''' [wiki:2009-11-18-wbm2009-2nd-encounter WirelessBattleMesh2009v2] * '''09.Nov. 2009''' [wiki:2009-11-08-batman-adv-0-2-release Batman-adv 0.2 released] - * '''23.Oct. 2009''' [wiki:2009-10-23-batman-goes-mainline Batman goes mainline] * [wiki:news-archive news archive] == Getting Started ==

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits July 2017