<?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 wireless signals in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/block-wireless-signals/m-p/1072815#M29331</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is no surprise. Under FCC part 15 rules, you're not allowed to deliberately interfere with anyone else's use of unlicensed radio spectrum (even if they're on your property). Jamming and autocontainment have always been questionable as far as teh regulatory side goes.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 02 Dec 2008 21:38:06 GMT</pubDate>
    <dc:creator>gamccall</dc:creator>
    <dc:date>2008-12-02T21:38:06Z</dc:date>
    <item>
      <title>block wireless signals</title>
      <link>https://community.cisco.com/t5/wireless/block-wireless-signals/m-p/1072811#M29324</link>
      <description>&lt;P&gt;Hi to all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible that a WLC or a WCS can block the wireless signal of a network that is not the one that we have at a customer location, for example an Ad-Hoc between two computers or the wireless signal from a building that is next to mine??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jul 2021 23:50:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/block-wireless-signals/m-p/1072811#M29324</guid>
      <dc:creator>alfonso.cornejo</dc:creator>
      <dc:date>2021-07-03T23:50:45Z</dc:date>
    </item>
    <item>
      <title>Re: block wireless signals</title>
      <link>https://community.cisco.com/t5/wireless/block-wireless-signals/m-p/1072812#M29328</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, the WLCs support auto-containment of rogue APs (also ADHOCs).  The APs will spoof deauthentication frames whenever a client tries to associate to the rogue network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Enabling this is risky, since it can be difficult to tell what is actually a rogue network and what is a legitimate neighbor network.  If you auto-contain your neighbor, you are essentially launching a denial of service attack against them.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Dec 2008 17:38:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/block-wireless-signals/m-p/1072812#M29328</guid>
      <dc:creator>dziminski</dc:creator>
      <dc:date>2008-12-02T17:38:38Z</dc:date>
    </item>
    <item>
      <title>Re: block wireless signals</title>
      <link>https://community.cisco.com/t5/wireless/block-wireless-signals/m-p/1072813#M29329</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ziminski,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I see your point, but just for knowledge can you tell me where can I configure that?? I've been looking for it on the Cisco Wireless LAN Controller Configuration Guide 5.0 and the Cisco Wireless Control System Configuration Guide 5.0 but i can't find it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks alot!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Dec 2008 17:51:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/block-wireless-signals/m-p/1072813#M29329</guid>
      <dc:creator>alfonso.cornejo</dc:creator>
      <dc:date>2008-12-02T17:51:04Z</dc:date>
    </item>
    <item>
      <title>Re: block wireless signals</title>
      <link>https://community.cisco.com/t5/wireless/block-wireless-signals/m-p/1072814#M29330</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Cisco may have removed the feature due to the legal issues.  I don't see it in the GUI anymore either.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/tech/tk722/tk809/technologies_white_paper09186a0080722d8c.shtml#conclusion" target="_blank"&gt;http://www.cisco.com/en/US/tech/tk722/tk809/technologies_white_paper09186a0080722d8c.shtml#conclusion&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"Rogue detection is not bound by any regulations and no legal adherence is required for its operation. However, rogue containment usually introduces legal issues that can put the infrastructure provider in an uncomfortable position if left to operate automatically."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I never actually used it, but it was an option at one point.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Dec 2008 21:24:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/block-wireless-signals/m-p/1072814#M29330</guid>
      <dc:creator>dziminski</dc:creator>
      <dc:date>2008-12-02T21:24:56Z</dc:date>
    </item>
    <item>
      <title>Re: block wireless signals</title>
      <link>https://community.cisco.com/t5/wireless/block-wireless-signals/m-p/1072815#M29331</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is no surprise. Under FCC part 15 rules, you're not allowed to deliberately interfere with anyone else's use of unlicensed radio spectrum (even if they're on your property). Jamming and autocontainment have always been questionable as far as teh regulatory side goes.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Dec 2008 21:38:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/block-wireless-signals/m-p/1072815#M29331</guid>
      <dc:creator>gamccall</dc:creator>
      <dc:date>2008-12-02T21:38:06Z</dc:date>
    </item>
  </channel>
</rss>

