<?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 Re: WLC 3504 and NAT Address Setting in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wlc-3504-and-nat-address-setting/m-p/4033673#M169514</link>
    <description>&lt;P&gt;Hi Jay,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for the reply. I will try that and test it out. Cheers.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 13:28:40 GMT</pubDate>
    <dc:creator>hamilton-i</dc:creator>
    <dc:date>2020-02-21T13:28:40Z</dc:date>
    <item>
      <title>WLC 3504 and NAT Address Setting</title>
      <link>https://community.cisco.com/t5/wireless/wlc-3504-and-nat-address-setting/m-p/4032475#M169512</link>
      <description>&lt;P&gt;I have a WLC 3504, with connecting AP2802 &amp;amp; OEAP1810 access points. The office based AP2802 connect to the WLC fine but the external OEAP1810 will not connect. After doing some research I found that the NAT address had to be set on the WLC management interface. Once the NAT is addedd the OEAP1810 connects fine. But this has caused another issue where if I try and add a new AP2802 or if an existing AP2802 resets, both will not connect to the WLC as they are trying to contact the NAT address rather than the LAN Interface address. Removing the NAT address then resolves the issue and the AP2802's will connect again but the OEAP1810 then drops from the WLC. I have carried out extensive research on this but can't find any resolution for it. Does anyone know how to get around this issue as it's really frustrating? Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 18:44:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-3504-and-nat-address-setting/m-p/4032475#M169512</guid>
      <dc:creator>hamilton-i</dc:creator>
      <dc:date>2021-07-05T18:44:29Z</dc:date>
    </item>
    <item>
      <title>Re: WLC 3504 and NAT Address Setting</title>
      <link>https://community.cisco.com/t5/wireless/wlc-3504-and-nat-address-setting/m-p/4033155#M169513</link>
      <description>&lt;P&gt;You need to use the command "config network ap-discovery nat-ip-only disable" so that the WLC will send both the NAT IP and the private IP in the CAPWAP discovery response.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Feb 2020 15:40:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-3504-and-nat-address-setting/m-p/4033155#M169513</guid>
      <dc:creator>Jay Vivas</dc:creator>
      <dc:date>2020-02-20T15:40:17Z</dc:date>
    </item>
    <item>
      <title>Re: WLC 3504 and NAT Address Setting</title>
      <link>https://community.cisco.com/t5/wireless/wlc-3504-and-nat-address-setting/m-p/4033673#M169514</link>
      <description>&lt;P&gt;Hi Jay,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for the reply. I will try that and test it out. Cheers.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 13:28:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-3504-and-nat-address-setting/m-p/4033673#M169514</guid>
      <dc:creator>hamilton-i</dc:creator>
      <dc:date>2020-02-21T13:28:40Z</dc:date>
    </item>
    <item>
      <title>Re: WLC 3504 and NAT Address Setting</title>
      <link>https://community.cisco.com/t5/wireless/wlc-3504-and-nat-address-setting/m-p/4034583#M169515</link>
      <description>&lt;P&gt;Worked perfectly. Thank you&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Feb 2020 10:16:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-3504-and-nat-address-setting/m-p/4034583#M169515</guid>
      <dc:creator>hamilton-i</dc:creator>
      <dc:date>2020-02-24T10:16:48Z</dc:date>
    </item>
  </channel>
</rss>

