NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Nighthawk M6 Pro April 14th 2024 Firmware Update
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?
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.
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 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.