NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
WAX630E cross-VLAN traffic still broken after over a year since Netgear is aware of the bug.
There's this nice topic that I can't reply on:
https://community.netgear.com/t5/Business-Wireless/WAX630E-VLAN-bug/td-p/2325009
So I'm running on the latest firmware - V10.8.10.10 in standalone mode. And guess what, it is still not working.
Yes, this is over a year now and it appears Netgear didn't fix the VLAN related issues on this high end AP model and they tell customers over support to return the device when they find out. What a wonderful experience.
TL;DR: Device is advertised to "control VLAN separately for each SSID". This is right on the product page. And it works, partially.
Now try to talk from device on one SSID/vlan to device on different SSID/vlan (traffic goes via a router/firewall ofc). Good luck. You have IoT network and try to access those devices? Oh that's a shame.
I debugged this issue for too long before I found the linked thread so I missed my return window.
This is unacceptable on this class of device. How this even works in corporate enviroments?
5 Replies
Hello kitor,
And welcome to the NETGEAR Community! đ
I had this issue with Netgear Engineering team that Vlan traffic across will not pass when connected to the same WAX630E Access point. It was advised that this was a product limitation to all Maple products of Netgear Access point which includes WAX630E We ended up replacing the unit to a WAX630 or a WBE710 if need a 6Ghz since the first does not. It will best to open a support case either to report this back to Netgear Engineering team to push a certain fix for the Maple products, otherwise it will end up a product replacement again.
Have a lovely day,
Rene D
Netgear TeamI have the same probleme device in 2 ssid with different vlan on the same wax630e cant talk eahother
i have pfsense as firewall and rule are ok ...
what is the workaround ? changing wax630e to wbe710/750 the only solution ?
If you need a workaround, you can put some kind of proxy in between (even for TCP conns you can run haproxy in TCP mode). I've done exactly that, but this is BS it is even needed.
As for ReneD - this device doesn't come from official Netgear distribution, so I am not likely to get any support.
On the other hand I talked with a friend who is a major OpenWRT contributor and he expressed his potential interest in porting to this device.
This is pretty sad as except this tiny issue I am actually happy from this device performance. It just crashes previous Cisco Meraki APs I had.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
