From: Eray Aslan <eray.aslan@caf.com.tr>
To: netfilter@vger.kernel.org
Subject: Re: [ANNOUNCE] Release of iptables-1.4.3.2
Date: Tue, 07 Apr 2009 07:26:08 +0300 [thread overview]
Message-ID: <49DAD5E0.9020303@caf.com.tr> (raw)
In-Reply-To: <49DA0F49.4090802@conversis.de>
On 06.04.2009 17:18, Dennis J. wrote:
> What does "deprecation of NAT filtering" entail exactly?
# /sbin/iptables -V
iptables v1.4.2
# /sbin/iptables -t nat -A OUTPUT -p tcp --dport 10000 -j DROP
The "nat" table is not intended for filtering, hence the use of DROP is
deprecated and will permanently be disabled in the next iptables
release. Please adjust your scripts.
# /sbin/iptables -L -nvx -t nat
[...]
Chain OUTPUT (policy ACCEPT 45827 packets, 3301166 bytes)
pkts bytes target prot opt in out source
destination
0 0 DROP tcp -- * * 0.0.0.0/0
0.0.0.0/0 tcp dpt:10000
#
versus
# /sbin/iptables -V
iptables v1.4.3.1
# /sbin/iptables -t nat -A OUTPUT -p tcp --dport 10000 -j DROP
iptables v1.4.3.1:
The "nat" table is not intended for filtering, the use of DROP is
therefore inhibited.
Try `iptables -h' or 'iptables --help' for more information.
# /sbin/iptables -L -nvx -t nat
[...]
Chain OUTPUT (policy ACCEPT 5115 packets, 415189 bytes)
pkts bytes target prot opt in out source
destination
#
Do not filter in the nat table and you will be fine.
--
Eray
next prev parent reply other threads:[~2009-04-07 4:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 11:38 [ANNOUNCE] Release of iptables-1.4.3.2 Pablo Neira Ayuso
2009-04-06 14:18 ` Dennis J.
2009-04-07 4:26 ` Eray Aslan [this message]
2009-04-09 8:31 ` Mart Frauenlob
2009-04-09 13:27 ` Eray Aslan
2009-04-09 17:02 ` Payam Chychi
2009-04-09 19:27 ` Vincent Bernat
2009-04-09 13:29 ` Eray Aslan
2009-04-10 7:21 ` Mart Frauenlob
2009-04-10 10:54 ` The death of policy (WAS -> Re: [ANNOUNCE] Release of iptables-1.4.3.2) Gáspár Lajos
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=49DAD5E0.9020303@caf.com.tr \
--to=eray.aslan@caf.com.tr \
--cc=netfilter@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