Jon Fink | 21 Oct 15:55 2014
Picon

Local Clients Expiring from Translation Table

I'm experiencing some issues where clients connected to a batman node
(through a wired interface) are expiring from the local translation
table after a period of inactivity. I'm guessing this is an
intentional feature to support roaming but I'm wondering if there is a
way to stop this behavior for certain MAC addresses. Some more detail
of my setup:

* I have multiple mesh nodes named pico9, pico17, pico24, pico41, etc...
* Each node is running BATMAN 2014.2.0 attached to a wireless device.
* Each node is also bridging the batman device with its local ethernet device.
* A subset of the nodes are then connected to the same wired backbone,
lets say pico9/17/24 are all on this backbone.
* I have my laptop also connected to the backbone and I am able to
successfully connect to any of the BATMAN nodes (over the wired
backbone or to other nodes via the wireless mesh).

pico41 (not on the backbone) has a wired client connected to it, lets
call it clientA

I can initially connect to clientA from my laptop and it shows up
correctly in pico41's local translation table. However if I do not
continually send data (ping, ssh, etc) between my laptop and clientA,
I see the "last seen" column of pico41's local translation table entry
increase. Eventually, clientA is removed from the table and I am not
able to connect to it (ping or ssh) until I "do something" to trigger
some traffic from clientA onto the mesh network. This is problematic
because it requires either physically accessing clientA (not practical
in our application) or manually ssh'ing into the node running batman
and then connecting to clientA (makes for a challenging use-case)

(Continue reading)

Krishnathiepan Rasanayagam | 20 Oct 16:34 2014
Picon

QoS tagging

Hi Guys,

is anyone working in batman-adv for tagging packets for QoS. Lke
tagging VOIP packets?

--

-- 
Best regards,
Krishna.

Antonio Quartulli | 19 Oct 19:59 2014

[PATCH] batman-adv: move misplaced compat code

consume_skb() has to be re-defined only for kernels <2.6.30
but the macro was accidentally placed right above any #ifdef
block causing the function to be always redefined.

Fix this by moving the macro to the proper #ifdef block.

Introduced by: 15fb0fab51a3695738f65dfaab045e979fc89dce
("batman-adv add compat code for consume_skb")

Reported-by: Sven Eckelmann <sven@...>
Signed-off-by: Antonio Quartulli <antonio@...>
---
 compat.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/compat.h b/compat.h
index ed5b815..8de2010 100644
--- a/compat.h
+++ b/compat.h
 <at>  <at>  -23,10 +23,10  <at>  <at> 

 #include <linux/version.h>	/* LINUX_VERSION_CODE */

-#define consume_skb(_skb) kfree_skb(_skb)
-
 #if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 30)

+#define consume_skb(_skb) kfree_skb(_skb)
+
 #undef __alloc_percpu
(Continue reading)

Krishnathiepan Rasanayagam | 19 Oct 14:26 2014
Picon

Changing interval of OGM

Hi guys,

Is there any possible ways to change the time where ogm's are
broadcasted in batman-adv algorithm.

--

-- 
Best regards,
Krishna.

tjhowse | 16 Oct 00:50 2014
Picon

Re: good dual radio node?

I've bought 20-odd WDR-3600 units and used them in a batman-adv mesh
in a dusty construction site for about three months. I've had zero
failures during that time. My only complaint with the hardware is that
it would be nice if the SMA antenna connectors were recessed a bit, as
the antenna protrudes quite a bit. But that is a minor trifle.
Otherwise they're great.

Note that not all "dual band" routers are created equal. Many are
advertised as dual band, but can only talk on one band or the other,
not both simultaneously. The WDR-3600 is a true dual band device. I
use the 5GHz radio for the mesh backbone between the routers, and
2.4GHz to clients.

On 16 October 2014 00:57, dan <dandenson@...> wrote:
> Gui, may I ask how you use the nodes?  Is it in production or just a hobby?
>
> I run a wireless ISP and I have a number of areas that no one has
> tried to get into because the traditional star topology wont work
> (valleys, heavily treed, lots of switchbacks).  I have enough people
> wanting service that I should be able to get at least 2 uplinks from
> any single node throughout these areas.  I've been trying to put
> together a dual radio mesh out of alix or routerboard hardware but I'm
> hitting $200 per node which is too much.  This TPLink looks like a
> good option, add an external enclosure and some 7-8dBi omnis should be
> under $100!
>
> I'm just not sure if these are 'production' quality, do you have any
> failure rate for these in an outdoor enclosure?
>
> On Wed, Oct 15, 2014 at 8:15 AM, Gui Iribarren <gui@...> wrote:
(Continue reading)

dan | 15 Oct 02:34 2014
Picon

good dual radio node?

Anyone have any recommendations for a good dual radio mesh node for
batman-adv that won't break the bank?  I'm looking at having wired
clients, but two mesh radios to keep throughput high.  802.11n radios
also required.

Thanks!

Simon Wunderlich | 13 Oct 12:52 2014
Picon

Re: batman-adv bonding feature - unable to get data packets fragmented into multiple wireless interfaces

Hello Syed,

thanks for testing.

Please don't send HTML mails to the mailing list, they will get rejected.

Thank you
    Simon

On Monday 13 October 2014 08:26:59 syedmoulana47 wrote:
> I am using batman-adv: 2012.5.0. I tried with version 2014.3.0 also.
> 
> Even without enabling bonding sometimes I can see simultaneous outbound udp
> traffic in both interfaces wlan0 and wlan1.
> 
> I will try with the patch and update.
> 
> Thanks.
> 
> Sent from my Xiaomi
> 
> On 11 Oct 2014 03:03, Simon Wunderlich <sw@...> wrote:
> Hey Syed,
> 
> which version of batman-adv are you using?
> 
> Please note there is a fix for a bonding problem which hasn't been merged
> yet, 
 please merge it manually for your tests (assuming you are using a
> recent version)
(Continue reading)

Linus Lüssing | 10 Oct 23:15 2014
Picon

[PATCH maint] batman-adv: fix counter for multicast supporting nodes

A miscounting of nodes having multicast optimizations enabled can lead
to multicast packet loss in the following scenario:

If the first OGM a node receives from another one has no multicast
optimizations support (no multicast tvlv) then we are missing to
increase the counter. This potentially leads to the wrong assumption
that we could safely use multicast optimizations.

Fixings this by increasing the counter if the initial OGM has the
multicast TVLV unset, too.

Introduced by 77ec494490d60d89b42cd01d5dbf8dee04503623
("batman-adv: Announce new capability via multicast TVLV")

Signed-off-by: Linus Lüssing <linus.luessing@...>
---
 multicast.c |    8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/multicast.c b/multicast.c
index 96b66fd..02c2e0c 100644
--- a/multicast.c
+++ b/multicast.c
 <at>  <at>  -686,11 +686,13  <at>  <at>  static void batadv_mcast_tvlv_ogm_handler_v1(struct batadv_priv *bat_priv,
 		if (orig_initialized)
 			atomic_dec(&bat_priv->mcast.num_disabled);
 		orig->capabilities |= BATADV_ORIG_CAPA_HAS_MCAST;
-	/* If mcast support is being switched off increase the disabled
-	 * mcast node counter.
+	/* If mcast support is being switched off or if this is an initial
(Continue reading)

Simon Wunderlich | 10 Oct 21:03 2014
Picon

Re: batman-adv bonding feature - unable to get data packets fragmented into multiple wireless interfaces

Hey Syed,

which version of batman-adv are you using?

Please note there is a fix for a bonding problem which hasn't been merged yet, 
please merge it manually for your tests (assuming you are using a recent 
version)

https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2014-August/012382.html

Also bonding has nothing to do with fragmentation - the idea of bonding is 
that the packets should not be split, but get sent interleaved over the 
interfaces, e.g. 

 * wlan 1 - packet 1
 * wlan 2 - packet 2
 * wlan 1 - packet 3
 * wlan 2 - packet 4
 * etc ...

To have a real gain from that, the two links must be equally good quality. 
Also deep queues in the driver may cause reordering of packets which will 
upset TCP. The best results I've seen in the past were 50% performance gain 
over a single link, but I didn't try it out in real world scenarios lately.

Thanks,
    Simon
On Tuesday 07 October 2014 17:27:50 syed moulana wrote:
> hi
> 
(Continue reading)

Simon Wunderlich | 10 Oct 20:54 2014
Picon

Re: new alfred packet type *3* for solar tracer charging units

On Monday 06 October 2014 23:04:28 Daniel Golle wrote:
> On Mon, Oct 06, 2014 at 04:39:15PM +0200, Simon Wunderlich wrote:
> > > so the next step should be to include these into alfred?
> > 
> > We basically have two options here:
> >  * integrat the tracetools into the alfred repository, similar to vis and
> > 
> > gpsd. Please note that the quality should also be similar and you or your
> > colleagues should be able to maintain that code
> > 
> >  * keep the package external (e.g. on gitorious), then since we have an
> > 
> > external software package now we should start using a number assignment
> > table in wiki to show which software uses which packet type. We could
> > then link from there your software
> > 
> > Any preferences? :)
> 
> I will definitely keep tracertools a standalone software package as there
> are many potential use-cases which do not involve alfred.
> Basically I'm still in the prototyping progress of a bigger system in,
> tracertools was a part of that effort. Now that other things (using PCF8574A
> and LTC4151 to monitor and control consumer-grade DC-to-AC inverters via
> I2C) also work, I will re-work the whole design, both, in terms of hardware
> I will move away from breadboard and loose wires to a proper shield
> targetting the WrtNode; in terms of software, tracertools will become a
> small lib and include handling serial port stuff instead of depending on
> socat to do that (though using socat has a couple of advantages as well and
> I may keep the option to pipe stuff through socat).
> Packages like collectd and alfred can then use libsolartracer to acquire
(Continue reading)

Simon Wunderlich | 10 Oct 20:53 2014
Picon

Re: Inquiry on interface alternating

Hello Ming Ann,

we had quite some changes for the interface alternation which were released 
with batman-adv 2014.1.0 / kernel 3.14. Could you please try your scenario 
with the latest batman-adv to make sure that we are not talking about old 
implementations?

Here is a link which describes more technical details about the new 
implementation:

http://www.open-mesh.org/projects/batman-adv/wiki/Multi-link-optimize

Thank you!
    Simon

On Tuesday 07 October 2014 17:10:26 MingAnn Ng wrote:
> Hello,
> 
> I am currently running some powerpc machines with buildroot environment. The
> Linux kernel version I am using is 3.8.13 and BATMAN-adv within the kernel
> without any modification. I am running interface alternating test with the
> topology below:
> 
> A========B=========C
> 
> There are two wireless links between A and B and two wireless links between
> B and C. The two wireless link is using two different channel and ESSID. TQ
> of the 4 links are vary from 250-255 at the initial state. I run udp iperf
> from A to C and observe tcpdump on node B for the two wireless interfaces
> (wlan0 and wlan1).
(Continue reading)


Gmane