Quantcast
Channel: CenturyLink forum - dslreports.com
Viewing all articles
Browse latest Browse all 4880

Pinging Router

$
0
0
Internet has took a dive a week or so ago. How many ms should it take to ping my router? 192.168.0.1 This is when I ping it from Terminal on my Mac. Would these numbers when pinging just the router mean the router is bad? Because pinging the router is just checking the connection between computer and router? Roberts-MacBook-Pro:~ robertehrlish$ ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1): 56 data bytes 64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=2.048 ms 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2.312 ms 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=2.251 ms 64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=2.360 ms 64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=2.645 ms 64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=2.594 ms 64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=67.312 ms 64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=87.044 ms 64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=112.694 ms 64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=2.513 ms 64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=42.245 ms 64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=22.392 ms 64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=2.427 ms 64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=1.316 ms 64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=31.001 ms 64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=2.234 ms ^C --- 192.168.0.1 ping statistics --- 16 packets transmitted, 16 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 1.316/24.087/112.694/34.301 ms

Viewing all articles
Browse latest Browse all 4880

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>