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

Forum Discussion

jeadams's avatar
jeadams
Aspirant
Apr 12, 2019

BUG REPORT Nighthawk® AX12 RAX120 Router Firmware Version V1.0.0.84

Choosing option  WPA2-Personal[AES] + WPA3-Personal  encryption  disconnects IPAD 2 running IOS 10.3.3 Must choose WPA2-Personal [AES] to stay connected.
schumaku's avatar
schumaku
Guru - Experienced User
Apr 22, 2019
These old iPad 2 don't get any more updates. As a WPA2 device it has to associate the new RAX and run reliably.
mbze430's avatar
mbze430
Guide
May 04, 2019

Surface Pro 3 with the Marvell Wifi will not connect when set to WPA2+WPA3.  Will connected fine WPA2 even with AX enabled.

  • mbze430's avatar
    mbze430
    Guide
    May 04, 2019

    Also for HT160, center valid channels are 50 & 114....

     

    neither of those 2 channels are available when changing over to HT160

    • avtella's avatar
      avtella
      Prodigy
      May 04, 2019

      HT160 works fine, it just wont report the actual center channels in the GUI, it will just mention the 8, 20 Mhz channels used. 

      • avtella's avatar
        avtella
        Prodigy
        May 04, 2019

        They probably did that so novices don't get confused, at least that is my guess.

  • schumaku's avatar
    schumaku
    Guru - Experienced User
    May 04, 2019
    mbze430 wrote:

    Surface Pro 3 with the Marvell Wifi will not connect when set to WPA2+WPA3.  Will connected fine WPA2 even with AX enabled.

    Aehm, the many years old Surface Pro 3 does unlikley support a config for WPA3 (just like the mainstrem Windows 10 release which don't yet...).

     

    Should you talk of the router radio setting, this system isn't alone - several devices are struggling. Could be a client as well as a AP problem.

    • mbze430's avatar
      mbze430
      Guide
      May 04, 2019
      schumaku wrote:
      mbze430 wrote:

      Surface Pro 3 with the Marvell Wifi will not connect when set to WPA2+WPA3.  Will connected fine WPA2 even with AX enabled.

      Aehm, the many years old Surface Pro 3 does unlikley support a config for WPA3 (just like the mainstrem Windows 10 release which don't yet...).

       

      True the Marvell doesn't support WPA3.  However this new setting

      WPA2-Personal[AES] + WPA3-Personal

      lead one to think that devices that CAN authenticate via WPA3 will do so, if not it will fall back to WPA2.  Which that is the case for Android devices that I have tested.  When I have it set to that particular setting.  My Android devices continues to connect via WPA2 even though it doesn't connect at WPA3.  Which should happen as well in Windows or ANY other devices. 

      Which also hold true to this setting

      WPA-Personal [TKIP] + WPA2-Personal [AES]

      if a device can't connect at WPA2, it will fall back WPA.

       

      • schumaku's avatar
        schumaku
        Guru - Experienced User
        May 04, 2019
        Sure, and that's what this thread bug report is about - some clients fail to associate if the RAX is set to WPA3+WPA2.