From: Steffen Klassert <steffen.klassert@secunet.com>
To: lina.wang <lina.wang@mediatek.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org,
Jakub Kicinski <kuba@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
"David S . Miller" <davem@davemloft.net>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] xfrm:fragmented ipv4 tunnel packets in inner interface
Date: Tue, 15 Sep 2020 11:32:30 +0200 [thread overview]
Message-ID: <20200915093230.GS20687@gauss3.secunet.de> (raw)
In-Reply-To: <1600160722.5295.15.camel@mbjsdccf07>
On Tue, Sep 15, 2020 at 05:05:22PM +0800, lina.wang wrote:
>
> Yes, DF bit is not set.
...
> Those two packets are fragmented to one big udp packet, which payload is 1516B.
> After getting rid of tunnel header, it is also a udp packet, which payload is
> 1466 bytes.It didnot get any response for this packet.We guess it is dropped
> by router. Because if we reduced the length, it got response.
If the DF bit is not set, the router should fragment the packet. If it
does not do so, it is misconfigured. Do you have access to that router?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-09-15 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200909062613.18604-1-lina.wang@mediatek.com>
2020-09-15 7:30 ` [PATCH] xfrm:fragmented ipv4 tunnel packets in inner interface Steffen Klassert
[not found] ` <1600160722.5295.15.camel@mbjsdccf07>
2020-09-15 9:32 ` Steffen Klassert [this message]
[not found] ` <1600172260.2494.2.camel@mbjsdccf07>
2020-09-17 7:46 ` Steffen Klassert
[not found] ` <1600341549.32639.5.camel@mbjsdccf07>
[not found] ` <1604547381.23648.14.camel@mbjsdccf07>
2020-11-05 4:41 ` Maciej Żenczykowski
2020-11-05 4:52 ` Lorenzo Colitti
2020-11-09 9:58 ` Steffen Klassert
2020-11-09 19:38 ` Maciej Żenczykowski
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=20200915093230.GS20687@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=lina.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).