netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Bizon <mbizon@freebox.fr>
To: Patrick McHardy <kaber@trash.net>
Cc: Eric Dumazet <edumazet@google.com>,
	davem@davemloft.net, netdev <netdev@vger.kernel.org>
Subject: Re: problem forwarding IP fragments with DF bit set (caused by ipv4: fix path MTU discovery with connection tracking)
Date: Tue, 29 Apr 2014 16:42:15 +0200	[thread overview]
Message-ID: <1398782535.4033.11.camel@sakura.staff.proxad.net> (raw)
In-Reply-To: <20140429143324.GB12781@macbook.localnet>


On Tue, 2014-04-29 at 15:33 +0100, Patrick McHardy wrote:

> That is the correct behaviour.

is it ?

say the remote host is sending two 1000 bytes fragments, with DF set to
me and my MTU is 1500, I'm suppose to route these packets to an
interface with the same MTU.

without conntrack both fragments are correctly forwarded

with conntrack, the original packet is re-assembled, then instead of
forwarding it, we send a "frag needed mtu = 1500" to the remote host,
which never sent any packets bigger than 1500 at the beginning.

-- 
Maxime

  reply	other threads:[~2014-04-29 14:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28 16:37 problem forwarding IP fragments with DF bit set (caused by ipv4: fix path MTU discovery with connection tracking) Maxime Bizon
2014-04-28 17:59 ` Maxime Bizon
2014-04-29 14:35   ` Patrick McHardy
2014-04-29 14:33 ` Patrick McHardy
2014-04-29 14:42   ` Maxime Bizon [this message]
2014-04-29 14:45     ` Patrick McHardy
2014-04-29 15:23       ` Maxime Bizon
2014-04-29 15:37         ` Eric Dumazet
2014-04-29 20:13           ` Florian Westphal
2014-04-30 14:34           ` Maxime Bizon

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=1398782535.4033.11.camel@sakura.staff.proxad.net \
    --to=mbizon@freebox.fr \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kaber@trash.net \
    --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).