From: Donald Gordon <don@dis.org.nz>
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.] batman-adv: softif lan loop avoidance
Date: Tue, 28 Sep 2010 10:00:21 +1300 [thread overview]
Message-ID: <AANLkTinacNr1_eAFPiEhxx0ahPZ0_TRYYxKJZ617cFaH@mail.gmail.com> (raw)
In-Reply-To: <201009271758.03620.lindner_marek@yahoo.de>
On Tue, Sep 28, 2010 at 4:58 AM, Marek Lindner <lindner_marek@yahoo.de> wrote:
> But thanks a lot for all your questions because it made me aware of the fact
> that my explanations were not clear enough. To address the matter I wrote a
> document: http://www.open-mesh.org/wiki/bridge-loop-avoidance
>
> Let me know if it answers the questions raised here and also pay close
> attention to the handcrafted fancy graphics. :-)
Questions I still have:
* Does this mean that batman will now send OGMs out the bat0 interface?
* Can the LAN be added as an interface that batman will send "normal"
batman packets out, too? So bat0 would be in a bridge br0 with e.g.
eth0, but br0 or eth0 would also be set up as an interface batman
would send/recieve batman-encapsulated packets on?
thanks
donald
next prev parent reply other threads:[~2010-09-27 21:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 18:57 [B.A.T.M.A.N.] LAN loop avoidance (part II) Marek Lindner
2010-09-26 18:57 ` [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: softif lan loop avoidance Marek Lindner
2010-09-26 19:16 ` [B.A.T.M.A.N.] " Lew Pitcher
2010-09-26 20:25 ` Marek Lindner
2010-09-27 0:25 ` DuncanSF
2010-09-27 1:22 ` Donald Gordon
2010-09-27 15:58 ` Marek Lindner
2010-09-27 21:00 ` Donald Gordon [this message]
2010-09-28 9:33 ` Marek Lindner
2010-09-28 21:23 ` [B.A.T.M.A.N.] [PATCH 1/2] " Sven Eckelmann
2010-09-29 11:44 ` Marek Lindner
2010-09-26 18:57 ` [B.A.T.M.A.N.] [PATCH 2/2] batctl: display soft-interface neighbor table Marek Lindner
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=AANLkTinacNr1_eAFPiEhxx0ahPZ0_TRYYxKJZ617cFaH@mail.gmail.com \
--to=don@dis.org.nz \
--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;
as well as URLs for NNTP newsgroup(s).