NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
JLS02
Mar 26, 2024Aspirant
Possible Firmware bug MR6550
I am in the process of replacing my MR6500 with an MR6550 because of an channel issue with the 5G network for T-Mobile in my primary usage area. The issue is I use this as a backup connection for my ...
KLLC
May 25, 2024Aspirant
I can report that this is a bug that exists with current .47 FW for MR6550.
I am trying to use 2x MR6550 (set up in Failover mode (2x different cellular internet providers)), with each MR6550 connected via Ethernet to a different ethernet port on my Dual WAN-capable router (Asus GT-AX6000).
When I put each MR6550 in IP Passthrough mode, no matter what value I had previously set and saved (and confirmed working) as the IP address for the MR6550 (e.g., 192.68.1.1; 10.65.50.1; etc.,), the IP address after reboot in IP Passthrough mode will automatically reset to 192.168.3.1. This is a problem when I use the 2x MR6550 because 2x MR6550s having the same IP address in IP Passthrough mode does not work with a router having Dual WAN capability. This issue did not exist in earlier FW versions (e.g., NTGX65_12.01.13.00), as I was able to program a different IP address for each MR6550, and that programmed IP address stayed the same on reboot into IP Passthrough mode.
For now, my second MR6550 is being returned; if Netgear can fix this issue in future FW versions (i.e., have changeable MR6550 IP address which stays changed when put MR6550 in IP Passthrough mode), then I will revisit purchasing a second MR6550 at that time.
Thanks.
P.S. I would appreciate it if anyone can report whether this issue has been resolved in the NTGX65_12.01.54.00 FW that Netgear recently released; I don't want to take FW update if it has not. Thanks.
MR6550
Firmware Version: NTGX65_12.01.47.00
Firmware Build Date: 2023/11/04
Hardware Version: 1.0
PRI Version: 04.11
Web App Version: MR6550-GENPAS_05.00.94.00
- JLS02Jun 15, 2024AspirantThe issue is still present in the new firmware as well. I tried to get Netgear to allow me to register this used product so that I could report the bug myself however I can’t get anyone from Netgear to respond to me.