Difference between revisions of "Check TCP connectivity"
Jump to navigation
Jump to search
↑ https://nmap.org/
Tags: Mobile web edit, Mobile edit |
(revert) |
||
| Line 1: | Line 1: | ||
| − | |||
| + | == Using: [[nping]] == | ||
| + | Install [[nmap]]<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: | ||
| − | + | <pre> | |
| + | 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> | ||
| + | </pre> | ||
| − | + | == Using [[nagios]]: check_tcp == | |
| − | + | <code>/usr/lib/nagios/plugins/check_tcp -H 127.0.0.1 -p 80</code> | |
| − | + | ||
| − | + | == See also == | |
| − | + | * {{TCP}} | |
| − | + | * {{ping}} | |
| − | + | * {{ethernet}} | |
| − | + | ||
| − | + | ||
| + | [[Category:Networking]] | ||
| + | [[Category:Ping]] | ||
| + | [[Category:Activities]] | ||
| + | [[Category:Internet Protocol Analysis]] | ||
Revision as of 08:53, 17 January 2024
Using: nping
Install nmap[1] tool, available at least for Windows, Mac and Linux and executenping --tcp -p 3306 172.16.22.218 to test tcp connectivity for port 3306 in host 172.16.22.218:
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>
Using nagios: check_tcp
/usr/lib/nagios/plugins/check_tcp -H 127.0.0.1 -p 80
See also
- TCP/IP, Transport protocol, UDP, SCTP, QUIC, subnet mask, Routing protocols: BGP, routing table, Policy based routing, multicast, TCP Fast Open, RDP, TTL, RTT, MPTCP, Large send offload (LSO): (TSO, GRO, GSO, TCP checksum),
ethtool, SCTP, 5-Tuple, Check TCP connectivity, TCP window size,/proc/sys/net/ipv4/tcp_rmem, ack, List of TCP ports, localhost, broadcast address 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 -a- Ethernet: MII, MDI, bonding, etherchannel, STP, ARP, MAC, STP, Jumbo frames, 802.1X, MTU, Ethernet In-Band Access (IBA), LACP, Multicast, Broadcast, SPI
Advertising:
