From: Marek Lindner <lindner_marek@yahoo.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.] Problems connecting VPN and WLAN with Batman-adv
Date: Sat, 3 Apr 2010 00:00:16 +0800 [thread overview]
Message-ID: <201004030000.16637.lindner_marek@yahoo.de> (raw)
In-Reply-To: <201004020054.08840.clemens-john@gmx.de>
Hi,
> The problem is, that I have a vpn network on tap0 (10.18.0.0/24) and I
> dont know how I can link this two networks/interfaces to each other with
> batman. I tried to assign tap0 to batman, but this doesnt work.
>
> I want to be able to ping hosts that uses batman in the vpn and in the
> wlan network. How can I do this?
I have been reading the other mails but I don't fully understand what you are
trying to achieve here. Nevertheless, I'll try to write something. If I got it
all wrong, please let me know. :-)
It is important to keep in mind that IP addresses are totally irrelevant to
make this setup work. I mention this since you seem to have experience with
layer 3 routing. Even if the tap interfaces had no IP addresses batman-adv
would route the traffic through. Unless you need to access services on the VPN
interfaces via IPs you can safely run them without.
If you IP networks don't share the same broadcast domain (e.g. 10.18.1.0/24 vs
10.18.0.0/24) batman-adv won't propate IP routing entries because it assumes
that is what you want. To resolve this you have 2 choices:
The easy way:
Move all nodes into the same broadcast domain. All nodes will be able to
communicate with each other without problems. Disadvantage: If you have many
nodes (100+) in close range it will create considerable (ethernet) broadcast
overhead.
The routing way:
Let your VPN nodes know how to reach to "other" IP networks by adding routing
entries. Naturally, this will reduce the broadcast overhead but requires a
mechanism to distribute the routes (as batman-adv won't do it for you). There
a couple of standard ways you can choose from. Depending on your setup & needs
one or the other might be more interesting to use which brings us back to my
initial question. :-)
Regards,
Marek
next prev parent reply other threads:[~2010-04-02 16:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 22:54 [B.A.T.M.A.N.] Problems connecting VPN and WLAN with Batman-adv Clemens John
2010-04-02 6:52 ` Linus Lüssing
2010-04-02 10:17 ` Clemens John
2010-04-02 11:50 ` Linus Lüssing
2010-04-02 12:27 ` Clemens John
2010-04-02 16:00 ` Marek Lindner [this message]
2010-04-02 16:25 ` Bjoern Franke
2010-04-03 4:54 ` Marek Lindner
2010-04-04 15:41 ` Clemens John
2010-04-04 15:54 ` 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=201004030000.16637.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox