B.A.T.M.A.N Archive on lore.kernel.org
 help / color / mirror / Atom feed
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.] MTU/connection problem
Date: Thu, 17 Jun 2010 16:19:44 +0200	[thread overview]
Message-ID: <201006171619.49916.clemens-john@gmx.de> (raw)
In-Reply-To: <20100617120708.GA23608@Sellars>

[-- Attachment #1: Type: Text/Plain, Size: 2336 bytes --]

On Thursday 17 June 2010 14:07:09 Linus Lüssing wrote:
> Yep, tap mode in openvpn is adding an extra header, it
> encapsulates not only the ip-packet but also the ethernet frame
> into udp or tcp. (By the way, tun-mode also adds an
> extra header, but the packets are smaller - only IP packets
> encapsulated in UDP or TCP.)
> 
> May I ask whether you are bridging tap0 or if you are routing the
> packets (so having an ip address on tap0 and having according
> entries in your routing table)? If it's the latter, then you could
> just decrease the MTU on the tap0 interfaces to a fitting size and
> let the VPN routers do the PMTU discovery stuff automatically. But
> of course, then you probably wouldn't need tap-mode in this
> scenario, as it just adds additional overhead with the unnecessary
> ethernet frame in between.
> 
> I know that tinc has two little, a bit hacky features in case of
> bridging tap0 with tap-mode (they call it switch-mode) to inform
> the other machines of the lower MTU in between. But I haven't
> heard of OpenVPN having similar features.
> 
> So I guess the easiest step would be the first suggestion, to do
> routing in between and lowering the MTU on the tap interfaces for
> a start before starting to experiment with (experimental) features
> and/or more complicated setups :).
> 
> Cheers, Linus

We tried tinc now, but the problem does still exist.
Our Tinc config looks like this:

----------
root@OpenWrt:~# cat /etc/tinc/batvpn/tinc.conf 
Hostnames=yes
Mode=Switch
name=floh1111
ConnectTo=batgw
#ConnectTo=harlingen
-----------

Normal ping over vpn till package size 1453 works.
If I increase the package size to 1454 ping fails.

All devices have an mtu of 1530 except bat0 and br-mesh which have an mtu of 
1500.
Batman is running on the tinc device tap0 and our bridge looks like this:

---------
config 'interface' 'mesh'
        option 'type' 'bridge'
        option 'ifname' 'ath0 bat0'
        option 'proto' 'static'
        option 'ipaddr' '10.18.1.101'
        option 'netmask' '255.255.128.0'
        option 'mtu' '1500'
        option 'dns'   '10.18.0.1 10.18.0.254'
--------------

If I decrease the mtu on the client that has no batman advanced to 1481, 
everything works fine.

Think we need help again^^
Clemens

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2010-06-17 14:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17  8:18 [B.A.T.M.A.N.] MTU/connection problem Clemens John
2010-06-17  8:44 ` Sven Eckelmann
2010-06-17 10:19   ` Clemens John
2010-06-17 12:07     ` Linus Lüssing
2010-06-17 12:35       ` Clemens John
2010-06-17 14:19       ` Clemens John [this message]
2010-06-17 15:19         ` Linus Lüssing
2010-06-17 16:16           ` Clemens John
2010-06-17 18:43             ` Marek Lindner
2010-06-18 10:34               ` Linus Lüssing
2010-06-18 17:40           ` Clemens John
2010-06-18 17:43             ` Marek Lindner
2010-06-18 17:47             ` Sven Eckelmann
2010-06-18 10:49 ` Michael Rack
2010-06-18 12:39   ` Linus Lüssing

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=201006171619.49916.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