Re: potato: port forwarding question--
On Mon, 2001-09-10 at 22:35, will trillich wrote:
> we're trying to establish port forwarding so that a box internal
> on our lan (192.168.1.2) can serve requests through the
> debian/potato firewall, from 'out there'.
>
> i had this working at some point -- but now i can't get
> 'ipmasqadm portfw' working. (i may have missed a step, but
> /usr/share/doc/ didn't help ring any bells...)
>
> "[PUBLIC_IP]" is, of course, the box's actual ip address:
>
> # ipmasqadm portfw -a -P tcp -L [PUBLIC_IP] 7890 -R 192.168.1.2 80
>
> # ipmasqadm portfw -ln
> prot localaddr rediraddr lport rport pcnt pref
> TCP [PUBLIC_IP] 192.168.1.2 7890 80 10 10
>
> well, it LOOKS like it's up, but--
>
> # nmap [PUBLIC_IP] -p 7890
>
> Starting nmap V. 2.12 by Fyodor (fyodor@dhp.com, www.insecure.org/nmap/)
> No ports open for host server ([public_ip])
> Nmap run completed -- 1 IP address (1 host up) scanned in 0 seconds
>
> which is bolstered by the fact that if i try to connect to
> public port :7890 from outside i get deafening silence (unable
> to connect to host).
>
> is there another step i've forgotten? i'm on potato 2.2.17 and
> this was working earlier...
This works from inside your net right? The firewall machine can see
port 80 and it's active on the internal net right? I'm just wondering
if apache isn't running yet on the target machine.
--mike
Reply to: