>From: Catherine Rowland <[EMAIL PROTECTED]>
>We are trying to forward (open up) a port on our firewall so that an
>outsider can test web pages on our internal test server:
>
> ipmasqadm portfw -a -P tcp -L 216.*.*.* 80 -R
>192.*.*.*:8000
> (where the 216 number is the firewall and the 192 number is
>the internal test server)
>
>I thought we were simply forwarding Port 80 of the firewall to Port 8000 on
>the internal server so that the user from outside would simply type:
>http://192.*.*.*:8000 and get the test server. Someone else says that the
>outsider types http://216.*.*.*:8000 and gets the test data. Neither one
of
>them work now anyway so something is wrong even if I am unclear on the
>concept.
The way your rules look, the "-L 216.*.*.* 80 -R 192.*.*.* 8000" means the
local port 80 gets mapped to the remote port on 8000. So your external URL
would be http://216.*.*.* and it should work (or http://216.*.*.*:80 if you
want to get technical about it), failing some other routing or setup gotcha.
BTW, your use of the colon in 192.*.*.*:8000 is incorrect syntax, but is
probably a typo, since ipmasqadm would have already choked on you if you
tried to type that in.
--
Gene Lee
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
