When I open/forward a port and I start the Application, shouldnt I see the port in "listening" stage? I currently have a prog running that utilizes 4661 thru 4672 (emule) but I dont see it when I run netstat.....
Linux boxes access the Net, my Win XP box sits behind it running emule..
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
DNAT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpts:6881:7000 to:192.168.0.2
DNAT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpts:4661:4672 to:192.168.0.2
DNAT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:4711 to:192.168.0.2
DNAT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpts:10240:20480 to:192.168.0.2
DNAT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:41170 to:192.168.0.2
root@server:~# netstat -nluta
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 232 192.168.0.1:22 192.168.0.2:2159 ESTABLISHED
udp 65208 0 0.0.0.0:68 0.0.0.0:*
nope... because there is no service running on the server that's listening on that port...
the iptables filtering happens at a very low level... it is monitoring the packet traffic and as soon as it sees headers that contain that port info, it changes it and sends it on its way again...
so netstat wouldn't know anything about it ... there'd never be a port opened on the server for it because there doesn't need to be - it's being redirected to another computer
|All times are GMT -5. The time now is 12:41 PM.|