- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- AP 420 VLAN issue
Switches, Hubs, and Modems
1753821
Members
9060
Online
108805
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-17-2008 04:26 PM
тАО09-17-2008 04:26 PM
It should be pretty simple, I suppose. I have an AP420 with two VLAN's on the WLAN, one for guests and another for
staff (VLAN 2 and 100, respectively). The guests are buck naked with no authentication, the staff are WPA+TKIP
w/passphrase. The AP is at 2.2.3 as of this afternoon, and I can authenticate to both just fine.
Associated 'stations' are always logged as VLAN 0 for some reason, but I'm not convinced that's the issue.
The switch the AP is plugged into, a 2600-8PWR, has VLAN 2 and 100 tagged on the incoming port, which is what I assume needs to be done. However, this doesn't work, and no DHCP for the clients.
I feel like I'm missing something very simple!
staff (VLAN 2 and 100, respectively). The guests are buck naked with no authentication, the staff are WPA+TKIP
w/passphrase. The AP is at 2.2.3 as of this afternoon, and I can authenticate to both just fine.
Associated 'stations' are always logged as VLAN 0 for some reason, but I'm not convinced that's the issue.
The switch the AP is plugged into, a 2600-8PWR, has VLAN 2 and 100 tagged on the incoming port, which is what I assume needs to be done. However, this doesn't work, and no DHCP for the clients.
I feel like I'm missing something very simple!
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-17-2008 10:30 PM
тАО09-17-2008 10:30 PM
Solution
Quick cut and paste from the manual...
Most likely you haven't enabled VLAN support under the Administration tab.
Web: Enabling VLAN Support
The Management window on the Administration tab to configure VLAN support and set a management VLAN ID.
The web interface enables you to modify these parameters:
├в VLAN Enable: Sets the VLAN tagging support on the access point.
Changing the VLAN support forces a reboot.
├в ┬в Disable: The access point does not tag traffic passing to the wired network and ignores the VLAN tags on any received frames.
├в ┬в Static: Enables VLAN tagging. Clients are assigned to the default VLAN ID of the associated SSID interface. VLAN assignment from a RADIUS server is not allowed.
├в ┬в Dynamic: Enables VLAN tagging. VLAN IDs are assigned from a RADIUS server, if configured. Otherwise, clients are assigned to the default VLAN ID of the associated SSID interface.
Most likely you haven't enabled VLAN support under the Administration tab.
Web: Enabling VLAN Support
The Management window on the Administration tab to configure VLAN support and set a management VLAN ID.
The web interface enables you to modify these parameters:
├в VLAN Enable: Sets the VLAN tagging support on the access point.
Changing the VLAN support forces a reboot.
├в ┬в Disable: The access point does not tag traffic passing to the wired network and ignores the VLAN tags on any received frames.
├в ┬в Static: Enables VLAN tagging. Clients are assigned to the default VLAN ID of the associated SSID interface. VLAN assignment from a RADIUS server is not allowed.
├в ┬в Dynamic: Enables VLAN tagging. VLAN IDs are assigned from a RADIUS server, if configured. Otherwise, clients are assigned to the default VLAN ID of the associated SSID interface.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-18-2008 12:47 PM
тАО09-18-2008 12:47 PM
Re: AP 420 VLAN issue
Hi Matt,
DOH. Yep, that certainly was a problem.
The next problem is the routing on the switch, which I have intentionally disabled. It looks like I have to reconfigure all the switches, since everything is running in the default VLAN, and not in the wi-fi VLAN.
Thanks. It certainly was simple!
DOH. Yep, that certainly was a problem.
The next problem is the routing on the switch, which I have intentionally disabled. It looks like I have to reconfigure all the switches, since everything is running in the default VLAN, and not in the wi-fi VLAN.
Thanks. It certainly was simple!
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP