NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
bug
3 TopicsBad Embedded Web Server
Have multiple NETGEAR WiFi routers in office. Prefer to use the office DNS to access them for obvious reasons (e.g., 'PetersWifi' instead of trying to remember IPv4/6 internal addresses like '192.168.245.22', especially since DHCP occasionaly changes the addresses). Unfortunately, calling the embedded admin page on the R7800s by name produces '404' or a bad page (a single digit, usually '0'). The R7800s work if I use the net local IP (sends me to admin login popup). All the other routers (e.g., the R6300s) work as expected regardless of using name, IPv4, or IPv6. Updated to firmware V1.0.2.28, but still fails. 90 day support (these are new routers) requests have produced nothing but a run-around, disrespect, insulting answers ('The Interenet is not available in AP mode.') and refusal to take documentation of the problem. They posted the report to the support web app with the title 'Unable to access the genie page using routerlogin.net' -- so it appears that their '2nd level support expert' doesn't understand basic networking concepts. So i turn to the community for help... anyone? * * * two WIFI access points on this network. One is called “R6300v2” and the other is called “R7800”: log onto the R6300 using its name and a browser, like so: Which gets me to the web interface: on the Nighthawk, here’s what happens: But it WORKS when I just use the IPv4 address:Solved3.8KViews0likes6CommentsWLAN config changes not possible
Hi Guys, I got a problem with my R8000. At the moment its broadcasting the default configured SSID, but for security purpose I want to configure my own SSID / PSK. But this doesn't seems to be possible. When I try to save a change on the SSID / PSK Menu, it gets cancelled: This DFS-Channel cant be used because a radar gets detected. (Error message in german, I translated it, so therefore it could be, that it isnt the exact error message on a english ui) BUT: The error appears even if the second 5G-Radio isn't even turned on, so therefore this shouldnt bother. Further, the first 5G-Radio is sending on a non-DFS-Channel, so this couldnt be the problem either. For me this seems to be a bug. I'm using V1.0.3.4_1.1.2 which seems to be the latest version. kind regards, AndreasSolved8.3KViews0likes12Comments