converting LWAPP AP to bridge mode breaks joining controller

Unanswered Question
May 17th, 2009

I ran into this a few weeks back as I was trying to get some demo depot gear working for a POC. basically all of the 1131 AP's would not join the controller and I got these errors

May 17 20:45:42.471: %LWAPP-3-RADIUS_ERR: spam_radius.c:108 Could not send join reply, AP authorization failed; AP:00:1d:70:9a:94:90

*May 17 20:45:30.714: %LWAPP-3-RADIUS_ERR: spam_radius.c:108 Could not send join reply, AP authorization failed; AP:00:1d:70:9a:94:90

I tried playing with a lot of things thought it was a certificate issue on the AP's really couldn't figure it out. I had to convert the AP to autonomous and then back to LWAPP for it to work. Now by putting it into bridge mode for mesh support its doing the same thing. Thoughts

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
naks Tue, 05/19/2009 - 05:55

Hi,

For bridge ap to join to the WLC, you should add the ap's MAC address to the WLC MAC filters. You can add the AP's MAC either through the command line interface or the web interface of the WLC. In your case, execute the following command on the WLC:

config mac-filter add

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