NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
WAX204 cannot run on UPS
I have a WAX204 which I need to plug into a UPS. It runs okay if the UPS is plugged into AC power. However, whenever the power goes out, the router reboots and gets stuck in a boot loop. The loop happens whenever it is about to turn on the WiFi light, then it reboots back to the red light and repeats all over. However, once the AC power is restored to the UPS, everything is back to normal. I had thought it was the UPS power, and I bought a 2000VA / 1200W power supply, which is the same. How can I use this router on UPS? Here is the exact UPS: https://www.hikvision.com/africa/products/premises-distribution-system/ups/back-up-type-ups/ds-ups2000/Netgear WiFi 7 WBE710 Crashing/Rebooting
I have 3 WBE710 APs that I am not using InSights on only using local GUI. Last week I decided to update them from V11.5.1.5 to V11.8.0.14 and since then 1 AP has been having a Reboot reason code of "Crash". The other 2 APs are stable and have been up and online since the upgrade. All 3 APs are configured in the same settings minus two APs are configured to have the LEDs off. One of the APs that is configured to the LEDs off started crashing every 3-12 hours. I did a typical restore to defaults and reconfigured to match the other settings of the APs and the single unit continued to crash. As a quick test I downgraded the crashing unit back to V11.5.1.5 "downgrading forces factory reset", reconfigured again to match the exact settings of the other APs, minus the LED setting. Since then it has been stable. Quick Configuration Settings - Everything else is default. Static LAN IP Configured 192.168.x.x SystemName Set LED Disabled - High doubt it is this. I've seen weirder Single SSID Configured WPA3/WPA2 Personal VLAN ID configured Band Steering Enabled Wireless Settings - 2.4/5/6Ghz All 3 bands are configured with Dynamic Channel Width Any thoughts would be welcomed. I don't really want to leave them on mismatch FW.Second hand wax630 keeps restoring to insight
I have 4 second hand wax630 that are unable to restore to factory defaults When I restore them to factory default I am able to access the web page one time and when I try a manual setup it reboots and restores the previous owner insight settings. Tried this multiple times and was able to do a firmware upgrade on it, but after a while it keeps restoring to the previous owners insight setting Offcourse I have no access to this account, I have aquired them legally offcourse but find it strange that if someone locks them nobody can access them. I guess when an it manager leaves a company the company is pretty much screwed (or when the it support firm goes out off bussiness) Anyone a solution for thisERROR: can't get kernel image!
Hi, Overnight switch malfunction. I managed to connect to the switch with miniUSB console port using HyperTerminal port 23. I switched off/on couple of times. This is the error logs i get. :( Please help. I am attaching the pictures of switch too. " U-Boot 2012.10-00205-gef56c5f (Jan 01 2016 - 14:02:15)VerNo=1.0.0.7 UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:fs", error -19 UBIFS error (pid 0): ubifs_mount: Error reading superblock on volume 'ubi:fs' er rno=-19! ubifsmount - mount UBIFS volume Usage: ubifsmount <volume-name> - mount 'volume-name' volume UBIFS not mounted, use ubifs mount to mount volume first! ubifsload - load file from an UBIFS filesystem Usage: ubifsload <addr> <filename> [bytes] - load file 'filename' to address 'addr' Wrong Image Format for bootm command ERROR: can't get kernel image! ERROR: can't get kernel image! done UBIFS not mounted, use ubifs mount to mount volume first! ubifsload - load file from an UBIFS filesystem Usage: ubifsload <addr> <filename> [bytes] - load file 'filename' to address 'addr' Wrong Image Format for bootm command ERROR: can't get kernel image! Saving Environment to SPI Flash... done UBIFS not mounted, use ubifs mount to mount volume first! ubifsload - load file from an UBIFS filesystem Usage: ubifsload <addr> <filename> [bytes] - load file 'filename' to address 'addr' Wrong Image Format for bootm command ERROR: can't get kernel image! ERROR: Ethernet external port not connected at bcmiproc_eth.c:125/bcmiproc_eth_open() Wrong Image Format for bootm command ERROR: can't get kernel image!" Thank you MMGS110EMX not tagging frames
I've had this switch for quite a while but haven't had a need to configure VLANs until now. I've started by moving all the ports to Vlan 2, and configuring ports 7 and 8 - part of an LACP bundle - as tagged interfaces . However, pcaps on my upstream router show that frames coming from the switch over the trunk do not have VLAN tags; it's receiving tagged frames from the router and processing those correctly, but there are no tags from frames coming from the switch seen by the router. Any ideas what to check that might be misconfigured? Configuration screenshots below: Pcap from upstream router shows untagged frames from the switch, while response is properly tagged:WAX210 Firmware 1.1.0.34 Bug – SSID Password Complexity Incorrectly Enforced
Hi everyone — I’m seeing what looks like a firmware regression on the WAX210 after updating to v1.1.0.34, and I want to report it in case others are affected. After updating, the AP now refuses to save any configuration changes (even unrelated ones like just renaming the Access Point). The UI throws this error: SSID1: SSID passphrase length must be between 8 and 63 characters, and contain at least one uppercase letter, one lowercase letter, one number, and one special symbol. This happens even when the SSID password is not edited at all. The AP loads the existing (valid) WPA2/WPA3 passphrase and flags it as invalid due to a complexity requirement that didn’t exist before. This appears to be the AP Login Password complexity policy being mistakenly applied to SSID passphrases, which contradicts the official manual. SSID passwords for WPA2/WPA3 should only require 8–63 characters. Reproduction Steps Update WAX210 to firmware 1.1.0.34 Log into the web interface Make any change (example: AP Name only) Click Apply The SSID password complexity error appears, even though SSID settings were untouched Impact. The AP cannot accept any configuration changes unless the SSID password is replaced with a much more complex passphrase. This forces a complete re-key of all connected devices. Expected Behavior Per the WAX210 User Manual, SSID passphrases should be valid with: 8 to 63 characters No requirements for uppercase/lowercase/digits/symbols Those rules worked correctly in previous firmware versions. Current Workaround Rolling back to firmware 1.1.0.25 or 1.1.0.20 fully resolves the issue. Request Can Netgear please confirm whether this is a regression in 1.1.0.34 and escalate to the firmware engineering team? This issue effectively prevents configuration of the device. I can provide: Screenshots of the error dialog A configuration backup A short video showing the issue Exact hardware revision and serial if needed Thanks in advance.wax202 no ethernet connection
Hello, I have a wax202(AX1800) I was using as an access point then decided to move it to main router function so I did a reset. I don't know if its related but now I have no ethernet connection(no orange or green light and no internet connection to pc or laptop) My old netgear router has a working throughput for ethernet when connected so it's not an isp or cable issue. tried a pushbutton reset a few times no luck, is my 202 dead? Is there a way to push a firmware update without an internet connection? tyCan't access ReadyNAS Pro 6
Hello friends, As the title says, I have an old RNDP6000 and I can't access it. It had been turned off for a long time. I'm using Windows 11 Pro. Its readout shows it is on and displays its IP address. I can successfully ping that address with the cmd prompt, but it doesn't show up in Network. I can log into the Control Panel through a web browser and log in, but the CP says "No shares currently available", and offers no options or menus. I would welcome any and all advice! Thanks in advance.
