From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netdev@vger.kernel.org, christian.perle@secunet.com,
steffen.klassert@secunet.com, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH net 0/3] net: fix netfilter defrag/ip tunnel pmtu blackhole
Date: Thu, 7 Jan 2021 23:14:03 +0100 [thread overview]
Message-ID: <20210107221403.GA15712@salvia> (raw)
In-Reply-To: <20210105231523.622-1-fw@strlen.de>
On Wed, Jan 06, 2021 at 12:15:20AM +0100, Florian Westphal wrote:
> Christian Perle reported a PMTU blackhole due to unexpected interaction
> between the ip defragmentation that comes with connection tracking and
> ip tunnels.
>
> Unfortunately setting 'nopmtudisc' on the tunnel breaks the test
> scenario even without netfilter.
>
> Christinas setup looks like this:
> +--------+ +---------+ +--------+
> |Router A|-------|Wanrouter|-------|Router B|
> | |.IPIP..| |..IPIP.| |
> +--------+ +---------+ +--------+
> / mtu 1400 \
> / \
> +--------+ +--------+
> |Client A| |Client B|
> +--------+ +--------+
>
> MTU is 1500 everywhere, except on Router A to Wanrouter and
> Wanrouter to Router B.
>
> Router A and Router B use IPIP tunnel interfaces to tunnel traffic
> between Client A and Client B over WAN.
>
> Client A sends a 1400 byte UDP datagram to Client B.
> This packet gets encapsulated in the IPIP tunnel.
>
> This works, packet is received on client B.
>
> When conntrack (or anything else that forces ip defragmentation) is
> enabled on Router A, the packet gets dropped on Router A after
> encapsulation because they exceed the link MTU.
>
> Setting the 'nopmtudisc' flag on the IPIP tunnel makes things worse,
> no packets pass even in the no-netfilter scenario.
>
> Patch one is a reproducer script for selftest infra.
>
> Patch two is a fix for 'nopmtudisc' behaviour so ip_tunnel will send
> an icmp error to Client A. This allows 'nopmtudisc' tunnel to forward
> the UDP datagrams.
>
> Patch three enables ip refragmentation for all reassembled packets, just
> like ipv6.
Acked-by: Pablo Neira Ayuso <pablo@netfilter.org>
Thanks.
next prev parent reply other threads:[~2021-01-07 22:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 12:12 BUG: IPv4 conntrack reassembles forwarded packets Christian Perle
2021-01-05 23:15 ` [PATCH net 0/3] net: fix netfilter defrag/ip tunnel pmtu blackhole Florian Westphal
2021-01-05 23:15 ` [PATCH net 1/3] selftests: netfilter: add selftest for ipip pmtu discovery with enabled connection tracking Florian Westphal
2021-01-05 23:15 ` [PATCH net 2/3] net: fix pmtu check in nopmtudisc mode Florian Westphal
2021-01-05 23:15 ` [PATCH net 3/3] net: ip: always refragment ip defragmented packets Florian Westphal
2021-01-07 7:52 ` Christian Perle
2021-01-07 22:14 ` Pablo Neira Ayuso [this message]
2021-01-07 22:45 ` [PATCH net 0/3] net: fix netfilter defrag/ip tunnel pmtu blackhole Jakub Kicinski
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=20210107221403.GA15712@salvia \
--to=pablo@netfilter.org \
--cc=christian.perle@secunet.com \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/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).