From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: b.a.t.m.a.n@lists.open-mesh.net
Subject: Re: [B.A.T.M.A.N.] MTU/connection problem
Date: Thu, 17 Jun 2010 10:44:59 +0200 [thread overview]
Message-ID: <201006171045.00578.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <201006171018.47209.clemens-john@gmx.de>
[-- Attachment #1: Type: Text/Plain, Size: 2223 bytes --]
Clemens John wrote:
> Hi,
>
> I have a problem to connect to the Internet. We are using Batman advanced
> 0.2.1 and IPv4 here in oldenburg. Our setup looks like this:
>
> Laptop-[wifi]->Fonera-[wifi]->Dir300-->OpenVPN-->
> virtual OpenWrt machine-->internet.
>
> The default route of the laptop goes to the virtual OpenWrt machine wich
> provides an Internet connection.
>
> I can acces google (wget google.de) but not heise.de or golem.de. I´m not
> verry familar with network configurations but I heared that this might be
> an mtu problem.
>
> All devices in the network (tap0, ath0, ath1, wifi0) have an mtu of 1524
> except bat0 and br-mesh which have an mtu of 1500.
>
> Our routers are configured to bridge connections from non batman devices
> (like the laptop) to bat0. This is done in the device "br-mesh".
>
> Everythink works fine, except I can´t connect to internet websites that are
> not google.de.
>
> When I decrease the mtu of the wireless device of the laptop to 1476
> everything works fine.
> But I have to do this by hand and on a client this is bad.
>
> Does anybody know what I´m doing wrong?
Sounds a little bit like a device is configured wrong. Lets go through the
devices:
Laptop:
* WiFi: MTU: 1500
Fonera:
* Incoming (to Laptop) WiFi: MTU 1500
* Outgoing (to Dir300) WiFi: MTU 1530
* Bridge (has bat0 and Incoming WiFi included): MTU 1500
* bat0 (has only Outgoing WiFi included): MTU 1500
Dir300:
* Incoming (to Fonera) WiFi: MTU 1530
* bat0 (only incoming device included): MTU 1500
This should work till Dir300. Now send 1500 Bytes large packets to each
interesting partner (fonera, dir300) and check were it drops.
This can be done using `ping -M do -s 1472 $IP`.
If it works till dir300 and drops somewhere in the openvpn/virtual
openwrt/internet connection then please check there. If it drops before then
please check your configuration (running, not configuration files) and try to
summarize those devices as I tried to do above.
How exactly is openvpn your connection to the internet configured? Do they
work in an mode which adds extra headers? Do they fragment packets?
Best regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-06-17 8:44 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 [this message]
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
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=201006171045.00578.sven.eckelmann@gmx.de \
--to=sven.eckelmann@gmx.de \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
--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