Ping Cheat Sheet

    Input:  ping google.com
    Output: PING google.com (142.250.69.110) 56(84) bytes of data.
            64 bytes from mia07s58-in-f14.1e100.net (142.250.69.110): icmp_seq=1 ttl=116 time=15.2 ms
            64 bytes from mia07s58-in-f14.1e100.net (142.250.69.110): icmp_seq=2 ttl=116 time=15.4 ms
            

    Input:  ping 8.8.8.8
    Output: PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
            64 bytes from 8.8.8.8: icmp_seq=1 ttl=117 time=12.3 ms
            64 bytes from 8.8.8.8: icmp_seq=2 ttl=117 time=12.1 ms
            

    Input:  ping -c 4 example.com
    Output: PING example.com (93.184.216.34) 56(84) bytes of data.
            64 bytes from 93.184.216.34: icmp_seq=1 ttl=56 time=120.1 ms
            64 bytes from 93.184.216.34: icmp_seq=2 ttl=56 time=119.6 ms
            64 bytes from 93.184.216.34: icmp_seq=3 ttl=56 time=120.3 ms
            64 bytes from 93.184.216.34: icmp_seq=4 ttl=56 time=119.8 ms
            
            --- example.com ping statistics ---
            4 packets transmitted, 4 received, 0% packet loss, time 3005ms
            rtt min/avg/max/mdev = 119.590/119.946/120.311/0.287 ms
            

    Input:  [Press Ctrl+C while ping is running]
    Effect: Stops ping and shows summary statistics
            

    Input:  ping -c 5 -i 2 -s 1000 google.com
    Effect: Sends 5 ping packets of 1000 bytes each with 2-second intervals to google.com
            

    Input:  man ping
    Effect: Displays the manual with all available ping options and their descriptions
            

    Input:  ping --help
    Effect: Shows a summary of ping command options
            

    Input:  ping -c 6 cloudflare.com
    Effect: Sends exactly 6 ping packets and then stops
            

    Input:  ping -n 6 cloudflare.com
    Effect: Sends exactly 6 ping packets and then stops (Windows command)
            

    Input:  ping github.com
    Effect: Continuously pings github.com until manually stopped
            

    Input:  ping -i 5 example.com
    Effect: Sends a ping packet every 5 seconds instead of the default 1 second
            

    Input:  sudo ping -i 0.2 192.168.1.1
    Effect: Sends 5 ping packets per second (privileged users only)
            

    Input:  ping -i 10 -c 6 google.com
    Effect: Sends 6 ping packets with 10-second intervals between each
            

    Input:  ping -W 2 slowserver.example.com
    Effect: Waits up to 2 seconds for each reply before timing out
            

    Input:  ping -w 2000 example.com
    Effect: Waits up to 2000 milliseconds for each reply (macOS)
            

    Input:  ping -W 1 -c 10 192.168.1.100
    Effect: Sends 10 packets with a 1-second timeout for each response
            

    Input:  ping -w 10 example.com
    Effect: Runs ping for 10 seconds total, then exits regardless of packet count
            

    Input:  ping -t 15 example.com
    Effect: Stops ping after 15 seconds total execution time
            

    Input:  timeout 30 ping google.com
    Effect: Runs ping for up to 30 seconds then terminates it
            

    Input:  ping -s 1000 google.com
    Effect: Sends ping packets with 1000 bytes of data (plus 8 byte ICMP header)
            

    Input:  ping -s 1472 192.168.1.1
    Effect: Tests if the path can handle maximum sized packets (1500 byte MTU)
            

    Input:  ping -s 2000 -c 5 example.com
    Effect: Sends 5 large packets (2000 bytes each) to test network capacity
            

    Input:  sudo ping -f 192.168.1.1
    Effect: Sends many packets per second with minimal output (just dots/backspaces)
            

    Input:  sudo ping -f -c 100 192.168.1.1
    Effect: Sends 100 packets in rapid succession and stops
            

    Input:  sudo ping -f -i 0.1 192.168.1.1
    Effect: Sends packets with 0.1 second intervals (10 per second)
            

    Input:  ping -a 8.8.8.8
    Effect: Beeps on each successful ping response (useful for audio monitoring)
            

    Input:  ping -a -i 2 example.com
    Effect: Beeps every 2 seconds when responses are received
            

    Input:  ping -a -O google.com
    Effect: Beeps on responses and shows outstanding packets
            

    Input:  ping -t 5 google.com
    Effect: Packets expire after passing through 5 routers
            

    Input:  ping -m 10 example.com
    Effect: Sets the TTL to 10 hops (macOS syntax)
            

    Input:  ping -i 64 8.8.8.8
    Effect: Sets the TTL to 64 hops (Windows syntax)
            

    Input:  ping -t 1 example.com
    Effect: Shows the first hop (router) in the path to the destination
            

    Input:  ping -I eth0 8.8.8.8
    Effect: Sends ping packets from the eth0 interface
            

    Input:  ping -I 192.168.1.5 example.com
    Effect: Uses 192.168.1.5 as the source IP address for the ping
            

    Input:  ping -S 10.0.0.5 8.8.8.8
    Effect: Sets 10.0.0.5 as the source IP (macOS syntax)
            

    Input:  ping -4 google.com
    Effect: Only uses IPv4 to connect to the target
            

    Input:  ping -6 google.com
    Effect: Only uses IPv6 to connect to the target
            

    Input:  ping6 ipv6.google.com
    Effect: Sends IPv6 ping packets to the target
            

    Input:  ping -R example.com
    Effect: Records and displays the route that packets take to reach the destination
            

    Input:  ping -R -c 1 8.8.8.8
    Effect: Shows the route for a single ping packet
            

    Input:  traceroute google.com
    Effect: Shows the complete route to the destination
            

    Input:  ping -D google.com
    Output: [1621789234.567890] 64 bytes from 142.250.69.110: icmp_seq=1 ttl=116 time=15.2 ms
            [1621789235.569012] 64 bytes from 142.250.69.110: icmp_seq=2 ttl=116 time=15.4 ms
            

    Input:  ping -T tsonly google.com
    Effect: Shows only timestamp information for each packet
            

    Input:  ping -T tsandaddr 8.8.8.8
    Effect: Shows timestamps and addresses for each router along the path
            

    Input:  ping -q -c 10 google.com
    Output: PING google.com (142.250.69.110) 56(84) bytes of data.
            
            --- google.com ping statistics ---
            10 packets transmitted, 10 received, 0% packet loss, time 9013ms
            rtt min/avg/max/mdev = 14.807/15.122/15.665/0.282 ms
            

    Input:  ping -q -c 5 8.8.8.8
    Effect: Silently sends 5 packets and only shows the final statistics
            

    Input:  ping -q -w 10 example.com
    Effect: Quietly pings for 10 seconds and then shows summary statistics
            

    Input:  ping -i 3 example.com
    Effect: Sends ping packets every 3 seconds instead of the default 1 second
            

    Input:  sudo ping --flood --preload=50 192.168.1.1
    Effect: Sends 50 packets immediately, then continues in flood mode
            

    Input:  ping --adaptive google.com
    Effect: Automatically adjusts ping interval based on response times
            

    Input:  ping -p ff 8.8.8.8
    Effect: Fills the ping packet with 0xFF bytes (all bits set)
            

    Input:  ping -p deadbeef google.com
    Effect: Fills the packet with the hex pattern 0xDEADBEEF
            

    Input:  ping -p ff -s 1000 example.com
    Effect: Sends 1000-byte packets filled with 0xFF bytes
            

    Input:  ping -M do -s 1500 example.com
    Effect: Sends 1500-byte packets with DF flag set (to test MTU)
            

    Input:  ping -M do -s 1472 8.8.8.8
    Effect: Tests if large packets can traverse the path without fragmentation
            

    Input:  ping -M dont -s 1500 192.168.1.1
    Effect: Prohibits fragmentation for testing maximum packet sizes
            

    Input:  sudo ping -f 8.8.8.8
    Effect: Allows use of flood mode which requires root privileges
            

    Input:  sudo ping -i 0.2 example.com
    Effect: Sends 5 pings per second (needs root privileges)
            

    Input:  sudo sysctl -w net.ipv4.ping_group_range="0 0"
    Effect: Enables all users to use ping without requiring sudo
            

    Output: 64 bytes from 8.8.8.8: icmp_seq=1 ttl=117 time=14.5 ms
    Meaning: This is the first packet in the sequence
            

    Output: 64 bytes from 8.8.8.8: icmp_seq=2 ttl=117 time=15.0 ms
    Meaning: The packet had a TTL of 117 when it arrived
            

    Output: 64 bytes from 8.8.8.8: icmp_seq=3 ttl=117 time=14.8 ms
    Meaning: It took 14.8 milliseconds for the packet to reach the destination and return
            

    Output: 5 packets transmitted, 5 received, 0% packet loss, time 4006ms
    Meaning: 5 ping packets were sent from your system
            

    Output: 5 packets transmitted, 5 received, 0% packet loss, time 4006ms
    Meaning: All 5 packets sent were received back
            

    Output: 5 packets transmitted, 4 received, 20% packet loss, time 4006ms
    Meaning: 1 out of 5 packets (20%) was lost in transit
            

    Output: rtt min/avg/max/mdev = 14.776/15.015/15.137/0.193 ms
    Meaning: Minimum RTT: 14.776ms, Average: 15.015ms, Maximum: 15.137ms, Mean deviation: 0.193ms
            

    Output: From 192.168.1.1 icmp_seq=1 Destination Host Unreachable
    Solution: Check if the target host is powered on and connected to the network
            

    Output: Request timed out.
    Solution: Check connectivity, firewall settings, or try increasing timeout
            

    Output: ping: unknown host example.invalid
    Solution: Verify hostname is correct, check DNS settings
            

    Output: ping: socket: Operation not permitted
    Solution: Run with sudo/administrator privileges or adjust system settings
            

    Output: From 192.168.1.1 icmp_seq=1 Packet filtered
    Solution: Check firewall settings on both source and destination
            

    Output: ping: connect: Network is unreachable
    Solution: Check if gateway is configured, VPN is connected, or network interface is up
            

    Input:  for i in {1..254}; do ping -c 1 -W 1 192.168.1.$i | grep "64 bytes"; done
    Effect: Pings all IPs in 192.168.1.0/24 subnet and shows only successful responses
            

    Input:  nmap -sn 192.168.1.0/24
    Effect: Performs ping sweep of entire subnet and shows hosts that are up
            

    Input:  fping -g 192.168.1.1 192.168.1.254
    Effect: Pings all addresses in the range and reports status
            

    Input:  traceroute google.com
    Effect: Shows all routers in the path to google.com
            

    Input:  mtr 8.8.8.8
    Effect: Shows a real-time, continuously updated traceroute with ping statistics
            

    Input:  fping google.com yahoo.com example.com
    Effect: Pings multiple hosts in parallel and reports results
            

    Input:  arping -I eth0 192.168.1.1
    Effect: Sends ARP requests rather than ICMP echo requests
            

    Input:  hping3 -S -p 80 example.com
    Effect: Send TCP SYN packets to port 80 instead of ICMP
            

    Input:  nmap -sP 192.168.1.0/24
    Effect: Scans the entire subnet to discover active hosts
            

    Command: ping 8.8.8.8
    Success: Internet connectivity is working at ICMP level
    Failure: Network connection, router, or ISP issue
            

    Command: ping google.com
    Success: Both DNS resolution and internet connectivity work
    Failure: If 8.8.8.8 works but domain doesn't, indicates DNS issue
            

    Command: ping default gateway
    Success: Local network connectivity is working
    Failure: Network adapter or local network issue
            

    Command: ping -c 100 server.example.com
    Result: 5% packet loss
    Meaning: Network has quality issues - congestion or hardware problems
            

    Command: ping cloud-server.example.com
    Result: time=150ms with high variation
    Meaning: High latency with jitter - might affect real-time applications
            

    Command: ping -M do -s 1472 example.com
    Failure: "Message too long"
    Meaning: Path MTU is smaller than 1500 bytes, indicating a potential MTU issue
            

    Issue: Host may be up but not responding to ping
    Note: Lack of ping response doesn't mean a service is down
    Alternative: Try connecting to specific service ports (e.g., HTTP/80)
            

    Risk: Ping flood can consume bandwidth or server resources
    Mitigation: Configure rate limiting for ICMP on network equipment
    Example: iptables -A INPUT -p icmp -m limit --limit 1/s --limit-burst 1 -j ACCEPT
            

    Risk: Attackers use ping to map networks before attacks
    Mitigation: Consider selective ICMP filtering at your network edge
    Best practice: Block external pings to internal hosts, but allow internal ping
            

    Issue: Running ping often requires root/administrator privileges
    Solution: Modern Linux systems allow unprivileged ping via capabilities
    Configuration: sysctl -w net.ipv4.ping_group_range="0 0"
            

    Features: Flood ping, timestamp, pattern filling, preload
    Example: ping -f -c 100 -i 0.01 192.168.1.1
    Version check: ping -V
            

    Features: Some options vary from Linux (e.g., -i for interval)
    Example: ping -c 5 -i 2 -s 1000 example.com
    Note: Use man ping to check options specific to your system
            

    Features: Basic functionality with fewer options
    Example: ping -n 4 -l 1000 -w 5000 example.com
    Note: -n (count), -l (size), -w (timeout in ms)
            

    Features: Limited options optimized for size
    Example: ping -c 4 192.168.1.1
    Common in: Routers, IoT devices, minimal Linux distributions
            

    Bash script:
    if ping -c 1 -W 1 8.8.8.8 > /dev/null; then
        echo "Network is up"
    else
        echo "Network is down"
    fi
            

    Bash script:
    while true; do
        date >> ping_log.txt
        ping -c 10 example.com | grep -A 2 "ping statistics" >> ping_log.txt
        sleep 60
    done
            

    Bash/awk:
    # Extract average ping time
    avg_ping=$(ping -c 4 google.com | grep 'avg' | awk -F'/' '{print $5}')
    echo "Average ping: $avg_ping ms"
            

    Bash script:
    hosts=("google.com" "cloudflare.com" "example.com")
    for host in "${hosts[@]}"; do
        if ping -c 1 -W 2 $host > /dev/null; then
            echo "$host is up"
        else
            echo "$host is down"
        fi
    done
            

    Bash script:
    while true; do
        if ! ping -c 3 8.8.8.8 > /dev/null; then
            echo "Alert: Internet connection down!" | mail -s "Network Alert" admin@example.com
        fi
        sleep 300
    done
            

    Count:   ping -c 5 example.com
    Interval: ping -i 2 example.com
    Timeout:  ping -W 2 example.com
    Size:     ping -s 1000 example.com
            

    Count:   ping -c 5 example.com
    Interval: ping -i 2 example.com
    Timeout:  ping -W 2000 example.com (milliseconds)
    TTL:      ping -t 64 example.com
            

    Count:   ping -n 5 example.com
    Timeout:  ping -w 2000 example.com
    Size:     ping -l 1000 example.com
    TTL:      ping -i 64 example.com
            

    Basic:    ping 192.168.1.1
    Count:    ping 192.168.1.1 repeat 5
    Size:     ping 192.168.1.1 size 1000
    Extended: ping ip 192.168.1.1 df-bit size 1500 timeout 2
            

    Basic:   ping google.com
    Count:   ping -c 5 google.com
    Note: Requires terminal app or ADB access
            

    Method: Use network utility apps from App Store
    Note: Native ping command not accessible to users