From: David Miller <davem@davemloft.net>
To: Anders.Franzen@ericsson.com
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org
Subject: Re: [RFC] Make the ip6_tunnel reflect the true mtu.
Date: Tue, 26 Oct 2010 10:44:52 -0700 (PDT) [thread overview]
Message-ID: <20101026.104452.70198187.davem@davemloft.net> (raw)
In-Reply-To: <1287499123-25018-1-git-send-email-Anders.Franzen@ericsson.com>
From: Anders.Franzen@ericsson.com
Date: Tue, 19 Oct 2010 16:38:43 +0200
> From: Anders Franzen <anders.franzen@ericsson.com>
>
> The ip6_tunnel always assumes it consumes 40 bytes (ip6 hdr) of the mtu of the
> underlaying device. So for a normal ethernet bearer, the mtu of the ip6_tunnel is
> 1460.
> However, when creating a tunnel the encap limit option is enabled by default, and it
> consumes 8 bytes more, so the true mtu shall be 1452.
>
> I dont really know if this breaks some statement in some RFC, so this is a request for
> comments.
This patch looks fine to me, but please fully resubmit this with a
proper "Signed-off-by: " tag as per Documentation/SubmittingPatches
Thanks.
prev parent reply other threads:[~2010-10-26 17:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 14:38 [RFC] Make the ip6_tunnel reflect the true mtu Anders.Franzen
2010-10-26 17:44 ` David Miller [this message]
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=20101026.104452.70198187.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Anders.Franzen@ericsson.com \
--cc=eric.dumazet@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).