NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
MarcHChampagne
Nov 21, 2020Guide
Nighthawk mesh MR60 - devices that require 2.4 GHz connection
Please be patient and descriptive in your replies, I pick things up pretty quickly but am far from a network engineer. I upgraded my entire network when the pandemic lockdown started due to my en...
- Nov 28, 2021
Thank you so much worked for me...I turned off my 2 satellites and went into my garage. I connected all my smart outlets in there.
Silly_PuTTY
May 03, 2021Guide
I have the MK83 (MR80/MS80) and the solution for me was to go into advanced -> customize wifi and it lets you create a new 2.4GHz only SSID. So now I have a robot vac soley on it's own SSID. Fun.
Did this option ever make it's way down to the MK63 line?
- MarcHChampagneMay 20, 2021Guide
Silly_PuTTY wrote:I have the MK83 (MR80/MS80) and the solution for me was to go into advanced -> customize wifi and it lets you create a new 2.4GHz only SSID. So now I have a robot vac soley on it's own SSID. Fun.
Did this option ever make it's way down to the MK63 line?
Nope.
The MR60/MK60/MS60 line seems to be a "beta"
People paid lots of money for a system, and had problems. They fixed the problems in the "80" series, not the "60" series and now I either have to pony up more money to buy the MR80, or get rid of all my "smart" devices.
Thanks Netgear.
- schumakuJun 17, 2021Guru
MarcHChampagne wrote:People paid lots of money for a system, and had problems. They fixed the problems in the "80" series, not the "60" series and now I either have to pony up more money to buy the MR80, or get rid of all my "smart" devices.
You are mixing up two products with different feature sets.
Granted, Netgear would do much better taking care on product continuity on the same product family instead of feature nut picking expecting higher sales numbers on the latest product versions only.
Ref. "problems". The majority of issues are caused by "smart" devices App requiring a forced connection on 2.4 GHz (something virtually no wireless client can do), and by poor IoT wireless client implementations struggling about extended standard data like AX mode bits or RRM (radio resource management) bits in use for informing capable clients of neighboring access points for the same network.
Benj3390 wrote:
...when u log in go to advanced settings then wireless settings and at the bottom it says enable AX with a check box beside it that is already checked i was told to uncheck this box and hit apply when it was done updating i was able to connect my devices that use 2.4ghz ......a typical example of an IoT WiFi client struggling on the AX bits, not on the concurrent 5 GHz and 2.4 GHz availability of the same network and SSID. Very useful 8-)