From: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org, steffen.klassert@secunet.com,
pablo@netfilter.org
Subject: Re: [PATCH nf-next] netfilter: nf_defrag_ipv4: Add sysctl to disable per interface
Date: Tue, 07 Nov 2017 11:58:40 -0700 [thread overview]
Message-ID: <8c74f85d5f668516766ed208cb8eb415@codeaurora.org> (raw)
In-Reply-To: <20171107103013.GA5512@breakpoint.cc>
> This breaks connection tracking for packets coming in via such
> interfaces.
>
> Nowadays we only enable defrag in a network namespace if the
> ip/nftables
> ruleset requires it, so this setting would be counter-productive.
Hi Florian
This usecase is run on an Android based device, so there will be only
the init namespace. While the specific rmnet interfaces for wifi calling
do
not require conntrack / iptables, some other scenarios like NAT on other
interfaces may trigger the load of the defrag module. Hence, we needed
this interface specific way of preventing defrag.
>> An example of this usage is for fixing wifi calling on networks
>> where certain routers are configured to drop fragments explicitly.
>
> Yay... does that happen for all frags or is this related to df bit
> somehow?
Based on our observations, the routers usually drop all fragmented
packets possibly for security reasons.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-11-07 18:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 2:28 [PATCH nf-next] netfilter: nf_defrag_ipv4: Add sysctl to disable per interface Subash Abhinov Kasiviswanathan
2017-11-04 9:07 ` Steffen Klassert
2017-11-07 10:30 ` Florian Westphal
2017-11-07 18:58 ` Subash Abhinov Kasiviswanathan [this message]
2017-11-08 4:34 ` Pablo Neira Ayuso
2017-11-08 20:46 ` Subash Abhinov Kasiviswanathan
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=8c74f85d5f668516766ed208cb8eb415@codeaurora.org \
--to=subashab@codeaurora.org \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.