Difference between revisions of "Nping"
Jump to navigation
Jump to search
↑ https://nmap.org/
| (5 intermediate revisions by 3 users not shown) | |||
| Line 2: | Line 2: | ||
Install <code>[[nmap]]</code><ref>https://nmap.org/</ref> tool, available at least for Windows, Mac and Linux and execute <code>[[nping --tcp]] -p 3306 172.16.22.218</code> to test tcp connectivity for port [[3306]] in host 172.16.22.218: | Install <code>[[nmap]]</code><ref>https://nmap.org/</ref> tool, available at least for Windows, Mac and Linux and execute <code>[[nping --tcp]] -p 3306 172.16.22.218</code> to test tcp connectivity for port [[3306]] in host 172.16.22.218: | ||
| + | [[nping --tcp]] -p [[5432]] your_postgres_host -q | ||
| − | nping --[[tcp]] -p 3306 172.16.22.218 [[-c 0]] | + | nping --[[tcp]] -p [[3306]] 172.16.22.218 [[-c 0]] |
Starting Nping 0.6.47 ( http://nmap.org/nping ) at 2019-03-12 09:47 UTC | Starting Nping 0.6.47 ( http://nmap.org/nping ) at 2019-03-12 09:47 UTC | ||
SENT (0.0125s) TCP 172.16.22.18:2734 > 172.16.22.218:3306 S ttl=64 id=56345 iplen=40 seq=1546620167 win=1480 | SENT (0.0125s) TCP 172.16.22.18:2734 > 172.16.22.218:3306 S ttl=64 id=56345 iplen=40 seq=1546620167 win=1480 | ||
| Line 24: | Line 25: | ||
nping -tcp -p 443 google.com -c 0 | nping -tcp -p 443 google.com -c 0 | ||
-c 0 number of probes. Default 5. If 0 run continuously. | -c 0 number of probes. Default 5. If 0 run continuously. | ||
| − | |||
| − | |||
| − | |||
== Related terms == | == Related terms == | ||
| Line 32: | Line 30: | ||
* [[Host sweep]] | * [[Host sweep]] | ||
* [[Nagios]]: <code>[[check_tcp]]</code> | * [[Nagios]]: <code>[[check_tcp]]</code> | ||
| + | * <code>[[nc -v]]</code> | ||
== See also == | == See also == | ||
| − | |||
* {{mtr}} | * {{mtr}} | ||
* {{ping}} | * {{ping}} | ||
* {{network performance}} | * {{network performance}} | ||
| − | * {{ | + | * {{nmap}} |
| + | |||
[[Category:ping]] | [[Category:ping]] | ||
Latest revision as of 14:03, 22 January 2024
Install nmap[1] tool, available at least for Windows, Mac and Linux and execute nping --tcp -p 3306 172.16.22.218 to test tcp connectivity for port 3306 in host 172.16.22.218:
nping --tcp -p 5432 your_postgres_host -q
nping --tcp -p 3306 172.16.22.218 -c 0 Starting Nping 0.6.47 ( http://nmap.org/nping ) at 2019-03-12 09:47 UTC SENT (0.0125s) TCP 172.16.22.18:2734 > 172.16.22.218:3306 S ttl=64 id=56345 iplen=40 seq=1546620167 win=1480 SENT (1.0127s) TCP 172.16.22.18:2734 > 172.16.22.218:3306 S ttl=64 id=56345 iplen=40 seq=1546620167 win=1480 RCVD (1.0129s) TCP 172.16.22.218:3306 > 172.16.22.18:2734 SA ttl=64 id=0 iplen=44 seq=1638376953 win=29200 <mss 1460> SENT (2.0141s) TCP 172.16.22.18:2734 > 172.16.22.218:3306 S ttl=64 id=56345 iplen=40 seq=1546620167 win=1480 RCVD (2.0143s) TCP 172.16.22.218:3306 > 172.16.22.18:2734 SA ttl=64 id=0 iplen=44 seq=1654006808 win=29200 <mss 1460> SENT (3.0155s) TCP 172.16.22.18:2734 > 172.16.22.218:3306 S ttl=64 id=56345 iplen=40 seq=1546620167 win=1480 RCVD (3.0157s) TCP 172.16.22.218:3306 > 172.16.22.18:2734 SA ttl=64 id=0 iplen=44 seq=1669652324 win=29200 <mss 1460>
nping -tcp -p 443 google.com -q Starting Nping 0.7.80 ( https://nmap.org/nping ) at 2020-01-13 17:00 +04 Max rtt: 14.615ms | Min rtt: 4.099ms | Avg rtt: 7.753ms Raw packets sent: 5 (200B) | Rcvd: 5 (270B) | Lost: 0 (0.00%) Nping done: 1 IP address pinged in 4.02 seconds
nping -tcp -p 443 google.com -c 0 -c 0 number of probes. Default 5. If 0 run continuously.
Related terms[edit]
See also[edit]
- IP:
route,mtr,traceroute,tcptraceroute,lft, TTL ping,nping,arping,fping, gping,hping,mtr,traceroute,tcptraceroute,tracepath,Test-ConnectionPowershell cmdlet,iperf, Ping (PAN-OS), BWPing,check_ping,ping -M,ios ping, ping -anetperf, iperf, ttcp, nuttcp, BWPing- Security tools: Vulnerability scanner, port scan, Host sweep,
nmap,nping,ncat, nc,psad, Gordon Lyon
Advertising:
