Vlan dot1q tag native causes problems with AP's

Unanswered Question
Jun 4th, 2007
User Badges:


Recent changes required me to enable "Vlan dot1q tag native" on our switch infrastructure, however, this has caused our AP's to lose connectivity. I have tried setting the native vlan on dot11radio0.xx and fastethernet0.xx to match the switch native vlan, but this doesn't work. Is there an easy solution to this problem?

I do have one switch running a trunk port configured below and the AP's work on this switch, but I would rather not have to redo all the other switches to match this configuration.


switchport trunk encapsulation dot1q

switchport trunk native vlan 999

switchport mode trunk

no ip address

mls qos trust dscp


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
gamccall Tue, 06/05/2007 - 07:59
User Badges:
  • Silver, 250 points or more


switchport trunk encapsulation dot1q

switchport trunk native vlan xxx

switchport mode trunk"

This is exactly the way I had all my AP's connected before converting to LWAPP.

You might try taking the "native" flag off of the native vlan interface on your AP. Since the AP is expecting native traffic to be untagged, that's probably the issue with the tag native command... the question is whether it'll let you have no native vlan.


This Discussion



Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode