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

Forum Discussion

j0ebeer's avatar
j0ebeer
Guide
Jan 14, 2020

Orbi excessive pinging

Does anyone else see their Orbi satellites doing excessing pings to the default gateway?  In my firewall log I am getting thousand of them and I don't know why.  Or where to disable it.   Joe
FURRYe38's avatar
FURRYe38
Guru - Experienced User
Jul 13, 2020

Somthiing to try for your self and see. I recommend a factory reset and setup from scratch. I would ping test with out the RBS and ALL other devices disconnected from the RBR. use just a wired PC to test with initially. 

kwiebe wrote:

V2.3.5.26 RBS20

 

I just noticed this too.  Disturbing and it's not normal.  This needs to be fixed.

 

Did it get fixed in 2.5.1.16?

 

kwiebe's avatar
kwiebe
Aspirant
Jul 13, 2020

I was hoping to find out from someone already running the later firmware whether the ping behavior was still exhibited.  Seems like a reasonable inquiry.  Are you running the newer firmware FURRYe38?

    • kwiebe's avatar
      kwiebe
      Aspirant
      Jul 13, 2020

      OK great - does the ping behavior carry forward with the newer firmware?

      • FURRYe38's avatar
        FURRYe38
        Guru - Experienced User
        Jul 13, 2020

        Heres my ping with my mac book wirelessly connected pinging the RBR50:

        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=21.581 ms
        64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=5.296 ms
        64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=7.785 ms
        64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=13.785 ms
        64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=16.978 ms
        64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=12.250 ms
        64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=10.974 ms
        64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=8.575 ms
        64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=12.546 ms
        64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=24.586 ms
        64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=7.343 ms
        64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=5.241 ms
        64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=4.750 ms
        64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=10.755 ms
        64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=13.280 ms
        64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=12.145 ms
        64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=12.212 ms
        64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=5.385 ms
        64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=11.898 ms
        64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=12.723 ms
        64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=13.254 ms
        64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=4.815 ms
        64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=6.125 ms
        64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=14.790 ms
        64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=12.195 ms
        64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=12.695 ms
        64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=18.840 ms
        64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=5.331 ms
        64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=15.378 ms

         

        This is with everthing online.