More Issues with ipmasqadm
Tyler Hall
plug-discuss@lists.PLUG.phoenix.az.us
Thu, 10 Jan 2002 19:58:31 -0700
Greetings (once again)
I sent a e-mail a few weeks ago about port forwarding not working right, and
got a respose, and I got it to work. But, of course something had to
happen. The hard drive in that machine died today so I had to re-format,
and now the port forwarding isn't working again.
These are the 3 lines in my /etc/rc.d/rc.local
/usr/sbin/ipmasqadm portfw -a -P tcp -L 208.142.86.2 5900 -R 192.168.0.2
5900
/usr/sbin/ipmasqadm portfw -a -P tcp -L 208.142.86.2 9999 -R 192.168.0.3
6499
/usr/sbin/ipmasqadm portfw -a -P tcp -L 208.142.86.2 9998 -R 192.168.0.4
3389
and when I do a port scan from another box;
[thall@wampa thall]$ nmap 208.142.86.2 -p 1-9999
Starting nmap V. 2.54BETA22 ( www.insecure.org/nmap/ )
Interesting ports on (208.142.86.2):
(The 9995 ports scanned but not shown below are in state: closed)
Port State Service
22/tcp open ssh
5900/tcp filtered vnc
9998/tcp open unknown
9999/tcp filtered unknown
Only 9998 is open, the other 2 are filtered, so I only can reach that box,
and not the others, yet the line is the same. Anyone have any ideas?