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

Forum Discussion

Rossi141's avatar
Rossi141
Aspirant
Jan 03, 2022

MR1100 Dropping pings to gateway

Hi all - I have an Nighthawk M1 Hardware version 1 running:

NTG9X50C_12.06.39.00

This is on an AT&T network.

My local network is 192.168.1.0/24

My gateway is 192.168.1.1

I have been suffering from outages, where even though my Wifi is connected correctly, I am unable to access the Internet. I have started to run a continuous ping to my gateway on 192.168.1.1, and what I see is during these periods, for 10 - 15 seconds at a time my gateway at 192.168.1.1 is not responding, then it comes back and works fine.

This happens both on 2.4GHz and 5.0Ghz, but not at the same time (I have 2 laptops running the same test of different frequencies).

I have checked for overlapping channels - I am on a unique channel on both frequencies.

My RSSI for 2.4GHz is sitting at -51 and my noise at -92

 

Does anyone have any ideas of what I can check next or thoughts on a solution?

I think my next step is to factory reset my M1 and re-setup, howver, I hate to do that without understanding what the issue is.

1 Reply

  • 5GHz seems to be working a little better now. I am not sure exactly which one helped, but I disabled the following:

    WPS

    UPnP

    DNLA

    WIFI Standby

     

    It still rotates through higher latency for no apparent reason, but no longer drops out on 5GHz

    64 bytes from 192.168.1.1: icmp_seq=17815 ttl=64 time=4.206 ms
    64 bytes from 192.168.1.1: icmp_seq=17816 ttl=64 time=3.344 ms
    64 bytes from 192.168.1.1: icmp_seq=17817 ttl=64 time=2.918 ms
    64 bytes from 192.168.1.1: icmp_seq=17818 ttl=64 time=3.914 ms
    64 bytes from 192.168.1.1: icmp_seq=17819 ttl=64 time=3.236 ms
    64 bytes from 192.168.1.1: icmp_seq=17820 ttl=64 time=11.040 ms
    64 bytes from 192.168.1.1: icmp_seq=17821 ttl=64 time=5.247 ms
    64 bytes from 192.168.1.1: icmp_seq=17822 ttl=64 time=11.177 ms
    64 bytes from 192.168.1.1: icmp_seq=17823 ttl=64 time=2.889 ms
    64 bytes from 192.168.1.1: icmp_seq=17824 ttl=64 time=5.217 ms
    64 bytes from 192.168.1.1: icmp_seq=17825 ttl=64 time=4.465 ms
    64 bytes from 192.168.1.1: icmp_seq=17826 ttl=64 time=4.551 ms
    64 bytes from 192.168.1.1: icmp_seq=17827 ttl=64 time=3.311 ms
    64 bytes from 192.168.1.1: icmp_seq=17828 ttl=64 time=3.261 ms
    64 bytes from 192.168.1.1: icmp_seq=17829 ttl=64 time=2.416 ms
    64 bytes from 192.168.1.1: icmp_seq=17830 ttl=64 time=2.359 ms

     

    The 2.4GHz does still drop.