<?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: Block SSID of others controllers in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/block-ssid-of-others-controllers/m-p/3806170#M26694</link>
    <description>&lt;P&gt;We need our clients cant&amp;nbsp; connect to others SSID outside of our network. But we need a feature to do it with discretion and our clients can't notice.&lt;/P&gt;</description>
    <pubDate>Wed, 20 Feb 2019 19:38:24 GMT</pubDate>
    <dc:creator>Spinzon84</dc:creator>
    <dc:date>2019-02-20T19:38:24Z</dc:date>
    <item>
      <title>Block SSID of others controllers</title>
      <link>https://community.cisco.com/t5/wireless/block-ssid-of-others-controllers/m-p/3805977#M26691</link>
      <description>&lt;P&gt;Im trying to restrict or block others SSID from other controllers with my WC 2504, it is possible to do that? To make our clients not to see others SSID that are not configured on my WC?&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 16:53:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/block-ssid-of-others-controllers/m-p/3805977#M26691</guid>
      <dc:creator>Spinzon84</dc:creator>
      <dc:date>2021-07-05T16:53:49Z</dc:date>
    </item>
    <item>
      <title>Re: Block SSID of others controllers</title>
      <link>https://community.cisco.com/t5/wireless/block-ssid-of-others-controllers/m-p/3805989#M26692</link>
      <description>&lt;P&gt;yes and no....&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can't block the clients from seeing the SSID from the WLC.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The client are going to see any SSID that is in their area.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You could look into some RF film on windows to help restrict what they can see.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there an issue with your users connecting to incorrect SSIDs?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Steve&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Feb 2019 16:22:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/block-ssid-of-others-controllers/m-p/3805989#M26692</guid>
      <dc:creator>Stephen Rodriguez</dc:creator>
      <dc:date>2019-02-20T16:22:24Z</dc:date>
    </item>
    <item>
      <title>Re: Block SSID of others controllers</title>
      <link>https://community.cisco.com/t5/wireless/block-ssid-of-others-controllers/m-p/3805992#M26693</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;You cannot block other SSID, but you could jam the rogue AP by wireless controller. However, it may bring some LEGAL ISSUE that you should really think before act.&lt;BR /&gt;&lt;BR /&gt;If I were you, I would check the RSSI of the rogue AP to estimate whether it is installed within your facility or not. And try to locate it, and remove it. If it is not within your facility, you better ignore it if there is no impact to your users.&lt;BR /&gt;&lt;BR /&gt;Please refer to the previous community post: &lt;A href="https://community.cisco.com/t5/other-wireless-mobility-subjects/rogue-ap-question/td-p/1379392" target="_blank"&gt;https://community.cisco.com/t5/other-wireless-mobility-subjects/rogue-ap-question/td-p/1379392&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 20 Feb 2019 16:24:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/block-ssid-of-others-controllers/m-p/3805992#M26693</guid>
      <dc:creator>ngkin2010</dc:creator>
      <dc:date>2019-02-20T16:24:49Z</dc:date>
    </item>
    <item>
      <title>Re: Block SSID of others controllers</title>
      <link>https://community.cisco.com/t5/wireless/block-ssid-of-others-controllers/m-p/3806170#M26694</link>
      <description>&lt;P&gt;We need our clients cant&amp;nbsp; connect to others SSID outside of our network. But we need a feature to do it with discretion and our clients can't notice.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Feb 2019 19:38:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/block-ssid-of-others-controllers/m-p/3806170#M26694</guid>
      <dc:creator>Spinzon84</dc:creator>
      <dc:date>2019-02-20T19:38:24Z</dc:date>
    </item>
    <item>
      <title>Re: Block SSID of others controllers</title>
      <link>https://community.cisco.com/t5/wireless/block-ssid-of-others-controllers/m-p/3806259#M26695</link>
      <description>&lt;P&gt;The easier way if the clients are SOE based type clients might be to do this with the wireless suppliant on the device like Cisco Anyconnect Network Access Manager, where you can restrict what SSID they can connect to, if your corporate SSIDs are available. This might also be able to be done using group policies etc.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the other SSIDs are managed by your own infrastructure you could look at AP Groups and WLAN IDs above 16 and selectively where you advertise them, and AP power levels.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If they are from other companies SSIDs, as WiFi is an unlicensed spectrum your options are limited:&lt;/P&gt;
&lt;P&gt;There is a feature to contain rogue APs - this does have some LEGAL ramifications to it, as you are launching a DOS attack against their network. If the AP is physically inside your facility (your owned or rented space/ not the floor above or next door) you would be able to use this feature, but normally easier to just find the AP and turn it off.&lt;/P&gt;
&lt;P&gt;The other option would be RF film on the windows, however this has other issues, like attenuating cell/mobile service which could cause other issues/ complaints.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Feb 2019 21:36:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/block-ssid-of-others-controllers/m-p/3806259#M26695</guid>
      <dc:creator>Haydn Andrews</dc:creator>
      <dc:date>2019-02-20T21:36:17Z</dc:date>
    </item>
  </channel>
</rss>

