NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
WAC510 firmware version 9 cannot use tagged VLAN.
I use WAC510 in local web management, with tagged VLANs to use multiple networks. However, the WAC510 firmware version 9, all devices cannot access the network normally in VLANs other than the m...
I was able to successfully self-solve this problem.
I updated the WAC510's firmware to the latest, did a factory reset and reconfigured everything from the initial settings, but still had the same problem.
Maybe, but it seemed that some people were using the same WAC510 and didn't have the same problem, so I next checked the operation, changing each setting one by one.
After doing so, I discovered what was causing the problem.
The problem was located under Management>Configration>Wireless>Basic>WLAN Settings.
I found that if the Wireless Client Isolation in the Advanced SSID setting was enabled, I couldn't communicate with any non-Wireless addresses too.
By disabling this setting, I was able to have network access on any VLAN other than the management VLAN.
I suspect that the point about not being able to communicate with non-wireless clients and gateways is a bug.
I'll be using this setting disabled until this issue is fixed.
Hello Nana11,
Is this WAC510 operating as a plain wireless access point, or do you experience this limitation in router mode?
Operating bunches of WAC5xx access points on various sites and venues, with at least two or more VLAN and SSIDs. Most are Insight managed (Premium and Pro sites), a hand full WAC are just locally managed. Have a local test set-up with an Insight managed switch and a local managed WAC540 on 9.1.0.13 - and we can't use SSIDs/VLANs off the base/untagged VLAN for the similar reason.
Hello schumaku,
This WAC510 is operating as a plain wireless access point mode, without Insight.
My site has three tagged VLANs.
The VLAN IDs are 11, 2001 and 4040.
The ID of the management VLAN is 11 and the communication is the same as with previous firmware.
Clients in VLANs 2001 and 4040 can get addresses from DHCP, but are unable to communicate with the gateway or within the VLAN.
These also used to be able to communicate without problems, but I had problems accessing it on version 9.
Is a large VLAN ID number not recommended?
Or is it not recommended to mix with L2 switches from other companies?
No obvious limitations hit there on the VLANs I'd say. It's all industry standard, using other brand switches should not cause an issue.
Since updating to v9 firmwares, have checked the configuration of the wired port VLAN config on Management > Configuration > Wired > VLAN ? Ensure all VLANs configured on the WiFi side exist here along with the tagging required.
I use local management, but I can't find "Wired" under "Configuration".
Below the "Configuration" are "System", "IP", "Wireless", "Security", and "Wireless Bridge".
I think the wired setting here is "IP".
There is only one child item here, "LAN".
There are Items that I think are related are "Untagged VLAN" and "Management VLAN".
I can't specify multiple VLANs as these places can only contain numbers.You wrote "WAC540 on 9.1.0.13" before.
Maybe the settings are different between WAC510 and WAC540?Sorry, my bad - the WAC505/510 don't have these controls.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
