Access point NWA210BE configuration
Freshman Member
I have installed 13 NWA210BE access points on a network using Zyxel XGS1935-28HP PoE switches.
The configuration is very basic: two SSIDs on VLAN 1 (the default), with the switch ports to which the APs are connected configured as "Untagged 1" and "Tagged ALL." For the time being, I have no SSIDs associated with any other VLANs. Everything works fine during startup; the APs successfully obtain an IP address via DHCP on VLAN 1. However, I need to move the AP management to my OAM VLAN 255—a process I have successfully carried out with APs from other brands in the past.
Once an access point receives its new IP address on VLAN 255, the SSIDs on VLAN 1 appear to stop passing any traffic; clients are unable to obtain an IP address via DHCP.
As a temporary workaround, I have reverted the APs to using DHCP on VLAN 1.
What could be causing this behavior?
Thank you.
Accepted Solution
-
Hi @Edoardo_PCCenter ,
The reason wireless clients fail to get an IP address when connecting to the VLAN 1 SSID is a misconfigured VLAN tag.
By default, the AP (like all other network devices) uses VLAN 1 as its management VLAN, and VLAN 1 traffic is untagged (the general default setting). Traffic in other VLANs must be tagged with the corresponding VLAN ID, so that each device can process the VLAN traffic correctly.
When you change the AP’s management VLAN to VLAN 255, it means the AP uses VLAN 255 as its management VLAN. So, the AP can only process traffic from the VLAN 1 SSID (wireless network) and the Ethernet side correctly if VLAN 1 traffic is tagged with ID 1 from the switch to the AP.
Solution:
Set the switch ports that connect to the AP to tag VLAN 1 on egress. On the XGS1935-28HP:- Go to SWITCHING > VLAN > VLAN Setup > Static VLAN.
- Select VID = 1.
- Set the ports where the AP connects to Tx Tagging.
Zyxel_Judy
0
All Replies
-
Hi @Edoardo_PCCenter ,
The reason wireless clients fail to get an IP address when connecting to the VLAN 1 SSID is a misconfigured VLAN tag.
By default, the AP (like all other network devices) uses VLAN 1 as its management VLAN, and VLAN 1 traffic is untagged (the general default setting). Traffic in other VLANs must be tagged with the corresponding VLAN ID, so that each device can process the VLAN traffic correctly.
When you change the AP’s management VLAN to VLAN 255, it means the AP uses VLAN 255 as its management VLAN. So, the AP can only process traffic from the VLAN 1 SSID (wireless network) and the Ethernet side correctly if VLAN 1 traffic is tagged with ID 1 from the switch to the AP.
Solution:
Set the switch ports that connect to the AP to tag VLAN 1 on egress. On the XGS1935-28HP:- Go to SWITCHING > VLAN > VLAN Setup > Static VLAN.
- Select VID = 1.
- Set the ports where the AP connects to Tx Tagging.
Zyxel_Judy
0 -
One detail I didn’t mention above, which might be important: the access point management configuration must be TAGGED on VLAN 255. The switch port allows this VLAN to pass through, and the access point successfully receives an IP address when configured for DHCP on VLAN 255 (tagged).
Does the solution mentioned above still hold true? I also need to keep an SSID on VLAN 1 (untagged). I’m wondering which VLAN should be set as "untagged" on the switch port—should it still be VLAN 1, using the settings provided in your previous response? Thanks again.0 -
Hi @Edoardo_PCCenter ,
Yes, we also assumed your VLAN 255 would be tagged, so the solution above still applies to your scenario.
With your current setup — where both VLAN 255 (management) and VLAN 1 (SSID) are sent tagged by the AP — VLAN 1 needs to be configured as tagged on the switch port as well (same as VLAN 255). You don’t need to keep any VLAN as untagged on that port in this case, since the AP is no longer sending any untagged traffic.
Zyxel_Judy
0
Categories
- All Categories
- 442 Beta Program
- 3.1K Nebula
- 243 Nebula Ideas
- 6.8K Security
- 783 USG FLEX H Series
- 389 Security Ideas
- 1.8K Switch
- 87 Switch Ideas
- 1.5K Wireless
- 58 Wireless Ideas
- 7.2K Consumer Product
- 325 Service & License
- 527 News and Release
- 101 Security Advisories
- 31 Education Center
- 10 [Campaign] Zyxel Network Detective
- 5.3K FAQ
- 34 Documents
- 91 About Community
- 122 Security Highlight
Zyxel Employee