From: Bastian Bittorf <bittorf@bluebottle.com>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] fool batman by simulating a layer3 mesh
Date: Thu, 12 Sep 2013 11:36:41 +0200 [thread overview]
Message-ID: <20130912093641.GX1558@medion.lan> (raw)
discussed in IRC, i'am searched for a better way to
load-balance a batman network. not the whole shaping/splashing
should run on one (central) node, so we needed something to stick it
to the node/AP which the user is connected to. than we have also
the ability to show a good page when the network is b0rken.
short overview:
NODE-1 (master/gateway)
ipv4: 192.168.1.1/16
dhcp: 192.168.1.x / gateway: 192.168.0.1
gateway: e.g. pppoe
NODE-2
ipv4: 192.168.2.1/16
dhcp: 192.168.2.x / gateway: 192.168.0.1
gateway: 192.168.1.1
NODE-3
ipv4: 192.168.3.1/16
dhcp: 192.168.3.x / gateway: 192.168.0.1
gateway: 192.168.1.1
the trick is, that every node offers DHCP which
does not interfere with other nodes AND offers a
gateway which is always the same: 192.168.0.1
if a user roams he simply moves on layer 1/2 and
its further working ok. important: the MAC of the
gateway should not change otherwise it's not working
for some seconds till the ARP times out. this can
be circumvented via kmod-macvlan:
ip link add link br-mybridge gateway0 address '02:00:c0:ca:c0:1a' type macvlan
ip address add 192.168.0.1/16 dev gateway0
ip link set dev gateway0 up
then the IP 192.168.0.1 is always reachable with the same MAC.
thats it. we can use the "normal" iptables/tc stuff like in
olsrd-networks...
giving out such dhcp-leases needs a fix to /etc/init.d/dhcp
which is available soon on OpenWrt mailinglist.
bye, bastian
PS:
thanks for the discussion and help, escpecially to T_X, ordex and marec
next reply other threads:[~2013-09-12 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 9:36 Bastian Bittorf [this message]
2013-09-13 11:49 ` [B.A.T.M.A.N.] fool batman by simulating a layer3 mesh Antonio Quartulli
2013-09-13 18:19 ` Jan Huwald
2013-09-15 7:55 ` Bastian Bittorf
2013-11-27 6:32 ` Linus Lüssing
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=20130912093641.GX1558@medion.lan \
--to=bittorf@bluebottle.com \
--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