Nighthawk M6 Pro April 14th 2024 Firmware Update

[JVB2112]

Last night I updated the firmware on my Nighthawk M6 Pro to a new version with a release date of April 14th 2024. Does anyone know what is in this release? Are there release notes anywhere for it?

[Blanca_O]

Hi @JVB2112

Please provide the device SKU (e.g. MR6150-100EUS) and the firmware version.

Regards,
Blanca
Community Team

[JVB2112]

Hi Blanca…

The model of my device is a MR6550-100PAS.  The firmware version is NTGX65_12.01.54.00 (2024/04/12)

Thanks,

Josh

[ywkuo227]

Any idea how to force this update? Thanks

[JVB2112]

All I had to do was go into the update check screen and it automatically downloaded over cellular.

[ywkuo227]

Lucky....I tried a dozen times today and no luck.

[JVB2112]

Do you have the exact same model that I posed above?

[ywkuo227]

Yes, MR6550-100PAS

[JVB2112]

Maybe it’s only for certain carriers?  I’m with Rogers in Canada.

[ywkuo227]

😞 Perhaps…. I am using Google Fi in US

[Blanca_O]

Hi, All, 

M6/M6 Pro FW 12.01.54.00 release notes: 
- Insight Support for M6 Pro Retail SKUs
- Updated Error codes
- Router Analytics Opt-in/Opt-out
- WiFi issue fixes
- APN fixes

Device SKU: 
- MR6150-100EUS
- MR6150-100NAS
- MR6450-100EUS
- MR6550-100APS
- MR6550-100PAS
 

Regards,
Blanca
Community Team

[rogerr2]

DO NOT UPDATE!! THIS FIRMWARE RUINED MY MR6550. 

Seriously, it will prefer 4g band even when in range of 5g so your internet speeds will be super slow and service will even cut out.  My latency fluctuates between 500ms and 5000ms.

[JVB2112]

Not to discount your experience, I’ve not had any issues with the update. No problems maintaining 5G connection, and no high latency.

[igorjrr]

Same experience as @rogerr2 .

Unfortunately the update was automatic.

Immediately after this firmware version NTGX65_12.01.54.00, my internet hangs after some time using it. I can see that clearly during games, where it disconnects. It comes back after a long pause, but there is an issue.

This was NOT happening with previous firmwares.

There is a problem with this firmware version NTGX65_12.01.54.00.

@Blanca_O please notify the developers / product manager @JohnPeng .

I have no doubts it is a problem introduced by this firmware, and I'd like to downgrade and disable automatic updates. The previous firmware was working very well and in my case there was no need for updates.

Please assist in reverting the firmware to NTGX65_12.01.47.00.

[NickTech360ny]

We also had 3 different M6 Pro's (MR6550) and each of them seemingly took the update and installed automatically without our knowledge. We've seen a lapse in connectivity, high latency and a much higher usage over the past few weeks without any change in hardware. Ive been told so far there's no way to roll back the firmware and what i'm afraid of is if the rollback is possible, but the update is automatic, will the firmware automatically update itself again? Mae from netgear is escalating this to the engineering department but I get the feeling I wont get the answers i need. 

[KLLC]

For those of you who have taken the FW update, can you confirm whether this .54 FW (NTGX65_12.01.54.00) fixes the issue where you cannot change the router's IP address if you put it in IP Passthrough mode (i.e., in IP Passthrough mode, router IP address automatically becomes 192.168.3.1, and cannot be changed and any prior change is nullified as IP address on IP Passthrough reboot becomes 192.168.3.1)?

Also, for those looking to downgrade MR6550 FW to .47 (and to block automatic FW updates), Google is your friend.

[JohnPeng]

---

@KLLC wrote:

For those of you who have taken the FW update, can you confirm whether this .54 FW (NTGX65_12.01.54.00) fixes the issue where you cannot change the router's IP address if you put it in IP Passthrough mode (i.e., in IP Passthrough mode, router IP address automatically becomes 192.168.3.1, and cannot be changed and any prior change is nullified as IP address on IP Passthrough reboot becomes 192.168.3.1)?

Also, for those looking to downgrade MR6550 FW to .47 (and to block automatic FW updates), Google is your friend.

---

I am working on your support case for the IP passthrough issue. I still don't understand why 192.168.3.1 could cause any connectivity issue. The device will get the network assigned IP address when IP passthrough is enabled, then the local DHCP server will not working anymore. Setting to 192.168.3.1 or any other IP address will not impact the data connection.

If you want to visit the admin portal, please check whether you can modify your local network IP address settings to work around the issue?

Thanks

[JohnPeng]

---

@NickTech360ny wrote:

We also had 3 different M6 Pro's (MR6550) and each of them seemingly took the update and installed automatically without our knowledge. We've seen a lapse in connectivity, high latency and a much higher usage over the past few weeks without any change in hardware. Ive been told so far there's no way to roll back the firmware and what i'm afraid of is if the rollback is possible, but the update is automatic, will the firmware automatically update itself again? Mae from netgear is escalating this to the engineering department but I get the feeling I wont get the answers i need. 

---

I am checking your support case and will get back to you soon.

Thanks

[KLLC]

@JohnPeng The issue with 192.168.3.1 (and Netgear having removed ability to custom set router IP address in IP Passthrough mode) only arises when I use 2x MR6550s (each having a separate carrier) connected to a single Dual WAN capable router.

When the condition (WAN 1 failure) happens to trigger the router's WAN2 connection (i.e., through failover mode), the router does not successfully connect to the second MR6550 (and its 192.168.3.1 address) on WAN 2. I believe that this happens because the router sees the same IP address on the WAN 2's MR6550 as was on WAN 1's (now failed connection) MR6550. The reason I believe this to be the reason is when I use a Netgear router that still has the ability for me to set the router IP address in IP Passthrough mode (i.e., MR5100), and I set this MR5100's IP address to be something different than 192.168.3.1, my router successfully connects to the MR5100 on WAN 2 when my WAN 1 MR6550 (and its 192.168.3.1 IP address) fails.

Re: your "If you want to visit the admin portal, please check whether you can modify your local network IP address settings to work around the issue?", I can modify the IP address when I am NOT in IP Passthrough mode (and my modification sticks), but when I go into IP Passthrough mode, the router IP address ALWAYS reverts back to 192.168.3.1 (and this is me having tested this on 3x MR6550s - 2x returned because of this issue (I kept only 1x)).

Hopefully, the above helps you better understand issue.