From: Guillaume <silencer@free-4ever.net>
To: netfilter@lists.netfilter.org
Subject: Re: Help with IPtables and NAT
Date: Sat, 22 Jul 2006 13:18:05 +0200 [thread overview]
Message-ID: <44C2096D.2050602@free-4ever.net> (raw)
In-Reply-To: <44C1FE22.70209@plouf.fr.eu.org>
Pascal Hambourg a écrit :
> Guillaume a écrit :
>>
>> I think you 2 problems in your rules:
>> - The chains in NAT table must not be set to drop. NO filtering in
>> nat table.
>> - You forgot to add the rules to autorise traffic coming from eth0:0
>> to your internal host. After a DNAT rule, you need to explicitely
>> autorise the corresponding traffic.
>> Ab i think, I've don't read any rule related to that.
>>
>> For example, you set this rule:
>> iptables -t nat -A PREROUTING -d 172.10.10.2 -p tcp --dport 80 -j DNAT
>> --to-dest 192.168.0.2
>> You must set this rule:
>> iptables -t filter -A FORWARD -i eth0:0 -p tcp -d 192.168.0.2 --dport
>> 80 -j ACCEPT
>> And the same for all incoming traffics.
>
> This is correct except for one detail : the interface eth0:0 does not
> exist. It is only an alias and is not used by either the routing nor
> iptables. You muse use the real interface name, eth0.
>
hhhmmm
Ok :-)
I never use alias on interface... :-)
Thx for correcting me
Guillaume
--
Guillaume
E-mail: silencer_<at>_free-4ever_<dot>_net
Blog: http://guillaume.free-4ever.net
----
Site: http://www.free-4ever.net
next prev parent reply other threads:[~2006-07-22 11:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-21 23:19 Help with IPtables and NAT James Marcinek
2006-07-21 23:32 ` Gary W. Smith
2006-07-22 0:58 ` Pascal Hambourg
2006-07-24 15:16 ` Martijn Lievaart
[not found] ` <42950.2001:888:19e1::53.1153754175.squirrel@dexter>
2006-07-28 10:31 ` Pascal Hambourg
2006-07-22 8:23 ` Guillaume
2006-07-22 10:29 ` Pascal Hambourg
2006-07-22 11:18 ` Guillaume [this message]
2006-07-22 14:38 ` James Marcinek
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=44C2096D.2050602@free-4ever.net \
--to=silencer@free-4ever.net \
--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 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.