/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting!
/* ALSO: Don't quote this header. It makes you look lame :-) */
hi joao,
many thanks for your answer.
i think, my question was misunderstanding, let me try again.
On Fri, 27 Oct 2000 10:13:00 -0200, Joco Neves
<[EMAIL PROTECTED]> wrote:
>Hi,
>Your portfw command is incorrect, because you are listening for connections
>to your $dmzIP and forwarding them to your $intIP. You should be listening
>on your $ExtIP, and forwarding to your $dmzIP:
> ipmasqadm portfw -a -P tcp -L $ExtIP 25 -R $dmzIP 25
> ipmasqadm portfw -a -P tcp -L $extIP 80 -R $dmzIP 80
no, the $dmzIP is an ip which exists (a.b.c.d). the server actually
was there and worked fine but
since i need the server on the internal net now (for customer reason),
but still would like to make the httpd externally accesibble, i need a
rule, which makes NAT to all packets, which are adressed to
212.254.210.228, they should be send to 192.168.0.10, where the server
now is.
|
| eth0
+--------------+
| | servers, a.b.c.d
| firewall +-----------------
| | eth1
+---+----------+
| eth2
|
|
| internal 192.168.0.x
| 192.168.0.10
so i need a rule which tells the kernel:
all packets which are going to a.b.c.d port 80 redirect to
192.168.0.10
jan
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
Admin requests can be handled at http://www.indyramp.com/masq-list/ --
THIS INCLUDES UNSUBSCRIBING!
or email to [EMAIL PROTECTED]
PLEASE read the HOWTO and search the archives before posting.
You can start your search at http://www.indyramp.com/masq/
Please keep general linux/unix/pc/internet questions off the list.
