NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Access Control Shows Device Both Connected & Not Connected
My RS300 Router's Access Control shows many devices that are connected and working properly as also listed as being allowed but disconnected! How can this be? If I remove the device from the "allowed but disconnected" section it then appears in the connected section as "BLOCKED". Is there a fix for this? It's obviously a bug in the router software or the firmware. Firmware Version: 1.2.7.2 Thanks, JerryStarlink Router
I bought a Netgear Nighthawk RS300 to be used with Starlink. I viewed a video that showed that you may not use the Starlink router and connect your own router directly to the Starlink power base and thus not use the Starlink router. So can I connect the RS300 router directly to Starlink and not connect the RS300 to the Starlink router and use the Bypass mode in the Starlink app.? Has anyone used this option of connecting your own router directly to Starlink and not using the Starlink router?Wi-Fi ping spikes every 10 seconds.
Ping jumps from around 5 ms to 100 ms every 10 seconds. The issue is reproducible only when connected via Wi-Fi. When connected to the router with an Ethernet cable, the problem does not occur. Resetting the router did not help. Steps to reproduce: 1. Connect to the router via Wi-Fi. 2. Start pinging any external service. 3. Observe the ping behavior.Router reset does not fully restore all settings while reset
Resetting the router does not clear all settings and does not change the router name. This leads to a situation where the user scans the QR code on the router, but the phone cannot connect to the router. The reason is that the app expects one set of credentials, while the router is actually using different credentials. ==== Can't change router's name because it then cause painful steps to restore the router in case it's neededRS300 & CityFibre - IDNet
Hello, Can’t seem to find conclusive evidence if the Netgear Nighthawk RS300 BE9300 will work with IDNet on a CityFibre connection. IDNet mentions VLAN 911 tagging but posts on the web seem to suggest the Netgear VLAN tagging implementation doesn’t cover the WAN port. Any feedback greatly appreciated. thanksDetermine IPv6 for a connected device
Greetings, I'm installing a new Ethernet device (it's a printer) and I made a slight oopsie. I disabled IPv4 in the web admin panel, because my network is 100% IPv6. Unfortunately I was connected via IPv4 to the web admin panel! Now I'm trying to determine the device's IPv6 assigned address(es) which should be at least one link-local and at least one routable: Surely the Nighthawk admin panels know this. I have access control enabled and I made sure to unblock/allow the device as soon as it showed up. So it had no connectivity problems and should be reachable over IPv6, but that seems not to be the case. Where in the Nighthawk RS300 admin panels can I find/determine IPv6 addresses of connected devices? Thanks!BE9300 Broken With 4kQAM Rate Set On BE200
So this is an interesting and very specific phenomenon I've narrowed down. The BE200 from intel and the BE9300 from Netgear completely bomb out their rate set negotiation when the signal is perfect. Yup, this means what you think. Moving the antenna further away or in a suboptimal position to force a lower RSSI so that 1024 QAM or lower is negotiated gives the expected bandwidth. It appears that one of the devices gets confused or "stuck" on properly allocating the available resource units or doesn't have 4kQAM properly mapped into a rate setting table. I've checked this repeatedly with spare wifi antennas, moving the PC around, and overzealous usage of iperf 3.2.0 against a wired PC also connected to the BE9300 as well as iperf on an iphone 16. The iphone 16's themselves appear fine under all conditions, but that's seemingly because they only support 160mhz wide connections and 1024QAM. Yup... apple runs their newer iphone 16s and 17s at 6E speeds, and it's on their official website as per https://support.apple.com/guide/deployment/wi-fi-ethernet-specifications-apple-devices-dep268652e6c/web. This is what it looks like when it's working and forced to a slightly weaker signal around 53db. This is what it looks like when the signal is stronger and 4kQAM is utilized on the link. As you can see the rate set for the uplink swaps to a 4kQAM mode while the downlink crashes and almost appears to be using the BPSK-DCM and BPSK-DCM-DUP rate sets listed as MCS indices 14 and 15 in the rate-set table for wifi7, instead of 12 or 13 as it should be. Either that or my other guess is the RU allocation "gets stuck" or confused under this specific scenario for some unknown reason. The BE9300 is using the latest 1.0.6.16 firmware, and the BE200 has been updated to the 24.20.2 drivers, although this has been an ongoing situation across multiple driver versions.
