NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

geneousgene's avatar
geneousgene
Aspirant
Sep 26, 2017

Packet loss during ping on same satellite or different satellites

I have two satellites and I see latency problems and lost pings whether the two machines are close together to the satellite or in different places. 

 

My ping looks like this:

 

64 bytes from 192.168.1.10: icmp_seq=17479 ttl=64 time=118.738 ms

64 bytes from 192.168.1.10: icmp_seq=17480 ttl=64 time=22.321 ms

64 bytes from 192.168.1.10: icmp_seq=17481 ttl=64 time=142.668 ms

64 bytes from 192.168.1.10: icmp_seq=17482 ttl=64 time=387.413 ms

64 bytes from 192.168.1.10: icmp_seq=17483 ttl=64 time=178.961 ms

64 bytes from 192.168.1.10: icmp_seq=17484 ttl=64 time=370.118 ms

Request timeout for icmp_seq 17485

64 bytes from 192.168.1.10: icmp_seq=17486 ttl=64 time=41.967 ms

64 bytes from 192.168.1.10: icmp_seq=17487 ttl=64 time=590.077 ms

64 bytes from 192.168.1.10: icmp_seq=17488 ttl=64 time=323.136 ms

64 bytes from 192.168.1.10: icmp_seq=17489 ttl=64 time=325.126 ms

64 bytes from 192.168.1.10: icmp_seq=17490 ttl=64 time=130.102 ms

64 bytes from 192.168.1.10: icmp_seq=17491 ttl=64 time=63.652 ms

64 bytes from 192.168.1.10: icmp_seq=17492 ttl=64 time=7.914 ms

64 bytes from 192.168.1.10: icmp_seq=17493 ttl=64 time=33.584 ms

64 bytes from 192.168.1.10: icmp_seq=17494 ttl=64 time=7.279 ms

64 bytes from 192.168.1.10: icmp_seq=17495 ttl=64 time=551.259 ms

64 bytes from 192.168.1.10: icmp_seq=17496 ttl=64 time=225.913 ms

Request timeout for icmp_seq 17497

64 bytes from 192.168.1.10: icmp_seq=17497 ttl=64 time=1089.848 ms

64 bytes from 192.168.1.10: icmp_seq=17498 ttl=64 time=86.661 ms

64 bytes from 192.168.1.10: icmp_seq=17499 ttl=64 time=135.036 ms

64 bytes from 192.168.1.10: icmp_seq=17500 ttl=64 time=7.765 ms

64 bytes from 192.168.1.10: icmp_seq=17501 ttl=64 time=157.633 ms

64 bytes from 192.168.1.10: icmp_seq=17502 ttl=64 time=376.278 ms

64 bytes from 192.168.1.10: icmp_seq=17503 ttl=64 time=26.287 ms

3 Replies

    • geneousgene's avatar
      geneousgene
      Aspirant

      Just upgraded to V2.0.0.74 and it made things worse. Packet loss still occurs, but I can no longer consistently ping devices connected to a different satellite. 

      • rhester72's avatar
        rhester72
        Virtuoso

        Check the CPU utilization on the debug page on the router - I had a EX6400 wifi extender that went _insane_ with DHCP requests that pretty much DoS'ed my entire wireless network.

         

        Rodney