NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
GS110EMX VLAN features not working
In my prior post here I described an issue I'm having with my GS110EMX, which is not tagging frames on a trunked interface despite an apparently valid configuration. This switch is running Yesterday, reading the documentation of another vendor's switch, I came on a setting on that device where the switch did not tag frames if the vlan matched the port's PVID. Given that at the time (our teenager was in the middle of an intense online game), I decided to test this with a new VLAN. The setup (screenshots below) is as follows: Port 2 untagged on VLAN 10, PVID set to 10 Ports 1-6, 9, 10 untagged on VLAN 2, PVID set to 2 Ports 7/8 (LAG 1, LACP) tagged on VLANS 2 and 10, PVID set to 2. I plugged my laptop into Port 2, and ran several packet captures from both my client and the upstream router (a Mikrotik RB5009) during my testing. Some interesting (and maddening) results came from this: Traffic from untagged VLAN 2 ports appeared up the upstream router untagged, as previously observed. Broadcast DHCP requests from my laptop did not appear on the upstream router, at all. No traffic tagged with VLAN 10 was seen (caveat: I did not test the forwarding of non-broadcast traffic sent from my laptop into port 2 using a static IP configuration on the DHCP client). Attached below is a series of screenshots showing the configuration and the resulting PCAPs. Is there anything I'm missing, or is this a failure of the switch hardware itself? And yes, I did powercycle it to make sure that wouldn't change anything. GS110EMX configuration: LACP configuration for LAG 1 on Ports 7-8: 801.Q Configuration: 802.1Q Configuration: ports 2,7-8 as members.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.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 o2Netgear GS316EP reports as GS108EV3 after factory reset
We have an unused Netgear GS316EP 16 port switch. During troubleshooting we were asked to factory reset the switch. After factory reset it reverted to it's default IP address. When you connect via web to the switch via it's default IP address, the switch now says it is a GS108Ev3 8 port switch. The configuration utility is completely different from before. I downloaded the newest firmware but have not yet tried to install. The installation of firmware is even very different between the different models and I was concerned that the incorrect firmware (wrong model) might brick the switch. How can we get our 16 port GS316EP back? (We need all 16 ports not just 8)
Orbi : planning Allumage-extinction
Bonjour, Lors d'une prochaine version de firmware, les développeurs pourraient-ils nous rajouter une fonction permettant d'éteindre et de rallumer automatiquement le réseau WIfi en fonction des heures et des jours comment cela existe sur de nombreux appareils ? La solution d'éteindre manuellement (OFF) l'appareil n'en étant pas une, tout ce qui ne se fait pas automatiquement ne sera pas fait régulièrement, à fortiori si aucun voyant n'attire notre attention. Si d'autres utilisateurs, qui sauf erreur de ma part devraient être assez nombreux, pouvaient soutenir cette demande, cela stimulerait peut être les développeurs pour implémenter cette fonction. Merci à tous.
