From: Nikolay Kichukov <hijacker@oldum.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: James Lay <jlay@slave-tothe-box.net>,
Netfilter <netfilter@vger.kernel.org>
Subject: Re: Blocking in NAT
Date: Mon, 09 May 2011 11:54:24 +0300 [thread overview]
Message-ID: <4DC7ABC0.6030304@oldum.net> (raw)
In-Reply-To: <alpine.LNX.2.01.1105071653100.31190@obet.zrqbmnf.qr>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
or just block it in the -t mangle -A PREROUTING table.
Have a look at the packet flow diagram and you will be good to go!
Cheers,
- -Nik
On 05/07/2011 05:54 PM, Jan Engelhardt wrote:
> On Saturday 2011-05-07 15:20, James Lay wrote:
>
>> Hey All,
>>
>> So?once upon a time one could block using NAT, which was nice since I run
>> a spamfilter that grabs everything coming in to port 25 with:
>>
>> iptables -t nat -A PREROUTING -m physdev --physdev-in eth0 ! -s 10.0.0.0/8
>> -p tcp --dport 25 -j DNAT --to-destination 10.0.0.1:25
>>
>> For some reason, filtering in the nat table was deemed bad, so now I can
>> no longer drop things there. So my question is, how do I block say...a
>> spammer from sending to port 25 now? I can't use:
>>
>> iptables -t nat -i PREROUTING -m physdev --physdev-in eth0 -s naughty.ip
>> -j DROP
>> or
>> iptables -t nat -i PREROUTING -m physdev --physdev-in eth0 -s naughty.ip
>> -j REJECT
>
>
> iptables -A INPUT (or FORWARD, depending on use case) -m physdev
> --physdev-in eth0 -s naughty.ip (-p tcp --dport 25) -j REJECT
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNx6vAAAoJEDFLYVOGGjgXS30H/RmE9stI4q8nWbZ03ObdIJ5H
gMQiZ2EST/Rz6q/OL37bGdk5bkZcRhj72AqRkrxB57lZDDpsk8uEwIlhoW61J3uI
dFXrGRZAPtCOd4yrGoILKBuK0hLOr/qWHGhxyCXw+Oa4Boq1LUjQHmJSRynss7Ui
caSjV9AWq4f6hmY3tLTQd8pXsi5zTOGKHSYwlRuoPeiUIiHZc9QkFAA6BOMw3Pl5
2NjjpOYAiRwt7/qbCWHaQkqsxvv3JD3tO/RT+Mg41cuOnuLj5945h7IktkbxVKj7
p7xvWJtUHDyD01A+rhb7B3lUn95eM3Hv3nBsAhnbcsXMQl/TO23/2jnsGuvxcbs=
=Hqow
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-05-09 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 13:20 Blocking in NAT James Lay
2011-05-07 14:54 ` Jan Engelhardt
2011-05-09 8:54 ` Nikolay Kichukov [this message]
2011-05-09 9:39 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2011-05-08 16:09 James Lay
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=4DC7ABC0.6030304@oldum.net \
--to=hijacker@oldum.net \
--cc=jengelh@medozas.de \
--cc=jlay@slave-tothe-box.net \
--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 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.