Nmap Development mailing list archives
ICMP issues for standard ping?
From: "Mike ." <dmciscobgp () hotmail com>
Date: Tue, 23 Feb 2016 20:32:48 +0000
i typed this all out before. either no one cared or it got lost in the shuffle. gonna send again because i am still bewildered. ok--setup is simple. 1 laptop, win7, one home cisco router all connected ethernet. no firewall running and no filtering i did on the cisco. when i go to a prompt and do a simple ping echo type 8 i get this for the traffic. me sending, me receiving: (pinging my TIVO box: 192.168.0.10) IP (tos 0x0, ttl 128, id 26085, offset 0, flags [none], proto: ICMP (1), length: 60) 192.168.0.16 > 192.168.0.10: ICMP echo request, id 1, seq 358, length 40 IP (tos 0x0, ttl 64, id 65278, offset 0, flags [none], proto: ICMP (1), length: 60) 192.168.0.10 > 192.168.0.16: ICMP echo reply, id 1, seq 358, length 40 same thing with NMAP now. and not the same results. my question is WHY? why am i sending that port unreachable using NMAP? and is this an NMAP thing or mine is the question. thank you command used: nmap -sn -PE -vv -n 192.168.0.10 -disable-arp-ping IP (tos 0x0, ttl 40, id 62683, offset 0, flags [none], proto: ICMP (1), length: 28) 192.168.0.16 > 192.168.0.10: ICMP echo request, id 19712, seq 0, length 8 IP (tos 0x0, ttl 64, id 65282, offset 0, flags [none], proto: ICMP (1), length: 28) 192.168.0.10 > 192.168.0.16: ICMP echo reply, id 19712, seq 0, length 8 IP (tos 0x0, ttl 128, id 26454, offset 0, flags [none], proto: ICMP (1), length: 56) 192.168.0.16 > 192.168.0.10: ICMP 192.168.0.16 protocol 1 unreachable, leng th 36 (is the sequence supposed to be 0?) Mike
_______________________________________________ Sent through the dev mailing list https://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
Current thread:
- ICMP issues for standard ping? Mike . (Feb 23)
- Re: ICMP issues for standard ping? jérémie banier (Feb 23)