NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
RS600 dropping connection, rebooting randomly...
I've had this RS 600 and it's been terrible. Very inconsistent wifi speeds, I tried manually changing channels, and the 5g line kept dropping out. Then today, the entire router crashed and was down for 5 minutes during a critical internet call. I'm on an experimental firmware 1.0.5.113 I spent a LOT on this router to get something reliable... and so far, this is not being that.Seeking update: client-side MLO on RS600 (Nighthawk WiFi 7)
Hi everyone, I'm trying to find out whether Multi-Link Operation (MLO) for client devices will be enabled on the RS600. I remember reading some comments about MLO coming to the RS700, but so far none of the RS600 firmware release notes (up to v1.0.5.12, Aug 2025) mention it. My support case #49306330 only yielded "no ETA". I have an RS600 running 1.0.5.12 here in France, and devices like the iPhone 17 Pro support Wi‑Fi 7 with MLO. Without MLO, a client can only use one band at a time, which limits throughput and increases latency. Competing vendors’ Wi‑Fi 7 routers (ASUS/TP‑Link) already support client MLO, and Netgear’s own Orbi 970 uses MLO on the backhaul. Is client-side MLO on the roadmap for RS600? If so, can Netgear give an approximate timeframe (beta or final)? It would be great if the RS600 could provide unified SSID MLO across 5 GHz and 6 GHz for devices that support it. Thanks!FYI, uPNP Port forwarding has Nat Loopback issues with DDNS... Use manual entering of ports instead
To anyone trying to access devices on your network via DDNS... Using uPNP for automatic port forwarding is resulting in DDNS failure behind the router, although devices can be connected outside the network. For instance, I have a Synology server, set up on my network, using xxx.synology.me:9999 as the ddns / port for accessing the server. Using upnp to set up ports, I could never access the server from inside the network, but it works fine accessing it outside the network. The way to resolve this, is to manually set up the port forwarding on the Netgear router. This has resulted in proper NAT loopback, allowing me to access xxx.synology.me:9999 from inside the network as well as from outside the network.
