<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic converting LWAPP AP to bridge mode breaks joining controller in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/converting-lwapp-ap-to-bridge-mode-breaks-joining-controller/m-p/1212041#M62751</link>
    <description>&lt;P&gt;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&lt;/P&gt;&lt;P&gt;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&lt;/P&gt;&lt;P&gt;*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&lt;/P&gt;&lt;P&gt;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&lt;/P&gt;</description>
    <pubDate>Sun, 04 Jul 2021 00:36:35 GMT</pubDate>
    <dc:creator>miwitte</dc:creator>
    <dc:date>2021-07-04T00:36:35Z</dc:date>
    <item>
      <title>converting LWAPP AP to bridge mode breaks joining controller</title>
      <link>https://community.cisco.com/t5/wireless/converting-lwapp-ap-to-bridge-mode-breaks-joining-controller/m-p/1212041#M62751</link>
      <description>&lt;P&gt;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&lt;/P&gt;&lt;P&gt;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&lt;/P&gt;&lt;P&gt;*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&lt;/P&gt;&lt;P&gt;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&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 00:36:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/converting-lwapp-ap-to-bridge-mode-breaks-joining-controller/m-p/1212041#M62751</guid>
      <dc:creator>miwitte</dc:creator>
      <dc:date>2021-07-04T00:36:35Z</dc:date>
    </item>
    <item>
      <title>Re: converting LWAPP AP to bridge mode breaks joining controller</title>
      <link>https://community.cisco.com/t5/wireless/converting-lwapp-ap-to-bridge-mode-breaks-joining-controller/m-p/1212042#M62752</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;config mac-filter add &lt;AP-MAC&gt; &lt;INTERFACE-ID&gt; &lt;WLAN-ID&gt; &lt;DESCRIPTION&gt;&lt;/DESCRIPTION&gt;&lt;/WLAN-ID&gt;&lt;/INTERFACE-ID&gt;&lt;/AP-MAC&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 May 2009 12:55:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/converting-lwapp-ap-to-bridge-mode-breaks-joining-controller/m-p/1212042#M62752</guid>
      <dc:creator>naks</dc:creator>
      <dc:date>2009-05-19T12:55:30Z</dc:date>
    </item>
  </channel>
</rss>

