<?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 APs in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/rogue-aps/m-p/2199290#M14914</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.cisco.com/docs/DOC-30149"&gt;https://supportforums.cisco.com/docs/DOC-30149&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#Don't use different RF group if they're part of same Network, even if they're different network still different RF group will fetch no advantage.&lt;/P&gt;&lt;P&gt;#Different RF group means roaming not expected between these APs, is that the case here.&lt;/P&gt;&lt;P&gt;#Also, Mobility between those WLCs are not expected if RF group names are dissimilar between the WLCs. what's the mobility config here.&lt;/P&gt;&lt;P&gt;#If RF grouping enabled and they find each other as Rogues, There'll be an Management overhead of adding each other as Friendly, however detecting each other as Rogue is harmless until you decide to contain them with the rule that could include other neighbor APs who are really Rogues.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 20 May 2013 11:32:58 GMT</pubDate>
    <dc:creator>Saravanan Lakshmanan</dc:creator>
    <dc:date>2013-05-20T11:32:58Z</dc:date>
    <item>
      <title>Rogue APs</title>
      <link>https://community.cisco.com/t5/wireless/rogue-aps/m-p/2199284#M14908</link>
      <description>&lt;P&gt;Hi All, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a couple of question in regards to rogues and rf grouping.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does the controller count the rougues access points when calculating channels assignments in the network?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The current setup has each floor in a separate RF group, does the APs in a RF group consider another AP from a different RF group a foreign Access Point? also when it is beneficial to have each floor in a separate RF group?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you all&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 06:54:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rogue-aps/m-p/2199284#M14908</guid>
      <dc:creator>atefbmejri</dc:creator>
      <dc:date>2021-07-04T06:54:47Z</dc:date>
    </item>
    <item>
      <title>Re: Rogue APs</title>
      <link>https://community.cisco.com/t5/wireless/rogue-aps/m-p/2199285#M14909</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;Does the controller count the rougues access points when calculating channels assignments in the network?&lt;/PRE&gt;&lt;P&gt;Depends on the RSSI values.&amp;nbsp; If the RSSI is strong enough, then yes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;The current setup has each floor in a separate RF group, does the APs in a RF group consider another AP from a different RF group a foreign Access Point?&lt;/PRE&gt;&lt;P&gt;If the AP is the same WLC then the WLC won't see it as a "rogue".&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;also when it is beneficial to have each floor in a separate RF group?&lt;/PRE&gt;&lt;P&gt;Don't see any benefit.&amp;nbsp; I see alot of disadvantage when you "separate" each floor in an RF group. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Apr 2013 23:41:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rogue-aps/m-p/2199285#M14909</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2013-04-12T23:41:24Z</dc:date>
    </item>
    <item>
      <title>Re: Rogue APs</title>
      <link>https://community.cisco.com/t5/wireless/rogue-aps/m-p/2199286#M14910</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;A WLC on a mobility group may see APs joining other WLCs on same mobility group as rogue devices IF they are in different RF groups.&lt;/P&gt;&lt;P&gt;This depends on the AP authentication configuration. (security -&amp;gt; Wireless Protection Policies -&amp;gt; AP Authentication).&lt;/P&gt;&lt;P&gt;If the value is set to "None" then different RF groups do not matter. If the value is set to "AP Authentication" then if two APs are in two RF groups the WLC will probably raise the rogue flag.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The above was true before different RF groups on same WLC were possible.&lt;/P&gt;&lt;P&gt;I don't honestly know the behavior when two different&amp;nbsp; RF groups are configured on the same WLC. (You may try changing the AP Authentication config and feed us back ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Amjad&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: blue;"&gt;Rating useful replies is more useful than saying &lt;SPAN style="color: green;"&gt; "&lt;SPAN style="text-decoration: underline;"&gt;Thank you&lt;/SPAN&gt;"&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 13 Apr 2013 05:12:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rogue-aps/m-p/2199286#M14910</guid>
      <dc:creator>Amjad Abdullah</dc:creator>
      <dc:date>2013-04-13T05:12:18Z</dc:date>
    </item>
    <item>
      <title>Rogue APs</title>
      <link>https://community.cisco.com/t5/wireless/rogue-aps/m-p/2199287#M14911</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote" style="border-collapse: collapse; font-size: 12px; list-style: none; margin: 10px 20px; padding-left: 10px; quotes: none; overflow: auto; font-family: Arial, verdana, sans-serif;"&gt;Does the controller count the rougues access points when calculating channels assignments in the network?&lt;/BLOCKQUOTE&gt;&lt;P style="background-color: #f7fafb; border-collapse: collapse; font-size: 12px; list-style: none; font-family: Arial, verdana, sans-serif;"&gt;Depends on the RSSI values.&amp;nbsp; If the RSSI is strong enough, then yes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Would this be the same for microwaves that have a significant leackage into the coverage area? Would the controller take that into consideration when calculating channel assignments ?&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Apr 2013 19:22:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rogue-aps/m-p/2199287#M14911</guid>
      <dc:creator>atefbmejri</dc:creator>
      <dc:date>2013-04-22T19:22:44Z</dc:date>
    </item>
    <item>
      <title>Rogue APs</title>
      <link>https://community.cisco.com/t5/wireless/rogue-aps/m-p/2199288#M14912</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes that’s true, if the RSSi value is more,&amp;nbsp; then it will definitely affect the channel assignment. They will interfere with your channel and waste the resource&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Apr 2013 02:00:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rogue-aps/m-p/2199288#M14912</guid>
      <dc:creator>Saurav Lodh</dc:creator>
      <dc:date>2013-04-23T02:00:36Z</dc:date>
    </item>
    <item>
      <title>Rogue APs</title>
      <link>https://community.cisco.com/t5/wireless/rogue-aps/m-p/2199289#M14913</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So Static channel assigment is recomended? is there any documentation that support this ?&lt;/P&gt;&lt;P&gt;there well over 300 APs and static would be not pratical! unless assigne static channel to the APs arround the microwave areas, if so would the controller use the static assignments in channel calculation ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Apr 2013 02:40:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rogue-aps/m-p/2199289#M14913</guid>
      <dc:creator>atefbmejri</dc:creator>
      <dc:date>2013-04-23T02:40:57Z</dc:date>
    </item>
    <item>
      <title>Rogue APs</title>
      <link>https://community.cisco.com/t5/wireless/rogue-aps/m-p/2199290#M14914</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.cisco.com/docs/DOC-30149"&gt;https://supportforums.cisco.com/docs/DOC-30149&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#Don't use different RF group if they're part of same Network, even if they're different network still different RF group will fetch no advantage.&lt;/P&gt;&lt;P&gt;#Different RF group means roaming not expected between these APs, is that the case here.&lt;/P&gt;&lt;P&gt;#Also, Mobility between those WLCs are not expected if RF group names are dissimilar between the WLCs. what's the mobility config here.&lt;/P&gt;&lt;P&gt;#If RF grouping enabled and they find each other as Rogues, There'll be an Management overhead of adding each other as Friendly, however detecting each other as Rogue is harmless until you decide to contain them with the rule that could include other neighbor APs who are really Rogues.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 May 2013 11:32:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rogue-aps/m-p/2199290#M14914</guid>
      <dc:creator>Saravanan Lakshmanan</dc:creator>
      <dc:date>2013-05-20T11:32:58Z</dc:date>
    </item>
  </channel>
</rss>

