- play_arrow Get Started
- play_arrow Access Points
- Overview of Juniper APs
- Juniper AP Ports and Their Usage
- PoE Requirements for Juniper APs
- play_arrow AP Dashboard
- play_arrow Onboarding
- play_arrow Configuration
- Auto-Provision Device Names, Sites, and Device Profiles
- BLE Settings
- Configure Ethernet Settings in a Device Profile
- Configure IP Settings
- Wireless Mesh Network Configuration
- Enable RTLS Support
- Electronic Shelf Labels
- Enabling LEDs on the AP
- Configure an AP for Survey Mode
- Configure Your APs as IEEE 802.1X Supplicants
- Enable Local Status Page
- Revert AP Configuration Automatically
- play_arrow Device Profiles
- Monitor and Manage Access Points
- Access Point FAQ
- play_arrow Integrations
- play_arrow WLAN Guest Portal
- Compare WLAN Guest Portal Options
- Automatic Client VLAN Assignments
- play_arrow Custom Guest Portal
- Use an External Portal for Guest Access
- play_arrow Use an Identity Provider for Guest Access
- Authorize, Reauthorize, and Reconnect Guest Clients
- Troubleshoot a Guest Network That Doesn't Work
- FAQs: Guest Portal
- play_arrow Radio Management
- play_arrow Wireless SLEs
- play_arrow Troubleshooting
- Using SLEs for Troubleshooting
- Wi-Fi Reason Codes
- play_arrow Troubleshooting an Access Point
- Replace an AP
- Reset an AP to the Factory-Default Configuration
- Troubleshooting Wireless Issues
- Common Wi-Fi Issues
- Dynamic and Manual Packet Captures
- Steer Clients to the 5-GHz Band
- Bonjour and Bluetooth Devices
- LLDP-MED Power Negotiation
- Troubleshoot Your Integration with Aruba ClearPass
- Use Labels to Identify "Unknown" Applications
- play_arrow Technology Reference
Create a WxLAN Policy to Override Client VLANs
Support per site VLAN flexibility with Multi-Pre-Shared Key (mPSK) by creating WxLAN policies that override client VLANs.
Let's illustrate the value of this feature by looking at a common use case when implementing Multiple-PSK. In this scenario, Site A needs the flexibility to use VLAN A for PSK A and VLAN B for PSK B. Site X needs to use VLAN X for PSK A and VLAN Y for PSK B. You can create WxLAN policies to assign VLANs to clients based on the PSK user role. The WxLAN-driven VLANs override any other VLAN assignments on a client. For example, this policy would override a dynamic VLAN that was received from RADIUS.
You can use this feature in addition to the normal methods of assigning a user to a VLAN by policy such as through RADIUS AVPs (Tunnel-Private-GroupId or Airespace-Interface-Name) or VLAN attached to MPSK.
Requirements
APs must have firmware version 0.14.29091 or newer.
The VLANs must be configured either in the VLAN list in the WLAN settings, ETH0 port configuration, or Mist Tunnel.
To create a WxLAN policy to override client VLANs: