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

Forum Discussion

jwong84's avatar
jwong84
Aspirant
Sep 11, 2015
Solved

R7000 2.4ghz not working but 5ghz is fine

Firmware 1.0.4.30 and 1.0.4.28 tried for weeks at a time.   Wireless devices connected to 5ghz band are all working perfectly and have been since i purchased this router at the beginning of June ...
Troubleshooting
  • Nifer's avatar
    Nifer
    May 25, 2016

    Good news! We now have a production version of firmware that should resolve the 2.4 GHz issue, v1.0.5.64. You may download this firmware from our R7000 page here: http://downloadcenter.netgear.com/en/product/R7000#searchResults

     

    As IrvSp correctly notes, this version of firmware fixes the 2.4 GHz issue and reinstates the new features, such as Kwilt, Smart Connect, and WiFI Transmit Power Control. It does not support Arlo.  We hope to have a beta version that supports Arlo in the next two weeks.

     

    We welcome any feedback you provide on this new firmware, and appreciate your patience as we resolved these issues. Thank you all for supporting the R7000 and NETGEAR!

Kernald's avatar
Kernald
Guide
Feb 01, 2016

Here are some logs I got from a Linux laptop, not sure if relevant (I don't use the router as my main unit anymore, so I wasn't using the laptop at that specific moment), but...

 

[24787.047715] wlan0: authenticate with c4:04:15:5b:ad:ec
[24787.065736] wlan0: send auth to c4:04:15:5b:ad:ec (try 1/3)
[24787.070892] wlan0: authenticated
[24787.071609] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3)
[24787.090121] wlan0: RX AssocResp from c4:04:15:5b:ad:ec (capab=0x1411 status=0 aid=3)
[24787.090222] wlan0: associated
[26595.067399] wlan0: AP c4:04:15:5b:ad:ec changed bandwidth, new config is 2437 MHz, width 1 (2437/0 MHz)
[26595.067407] wlan0: AP c4:04:15:5b:ad:ec changed bandwidth in a way we can't support - disconnect
[26596.171009] wlan0: authenticate with c4:04:15:5b:ad:ec
[26596.187849] wlan0: send auth to c4:04:15:5b:ad:ec (try 1/3)
[26596.191355] wlan0: authenticated
[26596.192287] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3)
[26596.299421] wlan0: associate with c4:04:15:5b:ad:ec (try 2/3)
[26596.401514] wlan0: associate with c4:04:15:5b:ad:ec (try 3/3)
[26596.532624] wlan0: association with c4:04:15:5b:ad:ec timed out

Once I got the bandwidth change, it struggled to connect back for a while, with a ton of this kind of entries:

[38978.203911] wlan0: authenticated
[38978.205258] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3)
[38979.018988] wlan0: associate with c4:04:15:5b:ad:ec (try 2/3)
[38979.597474] wlan0: associate with c4:04:15:5b:ad:ec (try 3/3)
[38979.931728] wlan0: association with c4:04:15:5b:ad:ec timed out
[38987.901790] wlan0: authenticate with c4:04:15:5b:ad:ec
[38987.916788] wlan0: send auth to c4:04:15:5b:ad:ec (try 1/3)
[38988.584247] wlan0: authenticated
[38988.584990] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3)
[38988.744159] wlan0: associate with c4:04:15:5b:ad:ec (try 2/3)
[38988.874270] wlan0: associate with c4:04:15:5b:ad:ec (try 3/3)
[38989.030395] wlan0: association with c4:04:15:5b:ad:ec timed out
[39000.005472] wlan0: authenticate with c4:04:15:5b:ad:ec
[39000.023958] wlan0: send auth to c4:04:15:5b:ad:ec (try 1/3)
[39000.057593] wlan0: authenticated
[39000.058608] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3)
[39000.621133] wlan0: associate with c4:04:15:5b:ad:ec (try 2/3)
[39000.957932] wlan0: associate with c4:04:15:5b:ad:ec (try 3/3)
[39001.147543] wlan0: association with c4:04:15:5b:ad:ec timed out
[39019.021418] wlan0: authenticate with c4:04:15:5b:ad:ec
[39019.039874] wlan0: send auth to c4:04:15:5b:ad:ec (try 1/3)
[39019.092735] wlan0: authenticated
[39019.093598] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3)
[39019.631177] wlan0: associate with c4:04:15:5b:ad:ec (try 2/3)
[39019.841233] wlan0: associate with c4:04:15:5b:ad:ec (try 3/3)
[39020.125504] wlan0: association with c4:04:15:5b:ad:ec timed out
  • TheEther's avatar
    TheEther
    Guru
    Feb 01, 2016
    Kernald wrote:

    Here are some logs I got from a Linux laptop, not sure if relevant (I don't use the router as my main unit anymore, so I wasn't using the laptop at that specific moment), but...

     

    [24787.047715] wlan0: authenticate with c4:04:15:5b:ad:ec
[24787.065736] wlan0: send auth to c4:04:15:5b:ad:ec (try 1/3)
[24787.070892] wlan0: authenticated
[24787.071609] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3)
[24787.090121] wlan0: RX AssocResp from c4:04:15:5b:ad:ec (capab=0x1411 status=0 aid=3)
[24787.090222] wlan0: associated
[26595.067399] wlan0: AP c4:04:15:5b:ad:ec changed bandwidth, new config is 2437 MHz, width 1 (2437/0 MHz)
[26595.067407] wlan0: AP c4:04:15:5b:ad:ec changed bandwidth in a way we can't support - disconnect
[26596.171009] wlan0: authenticate with c4:04:15:5b:ad:ec
[26596.187849] wlan0: send auth to c4:04:15:5b:ad:ec (try 1/3)
[26596.191355] wlan0: authenticated
[26596.192287] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3)
[26596.299421] wlan0: associate with c4:04:15:5b:ad:ec (try 2/3)
[26596.401514] wlan0: associate with c4:04:15:5b:ad:ec (try 3/3)
[26596.532624] wlan0: association with c4:04:15:5b:ad:ec timed out

    Once I got the bandwidth change, it struggled to connect back for a while, with a ton of this kind of entries:

    [38978.203911] wlan0: authenticated
[38978.205258] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3)
[38979.018988] wlan0: associate with c4:04:15:5b:ad:ec (try 2/3)
[38979.597474] wlan0: associate with c4:04:15:5b:ad:ec (try 3/3)
[38979.931728] wlan0: association with c4:04:15:5b:ad:ec timed out
[38987.901790] wlan0: authenticate with c4:04:15:5b:ad:ec
[38987.916788] wlan0: send auth to c4:04:15:5b:ad:ec (try 1/3)
[38988.584247] wlan0: authenticated
[38988.584990] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3)
[38988.744159] wlan0: associate with c4:04:15:5b:ad:ec (try 2/3)
[38988.874270] wlan0: associate with c4:04:15:5b:ad:ec (try 3/3)
[38989.030395] wlan0: association with c4:04:15:5b:ad:ec timed out
[39000.005472] wlan0: authenticate with c4:04:15:5b:ad:ec
[39000.023958] wlan0: send auth to c4:04:15:5b:ad:ec (try 1/3)
[39000.057593] wlan0: authenticated
[39000.058608] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3)
[39000.621133] wlan0: associate with c4:04:15:5b:ad:ec (try 2/3)
[39000.957932] wlan0: associate with c4:04:15:5b:ad:ec (try 3/3)
[39001.147543] wlan0: association with c4:04:15:5b:ad:ec timed out
[39019.021418] wlan0: authenticate with c4:04:15:5b:ad:ec
[39019.039874] wlan0: send auth to c4:04:15:5b:ad:ec (try 1/3)
[39019.092735] wlan0: authenticated
[39019.093598] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3)
[39019.631177] wlan0: associate with c4:04:15:5b:ad:ec (try 2/3)
[39019.841233] wlan0: associate with c4:04:15:5b:ad:ec (try 3/3)
[39020.125504] wlan0: association with c4:04:15:5b:ad:ec timed out

    I found a few threads on the Internet that suggest that this could be a Linux problem with handling changes between 40 MHz and 20 MHz channels. It's pretty much impossible to use 40 MHz at 2.4 GHz whenever other Wi-Fi networks are active.  You can force the R7000 to use 20 MHz channels by changing the wireless mode from Up to 600 Mbps to Up to 289 Mbps.  This might avoid the Linux issue.