From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Batman-adv and routed subnets
Date: Fri, 03 Aug 2012 11:22:05 +0200 [thread overview]
Message-ID: <2670997.NDZah7qDiQ@bentobox> (raw)
In-Reply-To: <BB2F02D2-9B93-465E-BB7D-FA13492511BF@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1947 bytes --]
On Friday 03 August 2012 11:08:37 Luca Pretto wrote:
> Hi folks,
>
> I really need a bit of your help! I've already spent a week on this and I
> can't succeed! :(
>
> I'm going to install a small mesh (12 nodes, initially) covering my city and
> linking some friends of mine. At the moment the equipment (Ubiquiti) is
> already installed, structured as AP-STA (PSK2) in one large LAN (all
> connections bridged L2) with one central dhcp/firewall serving the
> 192.168.9.0/24 subnet (now that's all inside this net only).
>
> I would like to migrate the topology to a routed network, where the wireless
> mesh nodes have IPs allocated inside 10.9.0.0/16, and below each one of
> these nodes there will be a local LAN with reserved subnet (IP offered by
> OpenWRT through dnsmasq). I've done some experiment with OLSRd and I got a
> working system that way, but I'd REALLY LOVE to use batman-adv instead.
> Some of the networks already have internet connectivity, that will be
> shared through the mesh to whom needs it.
>
> 10.9.11.1 <----> 192.168.11.0/24 --> 192.168.11.1 (internet gateway)
>
>
> 10.9.12.1 <----> 192.168.12.0/24
>
>
> 10.9.13.1 <----> 192.168.13.0/24 --> 192.168.13.1 (internet gateway)
>
>
> 10.9.14.1 <----> 192.168.14.0/24
>
>
> 10.9.xx.1 <----> 192.168.xx.0/24
>
> Batman-adv will take care of the routing inside the wireless mesh (links "
> || " in the diagram). Anyway, I need that any host on the 192.168.xx.0/24
> subnets will be able to talk to each other.
>
> How can this be done with batman-adv?
First thing: batman-adv doesn't route (as in l3 routing). batman-adv creates a
distributed switch on l2 (so, batman-adv does path finding). Therefore,
batman-adv doesn't care about the l3 stuff.
And the stuff you've mentioned above is l3 stuff. So out of scope for batman-
adv. Either you create static routes, use proxy arp or use another software
that distributes the l3 routes.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-08-03 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 9:08 [B.A.T.M.A.N.] Batman-adv and routed subnets Luca Pretto
2012-08-03 9:22 ` Sven Eckelmann [this message]
2012-08-03 9:40 ` Luca Pretto
2012-08-03 10:01 ` Sven Eckelmann
2012-08-12 16:30 ` Simon Wunderlich
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=2670997.NDZah7qDiQ@bentobox \
--to=sven@narfation.org \
--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