From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Satish Patel <satish.txt@gmail.com>
Cc: Pascal Hambourg <pascal@plouf.fr.eu.org>,
Anton Danilov <littlesmilingcloud@gmail.com>,
"netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: block ip fragmented packet
Date: Fri, 11 Dec 2015 18:22:08 +0100 [thread overview]
Message-ID: <20151211172208.GA1580@salvia> (raw)
In-Reply-To: <ADD0C2D1-9082-4F33-AFBE-637A3778B5B8@gmail.com>
On Fri, Dec 11, 2015 at 07:53:12AM -0500, Satish Patel wrote:
> I'm testing this rule from remote machine and sending fragmented packet using hping3 utility.
>
> -f iptables option is not going to work if conntrack there.
>
> I don't know why it's so hard for iptable to block something like this.
You got nf_defrag_ipv4 loaded (it comes with conntrack), therefore,
fragments are reassembled before entering conntrack, then fragmented
back from the output path.
In nftables you can add a chain *before* priority -400 that should see
fragmented packets.
next prev parent reply other threads:[~2015-12-11 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 22:38 block ip fragmented packet Satish Patel
2015-12-11 6:27 ` Anton Danilov
2015-12-11 8:14 ` Pascal Hambourg
2015-12-11 12:53 ` Satish Patel
2015-12-11 17:22 ` Pablo Neira Ayuso [this message]
2015-12-11 18:40 ` Satish Patel
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=20151211172208.GA1580@salvia \
--to=pablo@netfilter.org \
--cc=littlesmilingcloud@gmail.com \
--cc=netfilter@vger.kernel.org \
--cc=pascal@plouf.fr.eu.org \
--cc=satish.txt@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox