From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: [OT] Was: ESP does not hit the nat table
Date: Sun, 1 Aug 2004 23:28:16 +0100 [thread overview]
Message-ID: <200408012328.16124.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <D5C9032B2B09C64EA2409D6214E91AC9051218@asimail2.alphanumeric.com>
On Sunday 01 August 2004 8:03 pm, Jason Opperisano wrote:
> <OT>
> Where is the new-found obsession with dropping packets in the NAT table
> coming from? </OT>
Indeed. A few people here have commented recently that they prefer dropping
stuff in the PREROUTING nat table instead of waiting until it hits INPUT or
FORWARD, for things like spoofed packets or invalid TCP flag combinations.
I guess dropping things in nat is okay in exceptional circumstances, but I
hardly think the efficiency boost of dropping in nat instead of waiting until
the first filter table is reached makes any noticeable difference, and I
still advocate doing address translation in the nat tables, filtering
operations in the filter tables, and anything else in the mangle tables.
Just so long as you remember never to set a default policy other than ACCEPT
on any nat or mangle tables.....
Regards,
Antony.
--
I own three Windows books, published by O'Reilly. They are "Windows
Annoyances", "Office 97 Annoyances" and "Windows 98 Annoyances". That
pretty much sums it up for me.
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-08-01 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-01 19:03 ESP does not hit the nat table Jason Opperisano
2004-08-01 22:28 ` Antony Stone [this message]
2004-08-02 8:03 ` [OT] Was: " Jozsef Kadlecsik
-- strict thread matches above, loose matches on Subject: below --
2004-08-02 14:49 Kashyap Ashwin
2004-08-03 12:42 Jason Opperisano
2004-08-04 8:49 ` Antony Stone
2004-08-05 4:36 ` Ming-Ching Tiew
2004-08-05 14:26 Kashyap Ashwin
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=200408012328.16124.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--cc=netfilter@lists.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