Troubleshooting using CLI
Executing the Troubleshooting Command
Complete the following steps to execute the troubleshooting commands in the Command Line Interface (CLI).
- Log in to the CLI.
- Enter the troubleshooting commands. Refer to Troubleshooting Commands section.
Troubleshooting Commands
Following are the troubleshooting commands you can execute in the CLI:
help
The help command displays
the overall network help commands available for troubleshooting.
> network-tools help Usage: network-tools [-h] [COMMAND] Network Tools -h, --help display this help Commands: tcpdump dump traffic on a network nslookup query Internet name servers nc nc(ncat) - networking utility traceroute print the route packets trace to network host ping send ICMP ECHO_REQUEST to network hosts dig DNS lookup utility help Displays help information about the specified command
traceroute
The traceroute command
detects the connection status of each node from the local machine to the host.
traceroute -h
The traceroute
-h command displays the overall traceroute help commands
available for troubleshooting.
> network-tools traceroute -h
Usage: network-tools traceroute [-46hInTU] [-m=<maxTtl>] [-p=<port>]
[-w=<waitTime>] <host>
print the route packets trace to network host
<host> the name or IP address of the destination
-4 Use IPv4
-6 Use IPv6
-h, --help display this help
-I, icmp use ICMP echo requests to trace the route (default)
-m=<maxTtl> max_ttl(time-to-live) value
-n, --numeric do not resolve IP addresses to their domain names
-p=<port> specify a destination port for UDP or TCP traceroutes
-T, tcp use TCP packets to trace the route
-U, udp use UDP datagrams to trace the route
-w=<waitTime> wait time
traceroute <host>
The traceroute
<host> command displays the connection status of
each node from the local machine to the host.
Example:
To view the connection status of each node from the local machine to the RND license server (ruckuswireless.flexnetoperations.com):
> network-tools traceroute ruckuswireless.flexnetoperations.com > traceroute to ruckuswireless.flexnetoperations.com (185.146.155.66), 30 hops max, 60 byte packets 1 gateway (192.168.1.1) 0.273 ms 0.237 ms 0.228 ms 2 10.206.79.254 (10.206.79.254) 4.371 ms 7.865 ms 11.321 ms 3 10.7.42.30 (10.7.42.30) 0.988 ms 0.975 ms 0.950 ms 4 210-58-90-1.cm.static.apol.com.tw (210.58.90.1) 3.108 ms 4.803 ms 6.527 ms 5 IL203-79-251-137.static.apol.com.tw (203.79.251.137) 1.459 ms 1.345 ms 1.508 ms 6 211.76.96.191 (211.76.96.191) 2.434 ms 211.76.96.91 (211.76.96.91) 1.606 ms 1.569 ms 7 unknown.telstraglobal.net (210.176.44.13) 3.305 ms 2.870 ms 3.238 ms 8 i-91.ttak-core02.telstraglobal.net (202.84.137.254) 4.195 ms * * 9 * i-15735.siko-core02.telstraglobal.net (202.84.143.5) 32.732 ms * 10 i-10857.eqnx-core02.telstraglobal.net (202.84.141.1) 139.647 ms 139.613 ms 139.604 ms 11 i-92.eqnx03.telstraglobal.net (202.84.247.17) 140.064 ms 139.280 ms 139.873 ms 12 52.95.216.246 (52.95.216.246) 139.087 ms 139.005 ms 138.861 ms 13 15.230.28.65 (15.230.28.65) 140.995 ms 15.230.28.69 (15.230.28.69) 139.016 ms 15.230.28.61 (15.230.28.61) 139.435 ms 14 54.240.242.119 (54.240.242.119) 138.834 ms 54.240.242.81 (54.240.242.81) 140.667 ms 150.222.97.83 (150.222.97.83) 138.378 ms 15 * * * 16 52.93.15.4 (52.93.15.4) 195.588 ms 52.93.12.112 (52.93.12.112) 158.227 ms 52.93.12.222 (52.93.12.222) 262.588 ms 17 52.93.12.109 (52.93.12.109) 159.616 ms 52.93.14.105 (52.93.14.105) 158.394 ms 52.93.12.251 (52.93.12.251) 158.388 ms 18 52.93.14.106 (52.93.14.106) 159.208 ms 52.93.14.140 (52.93.14.140) 158.608 ms 52.93.12.250 (52.93.12.250) 181.837 ms 19 52.93.246.119 (52.93.246.119) 162.535 ms 160.675 ms 52.93.14.95 (52.93.14.95) 158.434 ms 20 205.251.232.167 (205.251.232.167) 158.289 ms 52.93.240.53 (52.93.240.53) 158.710 ms 54.239.48.177 (54.239.48.177) 159.341 ms 21 52.93.240.72 (52.93.240.72) 158.572 ms 52.93.246.74 (52.93.246.74) 163.190 ms 52.93.246.78 (52.93.246.78) 162.861 ms 22 52.93.15.221 (52.93.15.221) 159.754 ms 52.93.246.65 (52.93.246.65) 159.452 ms 52.93.15.221 (52.93.15.221) 159.690 ms
traceroute <ip> | -4 <ipv4> | -6 <ipv6>
The traceroute
<ip>
|
-4 <ipv4>
|
-6 <ipv6> command displays the connection status of
each node from the local machine to the destination IP address.
- ip: This
command displays the connection status of each node from the local machine
to the destination IP address.
Example:
To view the connection status of each node from the local machine to the destination IP address 192.168.1.52:
> network-tools traceroute 192.168.1.52 > traceroute to 192.168.1.52 (192.168.1.52), 30 hops max, 60 byte packets 1 192.168.1.52 (192.168.1.52) 0.236 ms 0.220 ms 0.224 ms
- -4
<ipv4>: This command displays the connection status of
each node from the local machine to the destination IPv4 address.
Example:
To view the connection status of each node from the local machine to the destination IPv4 address 192.168.1.52:
> network-tools traceroute -4 192.168.1.52 > traceroute to 192.168.1.52 (192.168.1.52), 30 hops max, 60 byte packets 1 192.168.1.52 (192.168.1.52) 0.127 ms 0.119 ms 0.101 ms
- -6
<ipv6>: This command displays the connection status of
each node from the local machine to the destination IPv6 address.
Example:
To view the connection status of each node from the local machine to the destination IPv6 address fd55:5555:5555:1::52:
> network-tools traceroute -6 fd55:5555:5555:1::52 > traceroute to fd55:5555:5555:1::52 (fd55:5555:5555:1::52), 30 hops max, 80 byte packets 1 fd55:5555:5555:1::52 (fd55:5555:5555:1::52) 0.199 ms 0.173 ms 0.172 ms
traceroute -I <ipv4 | ipv6 | host>
The traceroute
-I
{
<ipv4>
|
<ipv6>
|
<host>
} command
uses ICMP echo requests to trace the route to the destination IP address.
- ipv4:
This command uses ICMP echo requests to trace route to the destination IPv4
address.
Example:
To trace a route to the destination IPv4 address 192.168.1.52:
> network-tools traceroute -I 192.168.1.52 > traceroute to 192.168.1.52 (192.168.1.52), 30 hops max, 60 byte packets 1 192.168.1.52 (192.168.1.52) 0.131 ms 0.126 ms 0.127 ms
- ipv6:
This command uses ICMP echo requests to trace route to the destination IPv6
address.
Example:
To trace a route to the destination IPv6 address fd55:5555:5555:1::52:
> network-tools traceroute -I fd55:5555:5555:1::52 > traceroute to fd55:5555:5555:1::52 (fd55:5555:5555:1::52), 30 hops max, 80 byte packets 1 fd55:5555:5555:1::52 (fd55:5555:5555:1::52) 0.147 ms 0.141 ms 0.141 ms
- host:
This command uses an ICMP echo request to traces the route to the
destination host.
Example:
To traces the route to the host address ruckuswireless.flexnetoperations.com:
> network-tools traceroute -I ruckuswireless.flexnetoperations.com > traceroute to ruckuswireless.flexnetoperations.com (185.146.155.66), 30 hops max, 60 byte packets 1 gateway (192.168.1.1) 0.240 ms 0.231 ms 0.231 ms 2 10.206.79.254 (10.206.79.254) 4.296 ms * * 3 * * 10.7.42.30 (10.7.42.30) 0.787 ms 4 210-58-90-1.cm.static.apol.com.tw (210.58.90.1) 13.731 ms 10.256 ms 11.974 ms 5 IL203-79-251-137.static.apol.com.tw (203.79.251.137) 1.256 ms 1.308 ms 1.255 ms 6 211.76.96.91 (211.76.96.91) 1.645 ms 1.514 ms 1.493 ms 7 unknown.telstraglobal.net (210.176.44.13) 3.211 ms 3.205 ms 3.197 ms 8 i-91.ttak-core02.telstraglobal.net (202.84.137.254) 2.835 ms 2.831 ms 2.819 ms 9 i-15735.siko-core02.telstraglobal.net (202.84.143.5) 34.030 ms 34.035 ms 34.029 ms 10 i-10857.eqnx-core02.telstraglobal.net (202.84.141.1) 139.319 ms 139.277 ms 139.278 ms 11 i-92.eqnx03.telstraglobal.net (202.84.247.17) 138.976 ms 138.817 ms 139.001 ms 12 52.95.216.246 (52.95.216.246) 138.381 ms 138.879 ms 139.764 ms 13 15.230.28.63 (15.230.28.63) 139.418 ms 139.345 ms 139.363 ms 14 54.240.242.81 (54.240.242.81) 139.302 ms 139.169 ms 139.156 ms 15 * * * 16 52.93.12.44 (52.93.12.44) 158.587 ms 158.477 ms 159.120 ms 17 52.93.12.37 (52.93.12.37) 158.700 ms 158.698 ms 158.695 ms 18 52.93.12.180 (52.93.12.180) 165.010 ms 164.975 ms 164.986 ms 19 52.93.12.209 (52.93.12.209) 162.448 ms 160.828 ms 160.493 ms 20 52.93.240.61 (52.93.240.61) 159.218 ms 159.211 ms 159.206 ms 21 52.93.246.26 (52.93.246.26) 160.372 ms 160.346 ms 160.310 ms 22 52.93.246.17 (52.93.246.17) 159.499 ms 159.282 ms 159.144 ms
traceroute -4|-6 <ipv4 | ipv6 | host> -m <value>
The traceroute
-4
|
-6
{
<ipv4>
|
<ipv6>
|
host
-m
value
} command
uses ICMP echo requests to trace the route to the destination IP address for the
maximum time-to-live value.
- ipv4:
This command uses ICMP echo requests to trace the route to the destination
IPv4 address for the maximum time-to-live value.
Example:
To view the connection status to the destination IPv4 address 192.168.1.52 for the maximum time-to-live value of 10:
> network-tools traceroute -4 192.168.1.52 -m 10 > traceroute to 192.168.1.52 (192.168.1.52), 10 hops max, 60 byte packets 1 192.168.1.52 (192.168.1.52) 0.157 ms 0.104 ms 0.081 ms
- ipv6:
This command uses ICMP echo requests to trace the route to the destination
IPv6 address for the maximum time-to-live value.
Example:
To traces the route to the destination IPv6 address fd55:5555:5555:1::52 for the maximum time-to-live value of 10:
> network-tools traceroute -6 fd55:5555:5555:1::52 -m 10 > traceroute to fd55:5555:5555:1::52 (fd55:5555:5555:1::52), 10 hops max, 80 byte packets 1 fd55:5555:5555:1::52 (fd55:5555:5555:1::52) 0.127 ms 0.109 ms 0.099 ms
traceroute -4|-6 <ipv4 | ipv6 | host> -n | --numeric
The traceroute
-4
|
-6
{
<ipv4>
|
<ipv6>
|
host
-n
|
--numeric
} command
trace the route to the destination IP address without resolving the IP address to
their domain name.
- ipv4:
This command trace the route to the destination IPv4 address without
resolving the IP address to their domain name.
Example:
To trace the route to the destination IPv4 address 192.168.1.52 without resolving the IP address to their domain name:
> network-tools traceroute -4 192.168.1.52 -n > traceroute to 192.168.1.52 (192.168.1.52), 30 hops max, 60 byte packets 1 192.168.1.52 0.132 ms 0.116 ms 0.106 ms
- ipv6:
This command trace the route to the destination IPv6 address without
resolving the IP address to their domain name.
Example:
To trace the route to the destination IPv6 address fd55:5555:5555:1::52 without resolving the IP address to their domain name:
network-tools traceroute -6 fd55:5555:5555:1::52 -n > traceroute to fd55:5555:5555:1::52 (fd55:5555:5555:1::52), 30 hops max, 80 byte packets 1 fd55:5555:5555:1::52 0.164 ms 0.161 ms 0.153 ms
tcpdump
The tcpdump command
displays the packets on a network interface.
tcpdump -h
The tcpdump
-h
|
--help command displays the overall tcpdump help commands
available for troubleshooting.
> network-tools tcpdump -h
Usage: network-tools tcpdump [-hnq] [icmp] [-nn] [tcp] [udp] [-c=<count>]
[dst=<destination>] [host=<host>] [-i=interface]
[port=<port>] [src=<source>]
dump traffic on a network
-c=<count> capture a specific number of packets and then exit
dst=<destination> capture packets with a specific destination IP address
-h, --help display this help
host=<host> capture packets to or from a specific host
-i=interface specify the network interface to capture packets
from. For example, -i eth0
icmp capture only ICMP packets
-n display numeric IP addresses instead of resolving
hostnames
-nn display numeric IP addresses and port numbers without
resolving them
port=<port> capture packets for a specific port number, e.g.,
port 80
-q print less protocol information for a more concise
output
src=<source> capture packets with a specific source IP address
tcp capture only TCP packets
udp capture only UDP packets
>
tcpdump -c <value>
The tcpdump
-c
{
<value>
} command
displays the number of packets mentioned in the value on a network interface.
Example:
To view the latest 10 packets on a network interface:
> network-tools tcpdump -c 10 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes 07:53:53.976996 IP node0.ssh > 192.168.1.230.50642: Flags [P.], seq 1438326772:1438326980, ack 2591271288, win 336, options [nop,nop,TS val 17079004 ecr 1463784910], length 208 10 packets captured 20 packets received by filter 0 packets dropped by kernel 07:53:53.977084 IP 192.168.1.230.50642 > node0.ssh: Flags [.], ack 208, win 501, options [nop,nop,TS val 1463785043 ecr 17079004], length 0 07:53:54.620035 ARP, Request who-has gateway (Broadcast) tell 192.168.1.120, length 46 07:53:54.937182 ARP, Request who-has 192.168.1.240 tell 192.168.1.163, length 46 07:53:54.965322 IP node0.44195 > dns.google.domain: 47195+ PTR? 230.1.168.192.in-addr.arpa. (44) 07:53:54.967183 IP dns.google.domain > node0.44195: 47195 NXDomain 0/0/0 (44) 07:53:54.967989 IP node0.44977 > dns.google.domain: 4292+ PTR? 100.1.168.192.in-addr.arpa. (44) 07:53:54.969738 IP dns.google.domain > node0.44977: 4292 NXDomain 0/0/0 (44) 07:53:54.969885 IP node0.48173 > dns.google.domain: 22084+ PTR? 1.1.168.192.in-addr.arpa. (42) 07:53:54.971618 IP dns.google.domain > node0.48173: 22084 NXDomain 0/0/0 (42)
tcpdump -i <network interface>
The tcpdump
-i
{
network interface
} command displays the packets on the specified network
interface.
Example:
To view the packets on eth0 network interface:
> network-tools tcpdump -i eth0 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes 07:54:40.537567 IP node0.ssh > 192.168.1.230.50642: Flags [P.], seq 1438329748:1438329956, ack 2591272696, win 336, options [nop,nop,TS val 17125564 ecr 1463831565], length 208 07:54:40.537670 IP 192.168.1.230.50642 > node0.ssh: Flags [.], ack 208, win 501, options [nop,nop,TS val 1463831603 ecr 17125564], length 0 07:54:40.813393 ARP, Request who-has gateway (Broadcast) tell 192.168.1.120, length 46 07:54:40.952236 ARP, Request who-has 192.168.1.240 tell 192.168.1.163, length 46 07:54:41.167845 IP6 fe80::20c:29ff:fe79:9aef > ff02::1: ICMP6, router advertisement, length 56 07:54:41.529422 IP node0.41606 > dns.google.domain: 45206+ PTR? 230.1.168.192.in-addr.arpa. (44) 07:54:41.531289 IP dns.google.domain > node0.41606: 45206 NXDomain 0/0/0 (44) 07:54:41.532173 IP node0.46007 > dns.google.domain: 47241+ PTR? 100.1.168.192.in-addr.arpa. (44) 07:54:41.533776 IP dns.google.domain > node0.46007: 47241 NXDomain 0/0/0 (44) 07:54:41.533914 IP node0.49218 > dns.google.domain: 40619+ PTR? 1.1.168.192.in-addr.arpa. (42) 10 packets captured 32 packets received by filter 0 packets dropped by kernel
tcpdump -n
The tcpdump
-n command displays the packets on the IP
addresses.
> network-tools tcpdump -n > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes 10 packets captured 11 packets received by filter 0 packets dropped by kernel 07:55:20.608891 IP 192.168.1.100.ssh > 192.168.1.230.50642: Flags [P.], seq 1438332036:1438332244, ack 2591273464, win 336, options [nop,nop,TS val 17165635 ecr 1463871571], length 208 07:55:20.609012 IP 192.168.1.230.50642 > 192.168.1.100.ssh: Flags [.], ack 208, win 501, options [nop,nop,TS val 1463871675 ecr 17165635], length 0 07:55:20.762433 ARP, Request who-has 192.168.1.1 tell 192.168.1.193, length 46 07:55:20.966172 ARP, Request who-has 192.168.1.240 tell 192.168.1.163, length 46 07:55:20.980800 ARP, Request who-has 192.168.1.1 (Broadcast) tell 192.168.1.120, length 46 07:55:21.786409 ARP, Request who-has 192.168.1.1 tell 192.168.1.193, length 46 07:55:21.966166 ARP, Request who-has 192.168.1.240 tell 192.168.1.163, length 46 07:55:21.985193 ARP, Request who-has 192.168.1.1 (Broadcast) tell 192.168.1.120, length 46 07:55:22.810472 ARP, Request who-has 192.168.1.1 tell 192.168.1.193, length 46 07:55:22.966182 ARP, Request who-has 192.168.1.240 tell 192.168.1.163, length 46
tcpdump -nn
The tcpdump
-nn command displays the packets on the IP
addresses and port numbers.
> network-tools tcpdump -nn > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes 07:58:23.648882 IP 192.168.1.100.22 > 192.168.1.230.50642: Flags [P.], seq 1438333780:1438333988, ack 2591273720, win 336, options [nop,nop,TS val 17348675 ecr 1464054608], length 208 10 packets captured 50 packets received by filter 0 packets dropped by kernel 07:58:23.648972 IP 192.168.1.230.50642 > 192.168.1.100.22: Flags [.], ack 208, win 501, options [nop,nop,TS val 1464054715 ecr 17348675], length 0 07:58:23.786428 ARP, Request who-has 192.168.1.1 (ff:ff:ff:ff:ff:ff) tell 192.168.1.120, length 46 07:58:24.523335 ARP, Request who-has 192.168.1.240 tell 192.168.1.163, length 46 07:58:24.787929 ARP, Request who-has 192.168.1.1 (ff:ff:ff:ff:ff:ff) tell 192.168.1.120, length 46 07:58:25.161238 IP 192.168.1.230.62782 > 192.168.1.100.8443: Flags [S], seq 351965605, win 64240, options [mss 1460,sackOK,TS val 1464056227 ecr 0,nop,wscale 7], length 0 07:58:25.161260 IP 192.168.1.100.8443 > 192.168.1.230.62782: Flags [S.], seq 3078652237, ack 351965606, win 28960, options [mss 1460,sackOK,TS val 17350188 ecr 1464056227,nop,wscale 7], length 0 07:58:25.161317 IP 192.168.1.230.62782 > 192.168.1.100.8443: Flags [.], ack 1, win 502, options [nop,nop,TS val 1464056227 ecr 17350188], length 0 07:58:25.162653 IP 192.168.1.230.62782 > 192.168.1.100.8443: Flags [P.], seq 1:547, ack 1, win 502, options [nop,nop,TS val 1464056228 ecr 17350188], length 546 07:58:25.162662 IP 192.168.1.100.8443 > 192.168.1.230.62782: Flags [.], ack 547, win 235, options [nop,nop,TS val 17350189 ecr 1464056228], length 0
tcpdump -q
The tcpdump
-q command displays print-less protocol
information to show shorter output lines.
> network-tools tcpdump -q > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes 07:59:23.022710 IP node0.ssh > 192.168.1.230.50642: tcp 208 10 packets captured 07:59:23.022784 IP 192.168.1.230.50642 > node0.ssh: tcp 0 20 packets received by filter 0 packets dropped by kernel 07:59:23.642138 ARP, Request who-has 192.168.1.240 tell 192.168.1.163, length 46 07:59:24.000860 ARP, Request who-has gateway (Broadcast) tell 192.168.1.120, length 46 07:59:24.013314 IP node0.45575 > dns.google.domain: UDP, length 44 07:59:24.015151 IP dns.google.domain > node0.45575: UDP, length 44 07:59:24.015862 IP node0.34105 > dns.google.domain: UDP, length 44 07:59:24.017542 IP dns.google.domain > node0.34105: UDP, length 44 07:59:24.017651 IP node0.38797 > dns.google.domain: UDP, length 44 07:59:24.019702 IP dns.google.domain > node0.38797: UDP, length 44
nslookup
The nslookup command
queries DNS records for the host.
nslookup -h
The nslookup
-h
command displays the overall nslookup help commands available for
troubleshooting.
> network-tools nslookup -h
Usage: network-tools nslookup [-h] <domainName>
query Internet name servers
<domainName> domain name
nslookup <host>
The nslookup
<host>
command queries DNS records for the host.
Example:
To view the DNS query for the RND license server (ruckuswireless.flexnetoperations.com):
> network-tools nslookup ruckuswireless.flexnetoperations.com Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: ruckuswireless.flexnetoperations.com canonical name = api-prod.flexnetoperations.com. api-prod.flexnetoperations.com canonical name = front-nlb-prod-us-west-2-0-b532f90042a6cf90.elb.us-west-2.amazonaws.com. Name: front-nlb-prod-us-west-2-0-b532f90042a6cf90.elb.us-west-2.amazonaws.com Address: 185.146.155.64 Name: front-nlb-prod-us-west-2-0-b532f90042a6cf90.elb.us-west-2.amazonaws.com Address: 185.146.155.65 Name: front-nlb-prod-us-west-2-0-b532f90042a6cf90.elb.us-west-2.amazonaws.com Address: 185.146.155.66 Name: front-nlb-prod-us-west-2-0-b532f90042a6cf90.elb.us-west-2.amazonaws.com Address: 2620:122:f003:202:247c:97f5:8b35:e658 Name: front-nlb-prod-us-west-2-0-b532f90042a6cf90.elb.us-west-2.amazonaws.com Address: 2620:122:f003:200:93a6:5a52:984a:498f Name: front-nlb-prod-us-west-2-0-b532f90042a6cf90.elb.us-west-2.amazonaws.com Address: 2620:122:f003:201:ebd4:96c8:5c31:bf19
dig
The dig command queries
DNS-related information for the host.
dig -h
The dig
-h
command displays the overall dig help commands available for
troubleshooting.
> network-tools dig -h
Usage: network-tools dig [-h] [<name>...]
DNS lookup utility
[<name>...] the resource record that is to be looked up
dig <domain name>
The dig
<domain name>
command queries DNS-related information for the domain name.
Example:
To query DNS-related information for the RND license server (ruckuswireless.flexnetoperations.com):
> network-tools dig rukuswireless.flexnetoperations.com ; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.15 <<>> rukuswireless.flexnetoperations.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28388 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;rukuswireless.flexnetoperations.com. IN A ;; AUTHORITY SECTION: flexnetoperations.com. 1800 IN SOA pdns1.ultradns.net. it-dns.flexerasoftware.com. 2012140769 10800 3600 2592000 86400 ;; Query time: 49 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Thu Nov 23 08:16:37 UTC 2023 ;; MSG SIZE rcvd: 141 >
nc (ncat)
The nc (ncat) command
checks if the service port on the host is open.
nc -h
The nc
-h
command displays the overall nc help commands available for
troubleshooting.
> network-tools nc -h
Usage: network-tools nc [-hvz] <host> <port>
nc(ncat) - networking utility
<host> hostname or IP address
<port> port
-h, --help display this help
-v set verbosity level
-z zero-I/O mode, report connection status only
>
nc <host> <port>
The dig
<host>
<port>
command checks if the service port on the host is open.
Example:
To query if port 443 on the RND license server (ruckuswireless.flexnetoperations.com) is open:
> network-tools nc ruckuswireless.flexnetoperations.com 443 > Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connected to 185.146.155.66:443. Ncat: 0 bytes sent, 0 bytes received in 0.21 seconds.
ping
The ping command sends an
ICMP echo request to the Google DNS server.
ping -h
The ping
-h
command displays the overall ping help commands available for
troubleshooting.
> network-tools ping -h
Usage: network-tools ping [-6h] [-c=<count>] [-i=<interval>] [-s=<packetSize>]
[-W=<waitTime>] <destination>
send ICMP ECHO_REQUEST to network hosts
<destination> host name or IP address
-6 Use IPv6
-c=<count> specify the number of ICMP Echo Request packets to send
-h, --help display this help
-i=<interval> set the time interval in seconds between sending each
packet
-s=<packetSize> the size of the packets being sent
-W=<waitTime> time to wait for a response, in seconds
>
ping <ip>
The ping
<ip>
|
-6 <ipv6>
command sends an ICMP echo request for the IP address to the Google DNS
server.
- ip: This
command sends an ICMP echo request for the IP address to the Google DNS
server.
Example:
To sends an ICMP echo request for the IP address 192.168.1.52 to the Google DNS server:
> network-tools ping 192.168.1.52 > PING 192.168.1.52 (192.168.1.52) 56(84) bytes of data. 64 bytes from 192.168.1.52: icmp_seq=1 ttl=64 time=0.105 ms 64 bytes from 192.168.1.52: icmp_seq=2 ttl=64 time=0.156 ms 64 bytes from 192.168.1.52: icmp_seq=3 ttl=64 time=0.105 ms 64 bytes from 192.168.1.52: icmp_seq=4 ttl=64 time=0.095 ms 64 bytes from 192.168.1.52: icmp_seq=5 ttl=64 time=0.123 ms --- 192.168.1.52 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3999ms rtt min/avg/max/mdev = 0.095/0.116/0.156/0.025 ms
- -6
<ipv6>: This command sends an ICMP echo request for the
IPv6 address to the Google DNS server.
Example:
To sends an ICMP echo request for the IPv6 address fd55:5555:5555:1::52 to the Google DNS server:
> network-tools ping -6 fd55:5555:5555:1::52 > PING fd55:5555:5555:1::52(fd55:5555:5555:1::52) 56 data bytes 64 bytes from fd55:5555:5555:1::52: icmp_seq=1 ttl=64 time=0.101 ms 64 bytes from fd55:5555:5555:1::52: icmp_seq=2 ttl=64 time=0.112 ms 64 bytes from fd55:5555:5555:1::52: icmp_seq=3 ttl=64 time=0.142 ms 64 bytes from fd55:5555:5555:1::52: icmp_seq=4 ttl=64 time=0.116 ms 64 bytes from fd55:5555:5555:1::52: icmp_seq=5 ttl=64 time=0.126 ms --- fd55:5555:5555:1::52 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3999ms rtt min/avg/max/mdev = 0.101/0.119/0.142/0.016 ms