Re: nping doesn't recognise --icmp-code parameter

[Simon Taylor <simon1000001 () gmail com>]

Yes you are right!

Not sure how I missed that – must have typed it have or 6 times trying it!

 

Thanks for your help

 

[ec2-user@ip-100-64-0-200 ~]$ sudo nping --icmp --icmp-type destination-unreachable --icmp-code port 192.168.1.250

 

Starting Nping 0.7.12 ( https://nmap.org/nping ) at 2016-05-13 15:04 UTC

SENT (0.0025s) ICMP 100.64.0.200 > 192.168.1.250 Destination unreachable (type=3/code=3) ttl=64 id=20710 iplen=28 

SENT (1.0027s) ICMP 100.64.0.200 > 192.168.1.250 Destination unreachable (type=3/code=3) ttl=64 id=20710 iplen=28 

SENT (2.0040s) ICMP 100.64.0.200 > 192.168.1.250 Destination unreachable (type=3/code=3) ttl=64 id=20710 iplen=28 

SENT (3.0053s) ICMP 100.64.0.200 > 192.168.1.250 Destination unreachable (type=3/code=3) ttl=64 id=20710 iplen=28 

SENT (4.0066s) ICMP 100.64.0.200 > 192.168.1.250 Destination unreachable (type=3/code=3) ttl=64 id=20710 iplen=28 

 

Max rtt: N/A | Min rtt: N/A | Avg rtt: N/A

Raw packets sent: 5 (140B) | Rcvd: 0 (0B) | Lost: 5 (100.00%)

Nping done: 1 IP address pinged in 5.01 seconds

 

 

From: Luis MartinGarcia <luis.mgarc () gmail com>
Date: Friday, 13 May 2016 at 16:02
To: Simon Taylor <simon1000001 () gmail com>
Cc: "dev () nmap org" <dev () nmap org>
Subject: Re: nping doesn't recognise --icmp-code parameter

 

Hi Simon,

 

Thanks for contacting us. I think this is just a typo in your command. It looks like some copy&paste error introduced a 
weird hyphen there. If you look closely, it says "–-icmp-code" but it should say "--icmp-code". If you correct that, it 
will work ;)

 

Please let me know if you copied that from some documentation that we need to update. Thanks again. Best regards,

 

Luis MartinGarcia.

 

On Fri, May 13, 2016 at 1:24 PM, Simon Taylor <simon1000001 () gmail com> wrote:

nping doesn't recognise --icmp-code parameter

outputs the following when I try and use it

 

[ec2-user@ip-100-64-0-200 ~]$ sudo nping --icmp –-icmp-code 3  192.168.1.250

Failed to resolve given hostname/IP: –-icmp-code.  Note that you can't use '/mask' AND '1-4,7,100-' style IP ranges

Invalid target host specification: 3

 

Or as I expect it should be more accurately used:-

 

[ec2-user@ip-100-64-0-200 ~]$ sudo nping --icmp --icmp-type destination-unreachable –-icmp-code port 192.168.1.250

Failed to resolve given hostname/IP: –-icmp-code.  Note that you can't use '/mask' AND '1-4,7,100-' style IP ranges

Failed to resolve given hostname/IP: port.  Note that you can't use '/mask' AND '1-4,7,100-' style IP ranges

 

Starting Nping 0.7.12 ( https://nmap.org/nping ) at 2016-05-13 12:16 UTC

SENT (0.0058s) ICMP 100.64.0.200 > 192.168.1.250 Destination unreachable (type=3/code=0) ttl=64 id=42972 iplen=28

SENT (1.0060s) ICMP 100.64.0.200 > 192.168.1.250 Destination unreachable (type=3/code=0) ttl=64 id=42972 iplen=28

SENT (2.0073s) ICMP 100.64.0.200 > 192.168.1.250 Destination unreachable (type=3/code=0) ttl=64 id=42972 iplen=28

SENT (3.0086s) ICMP 100.64.0.200 > 192.168.1.250 Destination unreachable (type=3/code=0) ttl=64 id=42972 iplen=28

SENT (4.0099s) ICMP 100.64.0.200 > 192.168.1.250 Destination unreachable (type=3/code=0) ttl=64 id=42972 iplen=28

 

Max rtt: N/A | Min rtt: N/A | Avg rtt: N/A

Raw packets sent: 5 (140B) | Rcvd: 0 (0B) | Lost: 5 (100.00%)

Nping done: 1 IP address pinged in 5.01 seconds

 


_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/

 

_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/