<?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: AP350 Beaconing in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/ap350-beaconing/m-p/46772#M195331</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Under setup -&amp;gt; AP radio -&amp;gt; hardware  you can see a "Allow "broadcast" SSID to associate" yes/no radio button. Selecting no will disable broadcast SSID&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Turning off broadcast-SSID removes the SSID from the beacons (which are sent every 100ms by default), but the SSID is still visible in all probe-request/response frames (much less frequent, but **easily** sniffed by anyone with the intent to hack a WLAN).&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;My take is also that disabling broadcast-SSID is **not** a security precaution. SSID is the **NAME** of the WLAN. However, most WLAN security articles in the press mention turning broadcast-SSID off as part of a security policy (without really justifying how it makes the network any more secure).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are looking to make your wireless LAN more secure, you should look into LEAP, VPN or many of the other security solutions available.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 25 Sep 2002 01:57:44 GMT</pubDate>
    <dc:creator>bmcmurdo</dc:creator>
    <dc:date>2002-09-25T01:57:44Z</dc:date>
    <item>
      <title>AP350 Beaconing</title>
      <link>https://community.cisco.com/t5/wireless/ap350-beaconing/m-p/46771#M195330</link>
      <description>&lt;P&gt;How do I stop the AP350 from beaconing the SSID?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Dan Laden&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 06:25:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap350-beaconing/m-p/46771#M195330</guid>
      <dc:creator>dladen</dc:creator>
      <dc:date>2021-07-05T06:25:18Z</dc:date>
    </item>
    <item>
      <title>Re: AP350 Beaconing</title>
      <link>https://community.cisco.com/t5/wireless/ap350-beaconing/m-p/46772#M195331</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Under setup -&amp;gt; AP radio -&amp;gt; hardware  you can see a "Allow "broadcast" SSID to associate" yes/no radio button. Selecting no will disable broadcast SSID&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Turning off broadcast-SSID removes the SSID from the beacons (which are sent every 100ms by default), but the SSID is still visible in all probe-request/response frames (much less frequent, but **easily** sniffed by anyone with the intent to hack a WLAN).&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;My take is also that disabling broadcast-SSID is **not** a security precaution. SSID is the **NAME** of the WLAN. However, most WLAN security articles in the press mention turning broadcast-SSID off as part of a security policy (without really justifying how it makes the network any more secure).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are looking to make your wireless LAN more secure, you should look into LEAP, VPN or many of the other security solutions available.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Sep 2002 01:57:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap350-beaconing/m-p/46772#M195331</guid>
      <dc:creator>bmcmurdo</dc:creator>
      <dc:date>2002-09-25T01:57:44Z</dc:date>
    </item>
    <item>
      <title>Re: AP350 Beaconing</title>
      <link>https://community.cisco.com/t5/wireless/ap350-beaconing/m-p/46773#M195332</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the info...I will try it late this week.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We currently use LEAP to enhance security but I did not want an idle AP to announce itself to the world.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, &lt;/P&gt;&lt;P&gt;Dan Laden&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Sep 2002 03:01:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap350-beaconing/m-p/46773#M195332</guid>
      <dc:creator>dladen</dc:creator>
      <dc:date>2002-09-25T03:01:18Z</dc:date>
    </item>
  </channel>
</rss>

