public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] 2012.2 OGMs over ethernet issue?
Date: Sun, 8 Jul 2012 12:09:56 +0200	[thread overview]
Message-ID: <20120708100956.GA10210@pandem0nium> (raw)
In-Reply-To: <CAHD-aqKaF4tfsMBQLnyrn4wkqDHQpPjsfCDjhXPzrCbkzM7tsg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2119 bytes --]

Hey Guido,

On Sat, Jul 07, 2012 at 12:37:24AM -0300, Guido Iribarren wrote:
> Hello again nice folks,
> I updated today another segment of the network with just 4 nodes, to
> batman-adv 2012.2 (the one i compiled yesterday with simon patches for
> blaII, marek stability fixes, and debug log enabled , yikes!)
> and i couldn't get batman to work over wired ethernet?? (?)
> 
> P -(50mts wlan)- D -----(ubnt transparent bridge) 2km -- C
>  \----eth-------------------/
> 
> Node P and D connected by ethernet on eth0 but close enough that could
> also see each other through adhoc wlan, with bla enabled, correctly
> preferred ethernet connection to communicate between them (iperf
> yielded 92mbps), so far so good.

As seen on the dump, you only use eth0 in batman? Is the Ad-Hoc connection
still active (on wlan0 or wlan-1)?

> now, node D and C, too far away from each other to communicate over
> wlan, but connected by a "loooong eth cable" (mediated by a wds
> transparent bridge) wouldn't find each other batman originator.
> C originator table was empty, and D only showed P.
> I thought the transparent bridge was misbehaving, so I tried in a
> simpler setup using P and D, with the wifi off:
> but after disabling wlan0 (batctl if del wlan0-2) and adding eth0
> (batctl if add eth0) on both nodes, batman could not see each other
> anymore :(
> i thought i was doing something wrong, so i tried in different ways,
> but could not get it to work.
> batctl td eth0 shows both outgoing OGMs from local , and incoming OGMs
> from remote,
> but batctl l only reported outgoing OGMs.
> 
> http://pastebin.com/7DDUaXu1

Mhm, that's weird indeed. Is eth0 really not included in any other bridge?
It looks like the incoming packets don't reach BATMAN for some reason.

Also have you checked that the WDS bridge works via IP? You could first set
up some IP addresses and ping each other, confirm traffic with tcpdump, and
then activate batman-adv to see if the OGMs go through. So far, it  doesn't
seem like anything from your C node comes through at all.

Cheers,
	Simon

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-07-08 10:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-07  3:37 [B.A.T.M.A.N.] 2012.2 OGMs over ethernet issue? Guido Iribarren
2012-07-08 10:09 ` Simon Wunderlich [this message]
2012-07-23  7:20   ` Gui Iribarren
2012-07-25 20:34     ` Simon Wunderlich
2012-07-25 21:11       ` Gioacchino Mazzurco
2012-07-25 22:04         ` Sven Eckelmann
2012-07-25 22:16           ` Gioacchino Mazzurco
2012-07-28 18:34       ` Gui Iribarren
2012-07-30 10:31         ` Simon Wunderlich
2012-09-13 16:10           ` Gui Iribarren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120708100956.GA10210@pandem0nium \
    --to=simon.wunderlich@s2003.tu-chemnitz.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox