From: "Geneviève Bastien" <gbastien@versatic.net>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] packets not processed by batman on eth0
Date: Fri, 22 Jun 2012 23:08:52 -0400 [thread overview]
Message-ID: <4FE53344.5080508@versatic.net> (raw)
In-Reply-To: <201206222108.16918.lindner_marek@yahoo.de>
On 12-06-22 03:08 PM, Marek Lindner wrote:
> On Friday, June 22, 2012 20:53:57 Geneviève Bastien wrote:
>> Wow! It works! I just added the line
>> option 'type' 'bridge'
>> to my mesh1 interface and my whole mesh is now working. Thanks!
>>
>> Was that documented somewhere? It gave me quite a headache for such a
>> simple solution.
> Do you mind explaining your solution in greater detail ? So far, I don't quite
> follow your approach.
>
> Cheers,
> Marek
As Matthias suggested, I just changed my mesh1 interface, which was just
using the eth0 vlan interface, to a bridged interface. So my mesh1 is
now a bridge interface with only eth0 on it. (mesh1 is the interface I
add to the batman-adv file.)
In my /etc/config/network file, my mesh1 interface now looks like this
config interface 'mesh1'
option proto 'none'
option type 'bridge' # this line added from before, nothing else
changed
option ifname 'eth0'
option mtu '1528'
It seems batman-adv really does have a problem with vlans on openwrt.
Why? I don't know...
Cheers,
Geneviève
prev parent reply other threads:[~2012-06-23 3:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 2:27 [B.A.T.M.A.N.] packets not processed by batman on eth0 Geneviève Bastien
2012-06-21 8:28 ` Marek Lindner
2012-06-22 2:38 ` Geneviève Bastien
2012-06-22 3:03 ` Matthias Schiffer
2012-06-22 18:53 ` Geneviève Bastien
2012-06-22 19:08 ` Marek Lindner
2012-06-23 3:08 ` Geneviève Bastien [this message]
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=4FE53344.5080508@versatic.net \
--to=gbastien@versatic.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.