<?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 Rogue AP in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/rogue-ap/m-p/5257349#M280671</link>
    <description>&lt;P&gt;In the WLC we can contain the Rouge AP, but how we can make sure our AP is not contained by neighbor WLC if the my AP located not to far with neighbor AP?&lt;/P&gt;</description>
    <pubDate>Thu, 06 Feb 2025 00:47:25 GMT</pubDate>
    <dc:creator>hs08</dc:creator>
    <dc:date>2025-02-06T00:47:25Z</dc:date>
    <item>
      <title>Rogue AP</title>
      <link>https://community.cisco.com/t5/wireless/rogue-ap/m-p/5257349#M280671</link>
      <description>&lt;P&gt;In the WLC we can contain the Rouge AP, but how we can make sure our AP is not contained by neighbor WLC if the my AP located not to far with neighbor AP?&lt;/P&gt;</description>
      <pubDate>Thu, 06 Feb 2025 00:47:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rogue-ap/m-p/5257349#M280671</guid>
      <dc:creator>hs08</dc:creator>
      <dc:date>2025-02-06T00:47:25Z</dc:date>
    </item>
    <item>
      <title>Re: Rogue AP</title>
      <link>https://community.cisco.com/t5/wireless/rogue-ap/m-p/5257356#M280672</link>
      <description>&lt;P&gt;To start off containment is technically illegal in most countries, unless the rogue is connected to your network or broadcasting your SSID to be malicious.&lt;/P&gt;
&lt;P&gt;You would see aWIPS events of Deauthentication Flood, but you need Catalyst Center for aWIPS. That being said you would see clients being dropped from your network as containment will send clients connecting to it deauthentication frames.&lt;/P&gt;
&lt;P&gt;Easiest way to protect is to run MFP as mandatory&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-5/config-guide/b_wl_17_5_cg/m_awips.html" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-5/config-guide/b_wl_17_5_cg/m_awips.html&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Feb 2025 01:25:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rogue-ap/m-p/5257356#M280672</guid>
      <dc:creator>Haydn Andrews</dc:creator>
      <dc:date>2025-02-06T01:25:48Z</dc:date>
    </item>
    <item>
      <title>Re: Rogue AP</title>
      <link>https://community.cisco.com/t5/wireless/rogue-ap/m-p/5272551#M281705</link>
      <description>&lt;P&gt;&amp;gt;&amp;nbsp;&lt;SPAN&gt;how we can make sure our AP is not contained by neighbor WLC&lt;/SPAN&gt;&lt;BR /&gt;You cannot control how the other WLC is configured, but if they break the law (illegal containment) you can report them to the regulator for regulatory enforcement (but a friendly chat with your neighbours might be the better option).&amp;nbsp; But like&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/332987"&gt;@Haydn Andrews&lt;/a&gt;&amp;nbsp;says using MFP ensures that spoof de-auth frames (which is how containment is done) cannot be used.&lt;BR /&gt;&lt;A href="https://en.wikipedia.org/wiki/IEEE_802.11w-2009" target="_blank" rel="noopener"&gt;https://en.wikipedia.org/wiki/IEEE_802.11w-2009&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://techsearch.watchguard.com/KB?type=Article&amp;amp;SFDCID=kA10H000000bqRZSAY&amp;amp;lang=en_US" target="_blank" rel="noopener"&gt;https://techsearch.watchguard.com/KB?type=Article&amp;amp;SFDCID=kA10H000000bqRZSAY&amp;amp;lang=en_US&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Mar 2025 14:50:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rogue-ap/m-p/5272551#M281705</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2025-03-18T14:50:37Z</dc:date>
    </item>
  </channel>
</rss>

