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

Forum Discussion

EranSagi's avatar
EranSagi
Follower
Mar 24, 2021

How to Generate a specific band WIFI SSID ?

Hi Guys,

I'm using the Netgear NightHawk WIFI6 Mesh router and sattliete system (MK62).
I have a smart device which requires 2.4Ghz access, 
I'm looking for a way to identify a designated SSID for 2.4Ghz so I will be able to register the smart device to the WIFI and my smart mobile app.

I'm using Samsung Note10P as a mobile device. and a Smartr device (using the icomenX2 mobile App for Android).

Any Ideas how to work arround the dual band single SSID end point ?

 

Thanks, Eran

2 Replies

  • Christian_R's avatar
    Christian_R
    NETGEAR Employee Retired
    Mar 26, 2021

    Hello EranSagi,

     

    The Nighthawk mesh system currently does not support this feature. 

     

    Christian 

  • schumaku's avatar
    schumaku
    Guru - Experienced User
    Mar 26, 2021
    EranSagi wrote:

    I have a smart device which requires 2.4Ghz access, 

    Also this Nighthawk Mesh system can perfectly serve devices working on 2.4 GHz only ... the IoJ does not know about the 5 GHz band.

     

    EranSagi wrote:

    I'm looking for a way to identify a designated SSID for 2.4Ghz so I will be able to register the smart device to the WIFI and my smart mobile app.

    Head out to the maker of this IoJ product support or App feeback and explain them on how decent wireless systems are working - feel free to send them a link or this information - and ask when this simple fix will be made vailable to the App:

     

    ===

    There is _no_ technical need to connect to the 2.4 GHz radio - the only purpose _was_ for legacy routers where different network names are used for connecting to th every same network, so the App will pick the correct SSID (network name) to be configured to the IoT.

     

    What really happens? The factory reset IoT are putting up a typically hidden set-up SSID on air, the App will fetch the current WiFi SSID (probably also the security key), briefly disconnect from the WiFi network, search for the manufacturer specific SSID on air and connect insecure or with a predefined password, then push the WiFi SSID (along with the wireless security key or passphrase) to the IoT.

     

    At no point it's required to have the mobile on the 2.4 GHz network - especially not on modern Mesh systems using a single SSID. It does not matter if the mobile with the App is connected to a 2.4 GHz, a 5 GHz, a 60 GHz network, or the new WiFi 6E 6 GHz band the latest wireless systems can use - permitting all wireless SSID and security are set the same.

     

    All they have to do is remove the stupid check for a 2.4 GHz connection, or allow to skip this check (instead of a dead end!) in their stupid discovery and configuration Apps.

     

    For  reason, no mobile device wireless client does allow a control which band should be used - because ONE SSID defines the connection to ONE network.

    ===