From: Jonathan Thibault <jonathan@navigue.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: gretap default MTU question
Date: Wed, 9 Mar 2016 12:25:35 -0500 [thread overview]
Message-ID: <56E05C8F.1060901@navigue.com> (raw)
Hello good people of netdev,
When setting up gretap devices like so:
ip link add mydev type gretap remote 1.1.1.1 local 2.2.2.2 nopmtudisc
I'm observing two different behavior:
- On system A, the MTU of 'mydev' is set to the MTU of the 'parent'
interface (currently 1600) minus 38. All other interfaces on that system
have a default MTU of 1500, only the parent was forced to 1600 to avoid
fragmentation. So 'mydev' accurately figures out that its MTU is 1562.
- On system B, with the 'parent' interface MTU set to 1600 and all other
defaulting to 1500 (same situation as A), the MTU of 'mydev' gets set to
1462.
I'm trying to figure out which behavior is normal and what mechanism (if
any) causes the MTU to be set differently. In both cases the 'parent'
device has an MTU of 1600. The code in ip_gre.c does this:
dev->mtu = ETH_DATA_LEN - t_hlen - 4;
In this case, system B would have the expected behavior and I need some
way to explain what goes on with system A.
Of course I can force the MTU on system B but I was rather pleased with
the 'magic' on system A.
If anyone here familiar with this code can offer an explanation, it
would greatly ease my curiosity.
Jonathan
next reply other threads:[~2016-03-09 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 17:25 Jonathan Thibault [this message]
2016-03-10 14:30 ` gretap default MTU question Jonathan Thibault
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=56E05C8F.1060901@navigue.com \
--to=jonathan@navigue.com \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.