H-REAP with Multiple WLANs

Answered Question
Mar 2nd, 2010

I have a quest

ion regarding Multiple WLANs ssids? We have 2 Wlan's for client1 & client2. AP's are setup for HREAP doing local switching for both ssids. Question is I can Authenticate to client1 but can't authenticate to client2 both ssids are running at hearquarters without a problem. Each ssid has a subnet. The mapping vlan is setup & each wlan is setup for a different vlan. I can setup a wired connect for client2 and pull IP. I now DHCP is working for client2. We have booted the APs and no change. Does the controller require a reboot for the second ssid to work? Also we are running 4.2 and are trunking the ports. Any help would be great.

I have this problem too.
0 votes
Correct Answer by Scott Fella about 6 years 9 months ago

If you haven't yet..... I would try to map the ssid to a different existing vlan on the local subnet to see if you are associating and authenticating okay or even to the client 1 ssid.  If that works then the only issue can be the trunk port configuration or spanning tree not passing that vlan.  If you did connect a wired client to a switchport on the same switch that h-reap ap is on, then double check your trunk configuration... better yet, remove it and recreate the trunk.

Scott

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Scott Fella Wed, 03/03/2010 - 11:22

If you haven't yet..... I would try to map the ssid to a different existing vlan on the local subnet to see if you are associating and authenticating okay or even to the client 1 ssid.  If that works then the only issue can be the trunk port configuration or spanning tree not passing that vlan.  If you did connect a wired client to a switchport on the same switch that h-reap ap is on, then double check your trunk configuration... better yet, remove it and recreate the trunk.

Scott

Actions

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