From: "Linus Lüssing" <linus.luessing@web.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.] Stup batman ADv devel on openWRT
Date: Thu, 20 Jan 2011 13:52:59 +0100 [thread overview]
Message-ID: <20110120125259.GA14504@Sellars> (raw)
In-Reply-To: <4D37F45B.9000106@gmail.com>
On Thu, Jan 20, 2011 at 10:37:47AM +0200, wayne wrote:
> Linus Lüssing wrote:
> >Hi Michael,
> >
> >You have a bridge loop here, you cannot put an interface into
> >batman-adv and bridge the same one with bat0 again which seems to
> >be the case for wlan0. Packets will enter wlan0, batman will grab
> >them, encapsulate it in its own batman header and send the same
> >packet on wlan0 again, reaching another batman-adv
> >node, which encapsulates the same packet again etc.
> >
>
>
> Hi All
>
> If I can jump in here, I had the same prob with batman L3 in wrt
> with the bridge!
>
> Killing the Br-lan bridge kills everything, I eventually solved it
> by flashing a old kamakaze version : pre bridge version, which
> provides the simple ,
>
> eth0, eth1 , scenario!
>
> Wayne A
>
Sorry, but I don't get it, how are the batman-adv and batmand
bridge issues related? Why should an older OpenWRT "fix" this? In
this scenario I'm 100% that using a different OpenWRT version will
_not_ help Michael, as it is a conceptual issue, not a bug or so.
What kind of pre bridge version are you talking about?
Cheers, Linus
next prev parent reply other threads:[~2011-01-20 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 7:31 [B.A.T.M.A.N.] Stup batman ADv devel on openWRT Michael Y. Gluhovchenko
2011-01-20 8:25 ` Linus Lüssing
2011-01-20 8:37 ` wayne
2011-01-20 12:52 ` Linus Lüssing [this message]
2011-01-20 15:33 ` Tom Cannon
2011-01-21 5:05 ` wayne
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=20110120125259.GA14504@Sellars \
--to=linus.luessing@web.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