Nick Guenther wrote: > On 2/3/06, Melameth, Daniel D. <[EMAIL PROTECTED]> wrote: > > I don't get it--it appears nmap is broken. Perhaps I'm overlooking > > something obvious, but any thoughts appreciated... > > > > > > An nmap scan gives me this: > > > > $ sudo nmap 208.139.x.x > > > > Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2006-02-03 > > 19:45 MST Note: Host seems down. If it is really up, but blocking > > our ping probes, try -P0 Nmap finished: 1 IP address (0 hosts up) > > scanned in 2.109 seconds > > > > Try following the suggestion: > $ sudo nmap -P0 208.139.x.x > > and then if that still doesn't work, post again. Perhaps nmap has a > different sort of ping than the standard?
Same issue... It's as if nmap is blind to the return packets... $ sudo nmap -P0 208.139.x.x Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2006-02-03 20:30 MST All 1663 scanned ports on 208.139.x.x (208.139.x.x) are: filtered Nmap finished: 1 IP address (1 host up) scanned in 338.874 seconds $ sudo tcpdump -nqi pppoe0 src host 208.139.x.x and dst host 209.180.x.x tcpdump: listening on pppoe0, link-type PPP_ETHER 20:30:30.036433 208.139.x.x.80 > 209.180.x.x.58108: tcp 0 (DF) 20:30:30.052043 208.139.x.x.22 > 209.180.x.x.58108: tcp 0 (DF) 20:30:32.059800 208.139.x.x.22 > 209.180.x.x.58109: tcp 0 (DF) 20:30:32.066842 208.139.x.x.80 > 209.180.x.x.58109: tcp 0 (DF) $ sudo tcpdump -nqi pflog0 tcpdump: WARNING: pflog0: no IPv4 address assigned tcpdump: listening on pflog0, link-type PFLOG
