From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pascal Hambourg Subject: Re: no ssh on eth0 Date: Mon, 31 Jul 2006 15:44:01 +0200 Message-ID: <44CE0921.7050103@plouf.fr.eu.org> References: <1154239260.5429.2.camel@nirvana.aurokruti.in> <87fygje700.fsf@newton.gmurray.org.uk> <44CCA802.2090403@plouf.fr.eu.org> <44CCE712.4070907@plouf.fr.eu.org> <98ab1181f512c188a486f7e3667bb2c4@former03.de> <44CD10E0.501@plouf.fr.eu.org> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-bounces@lists.netfilter.org Errors-To: netfilter-bounces@lists.netfilter.org Content-Type: text/plain; charset="iso-8859-1"; format="flowed" To: netfilter@lists.netfilter.org former03 | Baltasar Cevc a =E9crit : >=20 >> Why ? What is the difference with or without NAT ? >=20 > You can filter out all incoming packets to local IP addresses on the wa= n=20 > interface before NAT is done; No you can't, unless you intend to do filtering in PREROUTING chain of=20 the 'mangle' table. > if you just use MASQUERADE for outgoing=20 > packets, "iptables -A INPUT -i eth0.-d 192.168.0.0/16 -j DROP". I just don't see how it is different whether you have NAT/MASQUERADE or=20 not. To me filtering and NAT in iptables are fundamentally independent.