commits July 2017

commits@lists.open-mesh.org

1 participants
1317 discussions

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/MeshLinux (9554aa5c)
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 9554aa5c089881e1cd73c2bf7e849a4a7200def3 Author: elektra wagenrad <onelektra(a)gmx.net> Date: Fri Mar 16 18:36:30 2012 +0000 doc: open-mesh/MeshLinux >--------------------------------------------------------------- 9554aa5c089881e1cd73c2bf7e849a4a7200def3 open-mesh/MeshLinux.textile | 2 -- 1 file changed, 2 deletions(-) diff --git a/open-mesh/MeshLinux.textile b/open-mesh/MeshLinux.textile index 7869354d..424ce7d2 100644 --- a/open-mesh/MeshLinux.textile +++ b/open-mesh/MeshLinux.textile @@ -1,7 +1,5 @@ h1. [[MeshLinux]] -*Linux distribution geared to build mesh supernodes - routers with many wireless interfaces and plenty CPU power on X86 platform* - Meshlinux is outdated and really old. The project hasn't been updated in a long time. It is unlikely that anyone will take up development on it again. We recommend to use OpenWrt for X86 platform. Nothing is as outdated as old software. Meshlinux was created in the early days of mesh networking at the Freifunk community in 2004. It is a CD-Image that can be used to convert old PCs into wireless supernodes. There is a old Meshlinux version based on Linux (Kernel 2.4.26) available at (http://wiki.c-base.org/coredump/MeshLinux) This old version is based on Slackware and not maintained anymore. However it works nicely with old Atmel USB wireless devices (which is a problem nowadays with recent kernels), Prism-based Chipsets and Orinoco. But you won't find any modern mesh routing protocol implementations in it. If you want to build a meshrouter with this kind of wireless devices you may still use it and install a recent version of Layer 3 B.A.T.M.A.N. - you can download a statically compiled version from this server. You can not use Batman-advanced, since this would require a recent Linux kernel. Some userland mesh protocol daemon might still work with it.

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/MeshLinux (f9be43bd)
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 f9be43bd8636ed4cb8cd9a54b026cad6158a6241 Author: elektra wagenrad <onelektra(a)gmx.net> Date: Fri Mar 16 18:32:16 2012 +0000 doc: open-mesh/MeshLinux >--------------------------------------------------------------- f9be43bd8636ed4cb8cd9a54b026cad6158a6241 open-mesh/MeshLinux.textile | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/open-mesh/MeshLinux.textile b/open-mesh/MeshLinux.textile index 9ae9bccb..7869354d 100644 --- a/open-mesh/MeshLinux.textile +++ b/open-mesh/MeshLinux.textile @@ -1,4 +1,9 @@ -= MeshLinux = -'''Linux distribution geared to build mesh supernodes - routers with many wireless interfaces and plenty CPU power on X86 platform''' +h1. [[MeshLinux]] -Meshlinux is available as a CD-Image that can be used to convert old PCs into wireless supernodes. There is a old Meshlinux version based on Linux (Kernel 2.4.26) available at (http://zolder.scii.nl/~elektra/) This old version is based on Slackware and not maintained anymore. However it works nicely with old Atmel USB wireless devices (which is a problem nowadays with recent kernels), Prism-based Chipsets and Orinoco. If you want to build a meshrouter with this kind of wireless devices you may still use it and install a recent version of B.A.T.M.A.N. - you can download a statically compiled version from this server. New releases will be published here at Open-Mesh. *Update*: I'm sorry that I didn't publish a new version yet. The development is stalled at the moment. I wanted a distribution for PCs, like I have done earlier based on Slackware. But OpenWRT doesn't suit this purpose: After I finished the system I found that it is not capable to automatically load necessary modules. And each and every kernel module is a seperate package - you as the user have to know which hardware you have and which module to install. Don't get me wrong - it is a great embedded system if you take it as it is. When you have embedded hardware you know what is inside, and there is a minimum of space. So you know which kernelmodule you have to install in order to make your hardware work. But it is nothing like: Put this CD in the drive of an old, random PC and there you go... I already head this working before with my earlier versions. Transforming OpenWRT into this seems to be too much hazzle. After spending quite a while on this I ran out of time. I'll do it the 'old' way based on an old fashioned, simple and rock solid distro like Slackware when I have the time. \ No newline at end of file +*Linux distribution geared to build mesh supernodes - routers with many wireless interfaces and plenty CPU power on X86 platform* + +Meshlinux is outdated and really old. The project hasn't been updated in a long time. It is unlikely that anyone will take up development on it again. We recommend to use OpenWrt for X86 platform. + +Nothing is as outdated as old software. Meshlinux was created in the early days of mesh networking at the Freifunk community in 2004. It is a CD-Image that can be used to convert old PCs into wireless supernodes. There is a old Meshlinux version based on Linux (Kernel 2.4.26) available at (http://wiki.c-base.org/coredump/MeshLinux) This old version is based on Slackware and not maintained anymore. However it works nicely with old Atmel USB wireless devices (which is a problem nowadays with recent kernels), Prism-based Chipsets and Orinoco. But you won't find any modern mesh routing protocol implementations in it. If you want to build a meshrouter with this kind of wireless devices you may still use it and install a recent version of Layer 3 B.A.T.M.A.N. - you can download a statically compiled version from this server. You can not use Batman-advanced, since this would require a recent Linux kernel. Some userland mesh protocol daemon might still work with it. + +Sooner or later this information will be removed. \ No newline at end of file

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Wbmv5-batmandev-agenda (fb8d145f)
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 fb8d145fb2015a77e2e5d3a8b1af313ef3869851 Author: Antonio Quartulli <a(a)unstable.cc> Date: Sun Mar 11 12:01:50 2012 +0000 doc: open-mesh/Wbmv5-batmandev-agenda >--------------------------------------------------------------- fb8d145fb2015a77e2e5d3a8b1af313ef3869851 open-mesh/Wbmv5-batmandev-agenda.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/Wbmv5-batmandev-agenda.textile b/open-mesh/Wbmv5-batmandev-agenda.textile index 94e7a994..605f03fa 100644 --- a/open-mesh/Wbmv5-batmandev-agenda.textile +++ b/open-mesh/Wbmv5-batmandev-agenda.textile @@ -18,6 +18,6 @@ h2. Concept discussion h2. Others * GSOC 2012 ideas refinement -* Explaining the batman-adv release cycle - the lifespan of a patch +* Explaining the batman-adv release cycle - the journey of a patch through the branches * How to make David happy: hands-on session

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/MeshLinux (6b61e30d)
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 6b61e30d1620343e65c9e1c2e3fbb0c6d9de97b1 Author: elektra wagenrad <onelektra(a)gmx.net> Date: Fri Mar 16 18:51:27 2012 +0000 doc: open-mesh/MeshLinux >--------------------------------------------------------------- 6b61e30d1620343e65c9e1c2e3fbb0c6d9de97b1 open-mesh/MeshLinux.textile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/open-mesh/MeshLinux.textile b/open-mesh/MeshLinux.textile index 424ce7d2..9d3035e7 100644 --- a/open-mesh/MeshLinux.textile +++ b/open-mesh/MeshLinux.textile @@ -1,7 +1,7 @@ h1. [[MeshLinux]] -Meshlinux is outdated and really old. The project hasn't been updated in a long time. It is unlikely that anyone will take up development on it again. We recommend to use OpenWrt for X86 platform. +Meshlinux is outdated and really old. The project hasn't been updated in a long time. It is unlikely that anyone will take up development on it again. We recommend to use OpenWrt for X86 platform. The only purpose we can think of today is software archaeology or the use of very old legacy WiFi hardware. -Nothing is as outdated as old software. Meshlinux was created in the early days of mesh networking at the Freifunk community in 2004. It is a CD-Image that can be used to convert old PCs into wireless supernodes. There is a old Meshlinux version based on Linux (Kernel 2.4.26) available at (http://wiki.c-base.org/coredump/MeshLinux) This old version is based on Slackware and not maintained anymore. However it works nicely with old Atmel USB wireless devices (which is a problem nowadays with recent kernels), Prism-based Chipsets and Orinoco. But you won't find any modern mesh routing protocol implementations in it. If you want to build a meshrouter with this kind of wireless devices you may still use it and install a recent version of Layer 3 B.A.T.M.A.N. - you can download a statically compiled version from this server. You can not use Batman-advanced, since this would require a recent Linux kernel. Some userland mesh protocol daemon might still work with it. +Nothing is as outdated as old software. Meshlinux was created in the early days of mesh networking at the Freifunk community in 2004. It is a CD-Image that can be used to convert old PCs into wireless supernodes. There is a old Meshlinux version based on Linux (Kernel 2.4.26) available at (http://wiki.c-base.org/coredump/MeshLinux) This old version is based on Slackware and not maintained anymore. However it works nicely with old Atmel USB wireless devices (which is a problem nowadays with recent kernels), Prism-based Chipsets and Orinoco. But you won't find any modern mesh routing protocol implementations in it. If you want to build a meshrouter with nothing better than a 486 CPU and this kind of old wireless devices because you have them lying around and want to do something useful with it, you may still use it and install a recent version of Layer 3 B.A.T.M.A.N. - you can download a statically compiled version from this server. You can not use Batman-advanced, since this would require a recent Linux kernel. Some userland mesh protocol daemons like OLSR might still work with it. Sooner or later this information will be removed. \ No newline at end of file

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/ELP: fix broken link and spell checkin (94bb6207)
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 94bb62078c0d0a88ad95138eb3ff3b13a6f43480 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Sat Mar 17 05:50:51 2012 +0000 doc: batman-adv/ELP: fix broken link and spell checkin >--------------------------------------------------------------- 94bb62078c0d0a88ad95138eb3ff3b13a6f43480 batman-adv/ELP.textile | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/batman-adv/ELP.textile b/batman-adv/ELP.textile index 64b7d312..ee9a09c6 100644 --- a/batman-adv/ELP.textile +++ b/batman-adv/ELP.textile @@ -11,14 +11,14 @@ This approach was chosen for its simplicity during the protocol design phase and * Wireless interfaces usually come with some packet loss, therefore a higher broadcast rate is desirable to allow a fast reaction on flaky connections. Other interfaces of the same host might be connected to Ethernet LANs / VPNs / etc which rarely exhibit packet loss would benefit from a lower broadcast rate to reduce overhead. * It generally is more desirable to detect local link quality changes at a faster rate than propagating all these changes through the entire mesh (the far end of the mesh does not need to care about local link quality changes that much). Other optimizations strategies, like reducing overhead, might be possible if OGMs weren't used for all tasks in the mesh at the same time. -As a result detecting local link qualities shall be handled by an independent message type, ELP, whereas the OGM message type remains responsible for flooding the mesh with these link quality information and determening the overall path transmit qualities. +As a result detecting local link qualities shall be handled by an independent message type, ELP, whereas the OGM message type remains responsible for flooding the mesh with these link quality information and determining the overall path transmit qualities. h2. 1. Definitions * Node - A mesh router which utilizes the B.A.T.M.A.N. protocol as specified in this document on at least one network interface. -* originator - A node broadcasting its own OGMs (see [[OGM]] for details) that is therefore addressable within the mesh network routing layer. It is uniquely identifiable by its originator address. [[/|B.A.T.M.A.N.-Advanced]] uses the MAC address of its primary hard interface. -* hard-interface - Network interface utilized by B.A.T.M.A.N. for its own ethernet frames. +* originator - A node broadcasting its own OGMs (see [[OGM]] for details) that is therefore addressable within the mesh network routing layer. It is uniquely identifiable by its originator address. [[batman-adv:Doc-overview|B.A.T.M.A.N.-Advanced]] uses the MAC address of its primary hard interface. +* hard-interface - Network interface utilized by B.A.T.M.A.N. for its own Ethernet frames. * sliding window - Sequence numbers are recorded in dedicated sliding windows until they are considered out-of-range. Thus, such a sliding window always contains the set of recently received sequence numbers. The amount of sequence numbers recorded in the sliding window is used as a metric for the quality of detected links and paths. * Neighbor: An ELP sender within one hop distance (note, this is defined differently for the OGM protocol) @@ -26,7 +26,7 @@ h2. 2. Conceptual Data Structures h3. 2.1. Neighbor List -* Neighbor Address: The ethernet source address of the received ELP message. +* Neighbor Address: The Ethernet source address of the received ELP message. * Originator Address: The originator address of the node. * Packet Count Window: * Current Window Sequence Number: @@ -55,7 +55,7 @@ Each node periodically (ELP interval) generates and broadcasts ELP messages for * Version: Set your internal compatibility version. * Originator Address: Set this field to the primary MAC address of this B.A.T.M.A.N. node. * Sequence number: On first broadcast set the sequence number to an arbitrary value and increment the field by one for each following broadcast. -* Interval: Set to the current ELP interval of this interface in milli seconds. The default interval is 500ms and it may be reconfigured during run-time. +* Interval: Set to the current ELP interval of this interface in milliseconds. The default interval is 500ms and it may be reconfigured during run-time. * Num Neigh: The number of neighbors that are announced with this message. If this B.A.T.M.A.N. interface wants to announce neighboring nodes it should append a neighbor entry message for each neighbor to be announced and fill the "number of neighbors" field accordingly. @@ -103,7 +103,7 @@ h3. 3.2. Receiving Echo Location Messages (ELP) Upon receiving an ELP packet a node must perform the following preliminary checks before the packet is further processed: * If the ELP contains a version which is different to the own internal version the message must be silently dropped (thus, it must not be further processed). -* If the sender address of the ELP message is an ethernet multicast (including broadcast) address the message must be silently dropped. +* If the sender address of the ELP message is an Ethernet multicast (including broadcast) address the message must be silently dropped. * If the destination address of the ELP message is a unicast address the message must be silently dropped. * If the originator address of the ELP message is our own the message must be silently dropped as this ELP message originated from this node. * If the ELP message has not been received from an out-of-sync neighbor interface (see section 3.5) and if the ELP message does not contain a newer sequence number (duplicate, out-of-order or out-of-range) the message must be silently dropped. @@ -183,7 +183,7 @@ For each ELP message having passed the preliminary checks the following actions * The last seen time of this neighbor interface needs to be updated. * The last updated time of this neighbor interface needs to be updated. -* The ndp interval of this neighbor interface needs to be updated with the ndp interval set in the received ELP message. +* The elp interval of this neighbor interface needs to be updated with the elp interval set in the received ELP message. * The last received sequence number from this neighbor needs to be set to the sequence number of the received ELP message. * If the sequence number of the received ELP message is higher than the current window sequence number then: ** The window's current sequence number for this neighbor needs to be set to the sequence number of the received ELP message. @@ -212,12 +212,12 @@ Periodically all ELP windows must be shifted to the expected current sequence nu More precisely, for any interface of a node towards any according, stored neighbor interface check whether: -* The last updated time plus the ndp interval times of this neighbor interface times two is higher than the current time. +* The last updated time plus the elp interval times of this neighbor interface times two is higher than the current time. If so, the following actions must be performed: * The last updated time of this neighbor interface needs to be set to the current time minus the neighbor interface's ELP interval. -* The current window sequence number of this neighbor needs to be set to the expected sequence number (based on the current sequence number, the current time, the last updated time as well as the neighbor interface's ndp interval) minus one. The result always needs to be rounded down. +* The current window sequence number of this neighbor needs to be set to the expected sequence number (based on the current sequence number, the current time, the last updated time as well as the neighbor interface's elp interval) minus one. The result always needs to be rounded down. * The sliding window of the ELP message must be shifted (purged) to reflect the new upper and lower boundaries of the ranking range. * The new resulting link RQ value is calculated by counting all sequence numbers that are to be found in the adjusted sliding window. * The best link TQ needs to be updated.

1 0

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

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Wbmv5-batmandev-agenda (1d89c5f3)
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 1d89c5f351b170e526e29d907a6fa3418188c954 Author: Antonio Quartulli <a(a)unstable.cc> Date: Sun Mar 11 11:54:34 2012 +0000 doc: open-mesh/Wbmv5-batmandev-agenda >--------------------------------------------------------------- 1d89c5f351b170e526e29d907a6fa3418188c954 open-mesh/Wbmv5-batmandev-agenda.textile | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/open-mesh/Wbmv5-batmandev-agenda.textile b/open-mesh/Wbmv5-batmandev-agenda.textile new file mode 100644 index 00000000..3f581ff5 --- /dev/null +++ b/open-mesh/Wbmv5-batmandev-agenda.textile @@ -0,0 +1,22 @@ +h1. Wbmv5-batmandev-agenda + +h2. Celebration! + +Find something to celebrate. + +h2. Testing + +* Catwoman (Throughput test) +* ELP Testing (Is the code ready? poke Marek) +* Roaming + +h2. Concept discussion + +* ELP / OGMv2 +* Bandwidth based routing + +h2. Others + +* GSOC 2012 ideas refinement +* How to make David happy: hands-on session +

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Wbmv5-batmandev-agenda (f8356c57)
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 f8356c57b355dd55d86aa34b1edffbc3b62e8c95 Author: Antonio Quartulli <a(a)unstable.cc> Date: Sun Mar 11 11:57:02 2012 +0000 doc: open-mesh/Wbmv5-batmandev-agenda >--------------------------------------------------------------- f8356c57b355dd55d86aa34b1edffbc3b62e8c95 open-mesh/Wbmv5-batmandev-agenda.textile | 1 + 1 file changed, 1 insertion(+) diff --git a/open-mesh/Wbmv5-batmandev-agenda.textile b/open-mesh/Wbmv5-batmandev-agenda.textile index 3f581ff5..94e7a994 100644 --- a/open-mesh/Wbmv5-batmandev-agenda.textile +++ b/open-mesh/Wbmv5-batmandev-agenda.textile @@ -18,5 +18,6 @@ h2. Concept discussion h2. Others * GSOC 2012 ideas refinement +* Explaining the batman-adv release cycle - the lifespan of a patch * How to make David happy: hands-on session

1 0

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

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Building-with-openwrt: s/kamikaze/backfire/ (04259f4a)
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 04259f4aa1ad6bf2dad1330c08f8e5502f4e9a84 Author: Nicolas Marchildon <nicolas(a)marchildon.net> Date: Sat Mar 10 11:24:13 2012 +0000 doc: batman-adv/Building-with-openwrt: s/kamikaze/backfire/ >--------------------------------------------------------------- 04259f4aa1ad6bf2dad1330c08f8e5502f4e9a84 batman-adv/Building-with-openwrt.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/Building-with-openwrt.textile b/batman-adv/Building-with-openwrt.textile index 7ca63c58..39e6798a 100644 --- a/batman-adv/Building-with-openwrt.textile +++ b/batman-adv/Building-with-openwrt.textile @@ -12,7 +12,7 @@ First, you need to obtain a copy of the OpenWrt build system which contains all svn co svn://svn.openwrt.org/openwrt/tags/backfire_10.03 openwrt </pre> -Change into the openwrt-kamikaze directory and configure the system to meet you needs (e.g. choose the platform and additional packages you intend to use). +Change into the openwrt-backfire directory and configure the system to meet you needs (e.g. choose the platform and additional packages you intend to use). <pre> cd openwrt

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits July 2017