From: Maxime Bizon <mbizon@freebox.fr>
To: Florian Westphal <fw@strlen.de>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, hannes@stressinduktion.org
Subject: Re: [PATCH -next, V3 0/2] net: force refragmentation for DF reassembed skbs
Date: Tue, 26 May 2015 11:57:25 +0200 [thread overview]
Message-ID: <1432634245.17881.57.camel@sakura.staff.proxad.net> (raw)
In-Reply-To: <20150522192651.GA3629@breakpoint.cc>
On Fri, 2015-05-22 at 21:26 +0200, Florian Westphal wrote:
Hello,
> But it does happen, see e.g. following bug report:
> http://marc.info/?l=linux-netdev&m=139870308431986&w=2
>
> Maxime, do you recall what type of traffic generates
> the DF-fragments you reported?
Yep
We are an ISP and provide our own home gateway to the subscribers, which
ends up routing traffic of a large range of end user devices.
In that case, the frag+DF traffic was seen in an exchange between a
femtocell and a femto GW during the IPsec IKE exchange, more precisely
on the IKE_AUTH message sent from the femto GW.
You can contact me privately if you need more details.
--
Maxime
next prev parent reply other threads:[~2015-05-26 10:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 14:32 [PATCH -next, V3 0/2] net: force refragmentation for DF reassembed skbs Florian Westphal
2015-05-22 14:32 ` [PATCH -next 1/2] net: ipv4: avoid repeated calls to ip_skb_dst_mtu helper Florian Westphal
2015-05-22 14:43 ` Hannes Frederic Sowa
2015-05-22 14:32 ` [PATCH -next 2/2] ip_fragment: don't forward defragmented DF packet Florian Westphal
2015-05-22 14:45 ` Hannes Frederic Sowa
2015-05-22 19:03 ` [PATCH -next, V3 0/2] net: force refragmentation for DF reassembed skbs David Miller
2015-05-22 19:26 ` Florian Westphal
2015-05-26 9:57 ` Maxime Bizon [this message]
2015-05-26 14:50 ` Florian Westphal
2015-05-22 22:52 ` Hannes Frederic Sowa
2015-05-27 17:04 ` David Miller
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=1432634245.17881.57.camel@sakura.staff.proxad.net \
--to=mbizon@freebox.fr \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=hannes@stressinduktion.org \
--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).