On Sun, 2008-01-27 at 00:28 -0500, Michael Quick wrote: > > Getting to the point, just turn off the iptables firewall for testing > purposes by typing /sbin/service iptables stop . Now any listening > ports can be accessed from at least within it's own collision domain. > The next step is to see if that port is accessible through your router, > use the nmap command for that. Figure out the ip address of the router > (i.e. 67.1.2.3), then from the command line type nmap -O 67.1.2.3, and > it will return the available ports. Your port should be one of them. > If not, look at the hardware router. >
> Thanks for your very informative post. I've just been on broadband for six months. Your post made me aware that I've got a lot more to learn about networking than I realized. You helped me out of what would otherwise have been a very difficult jam. I performed the test you recommended. It confirmed your initial conjecture that I had not set up port-forwarding correctly. My router is a Westell 6100-E90 DSL modem/router supplied by Verizon. A user manual was not included on the install CD. I was relying on documentation I found on the web for older editions of the Westell 6100. The user interface for my model had changed sufficiently to trip me up in correctly setting up port-forwarding. Thanks for showing me how to scan open ports on the router. I was not aware of nmap and did not know of a way to test if port-forwarding was functioning. I corrected the port-forwarding setup on the router. The Azureus NAT test now passes. So I'm now ready to move on and try to get Azureus functioning. There are a few things about this experience that are puzzling me. 1. After correcting the port-forwarding setup, I started Azureus and reran nmap. It still didn't show anything for port 60112. (Even though the Azureus NAT test for port 60112 passed.) Here is the output: ==================================================================================================== [EMAIL PROTECTED] aweiner]# nmap -O 192.168.1.1 Starting Nmap 4.20 ( http://insecure.org ) at 2008-01-27 21:23 EST Interesting ports on dslrouter (192.168.1.1): Not shown: 1696 closed ports PORT STATE SERVICE 80/tcp open http MAC Address: 00:18:3A:53:F7:FB (Westell Technologies) No exact OS matches for host (If you know what OS is running on it, see http://insecure.org/nmap/submit/ ). TCP/IP fingerprint: OS:SCAN(V=4.20%D=1/27%OT=80%CT=1%CU=34225%PV=Y%DS=1%G=Y%M=00183A% TM=479D3CC OS:3%P=i686-redhat-linux-gnu)SEQ(SP=99%GCD=1%ISR=9F%TI=I%II=I%SS=S% TS=1)SEQ OS:(SP=9A%GCD=1%ISR=A0%TI=I%II=I%SS=S%TS=1)SEQ(SP=9A%GCD=1%ISR=A1%TI=I% II=I OS:%SS=S%TS=1)SEQ(SP=9B%GCD=1%ISR=A0%TI=I%II=I%SS=S%TS=1)SEQ(SP=9B% GCD=1%IS OS:R=A1%TI=I%II=I%SS=S%TS=1)OPS(O1=M5B4NW0NNT11%O2=M5B4NW0NNT11% O3=M5B4NW0N OS:NT11%O4=M5B4NW0NNT11%O5=M5B4NW0NNT11%O6=M5B4NNT11)WIN(W1=2000% W2=2000%W3 OS:=2000%W4=2000%W5=2000%W6=2000)ECN(R=Y%DF=Y%T=40%W=2000%O=M5B4NW0%CC=N %Q= OS:)T1(R=Y%DF=Y%T=40%S=O%A=S+%F=AS%RD=0%Q=)T2(R=N)T3(R=Y%DF=Y%T=40% W=2000%S OS:=O%A=O%F=AS%O=M5B4NW0NNT11%RD=0%Q=)T4(R=Y%DF=N%T=40%W=2000%S=A%A=Z% F=R%O OS:=%RD=0%Q=)T5(R=Y%DF=N%T=40%W=0%S=Z%A=S+%F=AR%O=%RD=0%Q=)T6(R=Y%DF=N% T=40 OS:%W=0%S=A%A=Z%F=R%O=%RD=0%Q=)T7(R=Y%DF=N%T=40%W=0%S=Z%A=S%F=AR%O=% RD=0%Q= OS:)U1(R=Y%DF=N%T=40%TOS=0%IPL=38%UN=0%RIPL=G%RID=G%RIPCK=Z%RUCK=0%RUL=G %RU OS:D=G)IE(R=Y%DFI=S%T=40%TOSI=S%CD=S%SI=S%DLI=S) Uptime: 0.312 days (since Sun Jan 27 13:55:02 2008) Network Distance: 1 hop OS detection performed. Please report any incorrect results at http://insecure.org/nmap/submit/ . Nmap finished: 1 IP address (1 host up) scanned in 14.466 seconds ======================================================================================================================== 2. Iptables is logging large numbers of UDP packets to port 60112. I thought a rule had been added to Iptables to allow UDP packets to port 60112 to pass through. _______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Feb 6 - DBUS Mar 5 - Setting up a platform-independent home/small office network using Linux
