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

Forum Discussion

afraz92's avatar
afraz92
Follower
Aug 12, 2025

Guest Network & Dual Band Issues on Nighthawk M6 (MR6150-100EUS)

Hi everyone,

 

I’m using a Netgear Nighthawk M6 (MR6150-100EUS) and recently ran into two problems that weren’t there before — everything used to work fine until a short while ago:

  1. Guest Wi-Fi network not showing up
    • Guest network is enabled in the admin panel and set to broadcast.
    • SSID is simple, no special characters.
    • Broadcast is active but the SSID is invisible on all devices (iOS, Android, Windows).
    • Tried reboots, changing SSID/password, and other settings — no luck.
  2. Dual band issues
    • I have 2.4 GHz + 5 GHz enabled, but only 2.4 GHz works.
    • No device will connect to 5 GHz.

 

What I’ve tried so far:

  • Full factory reset
  • Updated firmware
  • Different SSIDs and passwords

 

The problems still remain. I’m trying to figure out whether this is:

  • A firmware bug
  • A new compatibility issue
  • Or a hardware fault

 

Has anyone here run into something similar with the MR6150-100EUS? Any tips or solutions would be greatly appreciated.

 

Thanks,

Afraz

1 Reply

  • Hi afraz92​,

    The 5 GHz and Guest SSID problems with your MR6150 appear to be more related to channel/security settings than to a hardware malfunction.  The M6 frequently switches to WPA3-only mode or DFS channels by default, which many devices cannot see.  Try this:

     Select Dual-Band (2.4 & 5 GHz) on the web user interface.

     With a 40/80 MHz width, force 5 GHz to Channel 36/40/44/48.

     Use combined WPA2/WPA3 or WPA2.

     To rule out power/thermal constraints, test in Plugged-In/In-Home mode (battery removed).
     Verify that the 5 GHz beacon is truly broadcasting by using a Wi-Fi scanner.
     It's worth establishing a case with Netgear support if, after trying those settings, 5 GHz still doesn't appear. This could indicate a hardware issue or a firmware regression (try an older stable build).