From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: johnzeng <johnzeng2013@yahoo.com>,
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.] i have a question ? How many relay nodes can be supported at NetworkCoding ( mtu 1546 ) .
Date: Wed, 9 Nov 2016 06:33:30 +0100 [thread overview]
Message-ID: <20161109053330.GH3391@otheros> (raw)
In-Reply-To: <mailman.87.1478663809.678.b.a.t.m.a.n@lists.open-mesh.org>
On Wed, Nov 09, 2016 at 04:56:52AM +0100, johnzeng via B.A.T.M.A.N wrote:
> Date: Wed, 09 Nov 2016 11:56:36 +0800
> From: johnzeng <johnzeng2013@yahoo.com>
> To: Simon Wunderlich <sw@simonwunderlich.de>
> CC: b.a.t.m.a.n@lists.open-mesh.org, Sven Eckelmann <sven@narfation.org>,
> Martin Hundebøll <martin@hundeboll.net>
> Subject: Re: [B.A.T.M.A.N.] i have a question ? How many relay nodes can be
> supported at NetworkCoding ( mtu 1546 ) .
> > if Relay mode is based on Layer 3 ( route or
> >Nat ) , it will be very complex and Infeasible at large wifi network
No, batman-adv has nothing to do with layer 3. For clients in batman-adv it
all looks like one, big switch.
It does that not by layer3 routing or layer3 NAT'ing, but by
encapsulating frames in its own headers.
next prev parent reply other threads:[~2016-11-09 5:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 12:30 i have a question ? How many relay nodes can be supported at NetworkCoding ( mtu 1546 ) johnzeng
2016-11-04 13:33 ` johnzeng
2016-11-05 14:28 ` [B.A.T.M.A.N.] " Sven Eckelmann
2016-11-07 7:37 ` Martin Hundebøll
2016-11-08 10:54 ` johnzeng
[not found] ` <mailman.63.1478602511.678.b.a.t.m.a.n@lists.open-mesh.org>
2016-11-08 19:14 ` [B.A.T.M.A.N.] " Simon Wunderlich
2016-11-09 3:50 ` johnzeng
2016-11-09 3:56 ` johnzeng
[not found] ` <mailman.87.1478663809.678.b.a.t.m.a.n@lists.open-mesh.org>
2016-11-09 5:33 ` Linus Lüssing [this message]
[not found] ` <mailman.86.1478663442.678.b.a.t.m.a.n@lists.open-mesh.org>
2016-11-09 5:28 ` Linus Lüssing
2016-11-09 5:59 ` johnzeng
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=20161109053330.GH3391@otheros \
--to=linus.luessing@c0d3.blue \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=johnzeng2013@yahoo.com \
/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