From: Clemens John <clemens-john@gmx.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.] Batman advanced and internet gateways
Date: Wed, 7 Jul 2010 01:45:30 +0200 [thread overview]
Message-ID: <201007070145.39178.clemens-john@gmx.de> (raw)
In-Reply-To: <201007070030.30940.lindner_marek@yahoo.de>
[-- Attachment #1: Type: Text/Plain, Size: 2267 bytes --]
Am Mittwoch 07 Juli 2010, 00:30:30 schrieb Marek Lindner:
> On Wednesday, July 07, 2010 00:21:38 Clemens John wrote:
> > I still got two question left that I remembered when I read your answers:
> > We discussed our networksetup on IRC (you remember?) and we decided to
> > choose the setup with tinc an not sending batman advanced packages over
> > VPN.
>
> Oh yeah, I remember. Did you document your setup somewhere ? Others might
> find it useful to see why & how you did it.
Yes we did some verry little documentation [1] but this is still the pure
configuraion without explenations because we are currently testing some
different configurations for example some IPv6 stuff and a script which can
automatically announce tinc installations with configuration and certificates on
a central server for automatic tinc installations etc..
I hope this will get better in the next time.
[1] http://wiki.freifunk-
ol.de/index.php?title=OpenWrt_Freifunk_Standartkonfiguration
> > Now batman advanced nodes behind the VPN does not get listet in the
> > originator tables of nodes on the other side of the VPN.
> > But do they get listed on the gateway list? Can Batman advanced choose a
> > gateway behind the VPN?
>
> No, because the gateway information travel with the OGMs which you don't
> have on your VPN. Sending dhcp requests via unicast also does not work
> because the VPN interfaces are not controlled by batman.
Mhh...
The only way to solve this would be to send whole batman advanced frames over
Tinc VPN right (we called this solution 3 in the irc session)?
Would this be possible? I know that we than have the MTU problem again and
higher traffic load (what would not be so fatal because we have no cetral server
with tinc).
Our current setup makes not much sense if we use Batman advanced with gateway
mode because we do not have a gateway in each cloud and it would be difficult to
get one to each cloud.
The best way would be a solution that can use all gateways available in the
network without extra configuration for each cloud.
Can you give me a short example of how to fix the mtu problem with this method?
Offcourse we are going to document both solutions ;)
Thank you
Clemens
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-07-06 23:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 17:47 [B.A.T.M.A.N.] Batman advanced and internet gateways Clemens John
2010-07-06 20:15 ` Marek Lindner
2010-07-06 21:46 ` Clemens John
2010-07-06 22:06 ` Marek Lindner
2010-07-06 22:21 ` Clemens John
2010-07-06 22:30 ` Marek Lindner
2010-07-06 23:45 ` Clemens John [this message]
2010-07-07 11:16 ` Marek Lindner
2010-07-07 11:25 ` Clemens John
2010-07-07 12:10 ` Marek Lindner
2010-07-07 12:33 ` Clemens John
2010-07-07 12:44 ` Antonio Quartulli
2010-07-07 13:49 ` Clemens John
2010-07-07 10:33 ` Clemens John
2010-07-07 10:50 ` Andrew Lunn
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=201007070145.39178.clemens-john@gmx.de \
--to=clemens-john@gmx.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