Nmap Development mailing list archives
Portscan: all 1000 ports filtered but tracert detects the device...why?
From: SheaO <shea () pobox sk>
Date: Sat, 14 Jan 2012 17:49:01 -0800 (PST)
Hi this might be a stupid question, im a bit of a newbie here, but maybe someone can clarify it for me. Im doing some portscanning with nmap on a IP-address, and get the result that all ports are closed (even tried using nmap -PN xxx.xxx.xxx.xxx). When I run a traceroute to a server on the same network, the router (xxx.xxx.xxx.xxx) with 1000 filtered ports, shows up! How can it be a part of the network if it's ports are all closed? Any suggestions? Clarification? /Shea -- View this message in context: http://old.nabble.com/Portscan%3A-all-1000-ports-filtered-but-tracert-detects-the-device...why--tp33137777p33137777.html Sent from the Nmap - Dev mailing list archive at Nabble.com. _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
Current thread:
- Portscan: all 1000 ports filtered but tracert detects the device...why? SheaO (Jan 14)
- Re: Sniffing: all 1000 ports filtered but tracert detects the device...why? Dagobert Michelsen (Jan 15)
- Re: Sniffing: all 1000 ports filtered but tracert detects the device...why? SheaO (Jan 15)
- Re: Sniffing: all 1000 ports filtered but tracert detects the device...why? Dagobert Michelsen (Jan 15)
- Re: Sniffing: all 1000 ports filtered but tracert detects the device...why? SheaO (Jan 15)
- Re: Sniffing: all 1000 ports filtered but tracert detects the device...why? Dagobert Michelsen (Jan 15)