From: Steffen Klassert <steffen.klassert@secunet.com>
To: Bram Yvahk <bram-yvahk@mail.wizbit.be>
Cc: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH ipsec/vti 0/2] Fragmentation of IPv4 in VTI
Date: Thu, 21 Mar 2019 16:16:30 +0100 [thread overview]
Message-ID: <20190321151630.GA25855@gauss3.secunet.de> (raw)
In-Reply-To: <1552865877-13401-1-git-send-email-bram-yvahk@mail.wizbit.be>
On Sun, Mar 17, 2019 at 11:37:55PM +0000, Bram Yvahk wrote:
> We've experienced an issue with VTI when the path-mtu is smaller than the size
> of the "client" packet.
>
> What happens: IPv4 packet from the client (i.e. another system in the LAN)
> attempts to transmit some data; IPv4 header shows that 'DF' bit is not set but
> still the client receives ICMPv4 "need-to-frag" message [which the client does
> not expect and ignores].
>
> Example: $ ping -s 1300 -M dont -c5 192.168.235.2
> PING 192.168.235.3 (192.168.235.3) 1300(1328) bytes of data.
> From 192.168.236.254 icmp_seq=1 Frag needed and DF set (mtu = 1214)
> From 192.168.236.254 icmp_seq=2 Frag needed and DF set (mtu = 1214)
> From 192.168.236.254 icmp_seq=3 Frag needed and DF set (mtu = 1214)
> From 192.168.236.254 icmp_seq=4 Frag needed and DF set (mtu = 1214)
> From 192.168.236.254 icmp_seq=5 Frag needed and DF set (mtu = 1214)
>
> --- 192.168.235.3 ping statistics ---
> 5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 3999ms
Hm, this works here. Can you show how you setup the vti device?
Some tunnel configuration options (set ttl etc.) force to have
the DF bit set.
next prev parent reply other threads:[~2019-03-21 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 23:37 [PATCH ipsec/vti 0/2] Fragmentation of IPv4 in VTI Bram Yvahk
2019-03-17 23:37 ` [PATCH ipsec/vti 1/2] vti: fragment IPv4 packets when DF bit is not set Bram Yvahk
2019-03-17 23:52 ` Bram Yvahk
2019-03-17 23:37 ` [PATCH ipsec/vti 2/2] vti6: process icmp msg when IPv6 is fragmented Bram Yvahk
2019-03-21 15:16 ` Steffen Klassert [this message]
2019-03-21 18:33 ` [PATCH ipsec/vti 0/2] Fragmentation of IPv4 in VTI Bram Yvahk
2019-03-22 20:46 ` Bram Yvahk
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=20190321151630.GA25855@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=bram-yvahk@mail.wizbit.be \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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).