NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
WAX630E: VLANs Not Behaving Correctly
Hi there,
I'm having an issue with WAX630E units at a site. VLANs are correctly configured but behaving oddly. Here are some verified facts.
- Connect WiFi to VLAN A SSID = Get VLAN A DHCP (good)
- Connect WiFi to VLAN B SSID = Get VLAN B DHCP (good)
- Connect CAT cable to VLAN A + Ping Printer on VLAN B = works (good - there's a firewall rule allowing this)
- Connect CAT cable to VLAN A + Print to Printer on VLAN B = works (good)
- Connect WiFi to VLAN A SSID + Ping Printer on VLAN B = works (good)
- Connect WiFi to VLAN A SSID + Print to Printer on VLAN B = does not work! (bad)
What the heck? Everything on the physical network operates as expected.
I think I'm running these APs with mostly default settings with each SSID in bridge mode. What could be causing this?
6 Replies
Does anyone have any ideas or questions?
Here are some thoughts ?
AP tags packets from wireless (802.11) to wired 802.3 with VLAN A
and expects packets from wired to wireless to also reach AP VLAN A
- Connect Wired PC to VLAN A SSID + Print to Printer on VLAN B = Good - Static Route configured.
- Connect WiFi to VLAN A SSID + Print to Printer on VLAN B = does not work! (bad)
1) What is port config where AP is connected ?
2) What is port config where PC was connected directly on wired side ?
3) who (switch or router) is converting control packets from printer that come tagged with VLAN B to VLAN A before it reaches the AP ?
Port where AP is connected should be a trunk port and static route configured on switch or gateway should make sure packets to clients in this SSID
WAX630A will tag VLAN A SSID packets from wireless clients as VLAN A.
for the reverse direction, who will convert VLAN B (printer control packets) to VLAN A ?
Thanks for the response!
1) The port is configured as a trunk. VLAN A is untagged and VLAN B is tagged.
2) It was untagged VLAN A. No direct access to VLAN B. Just a firewall rule allowing this type of traffic between A and B.
3) All firewall rules are in the firewall (pfsense). However, the pfsense is not aware of the difference between WiFi and hard-wired. Again, the hard wire on VLAN A works, but the WiFi on VLAN A doesn't.
There are no static routes (other than what the pfsense creates by default when making the firewall rules). They are not necessary for the packets to land where they are supposed to (as demonstrated by the hard-wire test).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
