From: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, fw@strlen.de, kadlec@blackhole.kfki.hu
Subject: Re: [PATCH nf-next] netfilter: nf_defrag_ipv4: Skip defrag if NOTRACK is set
Date: Sat, 09 Dec 2017 19:06:14 -0700 [thread overview]
Message-ID: <dd0bf36c855a8e2ea41039f2282fb9ff@codeaurora.org> (raw)
In-Reply-To: <20171209151018.GA5551@salvia>
> Would it work for you if this is specific via global modparam? I'm
> telling this because:
>
> 1) This is changing the default behaviour, which is always tricky.
> 2) This is already solved in nftables, so whatever solution that we
> apply, it should be iptables specific.
>
> If modparam is fine, just placing a line into
> /etc/modprobe.d/options.conf (or similar) should be good enough to
> store that you're requesting raw hook registration before defrag.
>
> Let me know,
> Thanks!
Hi Pablo
Can you explain a bit more about the /etc/modprobe.d/ option and how
it would be configured for this? /etc/modprobe.d/ doesnt exist on
Android based Linux systems so it might be a problem for me.
Would it be an acceptable solution to create a kernel config for this
particular feature instead?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-12-10 2:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 1:37 [PATCH nf-next] netfilter: nf_defrag_ipv4: Skip defrag if NOTRACK is set Subash Abhinov Kasiviswanathan
2017-12-09 15:10 ` Pablo Neira Ayuso
2017-12-10 2:06 ` Subash Abhinov Kasiviswanathan [this message]
2017-12-10 14:53 ` Pablo Neira Ayuso
2017-12-11 7:13 ` 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=dd0bf36c855a8e2ea41039f2282fb9ff@codeaurora.org \
--to=subashab@codeaurora.org \
--cc=fw@strlen.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).