Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: contact@saschahlusiak.de
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] sit: allow ip fragmentation when using nopmtudisc to fix package loss
Date: Fri, 28 Aug 2009 23:54:04 -0700 (PDT)	[thread overview]
Message-ID: <20090828.235404.61171174.davem@davemloft.net> (raw)
In-Reply-To: <1251197322-3177-1-git-send-email-contact@saschahlusiak.de>

From: Sascha Hlusiak <contact@saschahlusiak.de>
Date: Tue, 25 Aug 2009 12:48:42 +0200

> if tunnel parameters have frag_off set to IP_DF, pmtudisc on the ipv4 link
> will be performed by deriving the mtu from the ipv4 link and setting the
> DF-Flag of the encapsulating IPv4 Header. If fragmentation is needed on the
> way, the IPv4 pmtu gets adjusted, the ipv6 package will be resent eventually,
> using the new and lower mtu and everyone is happy.
> 
> If the frag_off parameter is unset, the mtu for the tunnel will be derived
> from the tunnel device or the ipv6 pmtu, which might be higher than the ipv4
> pmtu. In that case we must allow the fragmentation of the IPv4 packet because
> the IPv6 mtu wouldn't 'learn' from the adjusted IPv4 pmtu, resulting in
> frequent icmp_frag_needed and package loss on the IPv6 layer.
> 
> This patch allows fragmentation when tunnel was created with parameter
> nopmtudisc, like in ipip/gre tunnels.
> 
> Signed-off-by: Sascha Hlusiak <contact@saschahlusiak.de>

Seems reasonable, applied to net-next-2.6, thanks!

      reply	other threads:[~2009-08-29  6:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-25 10:48 [PATCH] sit: allow ip fragmentation when using nopmtudisc to fix package loss Sascha Hlusiak
2009-08-29  6:54 ` 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=20090828.235404.61171174.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=contact@saschahlusiak.de \
    --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