NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
AX600 missing Port Forwarding setting
I have an AX600 in router mode that has been running for multiple years with the same configuration and I had a port forward rule configured that was working on the initial setup. I am trying to edit the Port Forward rule but I am not seeing the setting/option anywhere in the management portal. I see everything that I normally see but am missing any Security and Firewall settings. What am I missing?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.GS305E Setup VLAN's from behind the switch
The PC used to configure the switch permanently resides downstream of the switch, on a VLAN, and MGMT VLAN that is not 1. It becomes a chicken & egg problem where you will be constantly locked out and forced to reset the switch as you try all the different combinations. I tried googling for solutions and the closest was the topic GS305E Trunking tagged and untagged VLAN's. It was very helpful. However my issue is slightly different and I wanted to share what worked. It was... a process. Step 1: Configure your upstream switch with a trunked port for all the VLAN's you intend to have traffic through the GS305E switch. In the case of a Ubiquiti EdgeSwitch 24 for example, it absolutely 100% requires a new trunked port... even though you already likely have a main trunk tagged and setup for VLAN's. Step 2: Manually configure your PC's IP address to be in the 192.168.0.x subnet. Plug your PC into any port on the switch. Which port you choose to plug into does not matter for initial configuration, they are all configured identically. Use a browser and go to 192.168.0.139 and login with the password: password. There is no username so this switch is not appropriate for a multi-admin environment. Step 3: Change your password. This is mandatory and you will be presented with a screen to do so immediately upon first successful login. Step 4: You will immediately see the main system settings page (home). Disable DHCP mode and provide the device with a static IP within the subnet range where it will permanently reside. Also provide the subnet gateway IP (Subnet DHCP server). Apply the changes, no reboot necessary, the browser will timeout because the switch will now be found at that new static IP. You will likely want to change your PC's IP again to be within the new subnet range. Step 5: Go to VLAN > 801.q > Advanced: and enable the advanced option. Step 6: Advanced > VLAN Configuration: add your VLANs. You cannot remove VLAN 1 it is hardcoded and also used as the management VLAN by default. DO NOT attempt to change the management VLAN yet if your management VLAN is not 1. You will do that at the very end almost as the last step. This is why a lot of people (meeeee) have locked up their GS305E during initial configuration by changing that too soon, don't do that, don't touch it, live with management VLAN as 1 until you have everything working. Step 7: Advanced > VLAN Membership: this is where you setup your trunked port and tags. Now is when you decide which port you want to be the trunk port. I use port 1 but port 5 is also a logical choice. Whatever port you decide to make the trunk the default VLAN 1 should be untagged and the rest of your VLAN's under it tagged. Step 8: Advanced > Port PVID: the trunk port should always remain as PVID 1. Change the PVID's to your VLAN ID's. A note of caution if you have a different management VLAN than 1. This will lock you out and force you to plug into a fall back port. If your management VLAN is 1 then you should be finished. Step 9: Advanced > VLAN Configuration: If you need to change your management VLAN now is the time, the last final step. If you would have attempted to change your management VLAN at any time during the prior processes you would have been locked out and likely forced to hardware reset the switch to defaults. This is what worked for me. I spent about a day trying to get it all to work and honestly I believe the one thing that prevented me from succeeding most of the time was not setting up that port as a trunk port on the Edgeswitch. It shouldn't be needed like that but it definitely does not work if that trunk checkbox isn't checked. All feedback, corrections, comments, will be gladly accepted. Just please try to keep them constructive.M4300-52G-POE+ Bricked Recovery Method
Anyone knows how to recover from a power outage that bricked my M4300 ? M4300-52G-POE+ We had an outage. Power came back on, then the unit boots but none of the 52-ports came back up. The OOB port lights up when plugged into, but nothing. Then I console it and got the readout. It didn't even get past port0 and stalled out. Here is the vid: https://www.youtube.com/shorts/7Q5zGWaNzxY About 8 seconds into it and the screen will show upWe have several WAX610Y that were added to device groups
We have several WAX610Y that were added to device groups. Everything runs right now on the new insight platform. Some of them were added and other failed and we had to re-add them manually on the insight using the serial number and MAC Address. Since then, we have several devices that constantly loose access to the insight (cloud). We have checked about DHCP exhaustion but did not find any issue on that side. Any thoughts on that issue ?Disable Auto Firmware Update - SXR50/SXS50
I have the SXR50 and 3 SXS50 satellites. The recent firmware update (V4.3.2.200) totally dorked up the routers. I would experience disconnects to wireless and hardwired devices were not picking up IPs correctly. I reverted back to the previous firmware version (V4.3.2.100) and all issues were resolved. However, the option to disable Auto Update for the firmware is greyed out. Any idea why this would be and how to allow me to disable it so I do not run in to this again?Nighthawk M2 IP PassThrough stops working when idle
So I have a Nighthawk M2 in IP PassThrough with a VPN tunnel uplink over time it disconnects from 4G network for some reason and as soon as I login to the Nighthawk it springs to life. firmware NTG24_10.19.03.00 So anyone else having this problem? the ISP is o2
