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.
The issues I've spotted here were related to some testing of WPA3-personal ... once Windows had seen WPA3 for an SSID, it will only connect very briefly to an SSID (regardless if untagged or tagged) configured for WPA2-PSK. Easiest way is dropping the known network entry, or use the assistant to fix it, will offer a control for changing from WPA3-personal to WPA2-PSK. Different behaviour was caused here by various test configs on untagged and tagged SSIDs.
Said that, I can't see any issues with multiple SSIDs associated to defined VLANs on WAC505/510/540/564 being on Insight environments or local Web managed devices with Netgear and other vendor VLAN trunk port configured switches.
You can always download the tech support or config form your WAC in question, send a link (e.g. Google Drive) share, and RaghuHR will look into it.
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.
One point to note.
I had the URL filtering feature disabled, but I was having this problem.
I should note that the situation is different from what is described in the "Known Issues" section of the firmware release page.Wow, great find!
Nana11 wrote: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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
