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.] fool batman by simulating a layer3 mesh
Date: Wed, 27 Nov 2013 07:32:04 +0100 [thread overview]
Message-ID: <20131127063204.GE5457@Linus-Debian> (raw)
In-Reply-To: <20130915075534.GI11829@medion.lan>
Hi Bastian,
Did you have a chance to try the iptables + netfilter_bridge hook
(I believe via the iptables physdev module?) Antonio suggested
yet?
It sounds like a good idea to me and since no one seems to have
tried it with batman-adv yet I'm curious whether it works well in
practice.
Whether you could enhance the user experience in an open,
batman-adv based community mesh network by having an IP instead
of connection based sharing of available bandwidth.
Cheers, Linus
On Sun, Sep 15, 2013 at 09:55:34AM +0200, Bastian Bittorf wrote:
> * Jan Huwald <jh@sotun.de> [13.09.2013 20:37]:
> > How do you handle the splash status of a user under roaming? Does a
> > splash screen reoccur if the gateway is switched (NODE-2 -> NODE-3)?
> > Because this switch will happen on a minutely basis if a user sits
> > between two equally strong gateways.
>
> Splashing is only done for clients which have a lease from this
> node. All other traffic gets just true (picopeer alike). After
> some minutes the information that "IPx/MAC must be shaped like..."
> is applied in the hole network. If the client only has a lease but
> is not "unsplashed" this information is also spread netwide.
>
> A little bit ugly, but works and we have no memory or load problems
> anymore on the gateway. (~1000 clients)
>
> bye, bastian
next prev parent reply other threads:[~2013-11-27 6:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 9:36 [B.A.T.M.A.N.] fool batman by simulating a layer3 mesh Bastian Bittorf
2013-09-13 11:49 ` Antonio Quartulli
2013-09-13 18:19 ` Jan Huwald
2013-09-15 7:55 ` Bastian Bittorf
2013-11-27 6:32 ` Linus Lüssing [this message]
2013-11-27 8:37 ` Bastian Bittorf
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=20131127063204.GE5457@Linus-Debian \
--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 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.