<?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: WLAN Security in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wlan-security/m-p/371217#M22709</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Maybe apply a MAC-based ACL on the concentrating switch to allow only Cisco MACs (the MAC of the AP Ethernet interface)? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not sure (haven't tried it), but, worse case, setup an additiional VLAN (so you have a tag &amp;amp; trunk established), blackhole the Native VLAN, and I believe, the tagged frames from the AP can pass through the MAC-secured port. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many of the SOHO APs cannot authenticate against RADIUS. Also, the RADIUS server must be configured to accept authentication requests from specific requesters. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you're talking about someone plugging an AP into their PC jack, that's going to go back to creating a policy (the first step to any kind of security) - if a user gets caught, the user gets fired. If management can't accept implementing a policy like that, your company's problems are larger than a/some rogue access points (IMHO).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FWIW&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 04 Feb 2005 04:29:26 GMT</pubDate>
    <dc:creator>scottmac</dc:creator>
    <dc:date>2005-02-04T04:29:26Z</dc:date>
    <item>
      <title>WLAN Security</title>
      <link>https://community.cisco.com/t5/wireless/wlan-security/m-p/371216#M22708</link>
      <description>&lt;P&gt; HI,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; We are planning to introduce a big WLAN, with 1200 AP, we´ll work with them using a RADIUS Server and 802.1x, here all is Ok,  but the problem is that any user can connect its AP(Linksys, anything else), it is a big hole, we don´t want that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Do you know something that we can do ? to prevent it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks Luis.&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 17:25:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlan-security/m-p/371216#M22708</guid>
      <dc:creator>luis.veraza</dc:creator>
      <dc:date>2021-07-04T17:25:26Z</dc:date>
    </item>
    <item>
      <title>Re: WLAN Security</title>
      <link>https://community.cisco.com/t5/wireless/wlan-security/m-p/371217#M22709</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Maybe apply a MAC-based ACL on the concentrating switch to allow only Cisco MACs (the MAC of the AP Ethernet interface)? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not sure (haven't tried it), but, worse case, setup an additiional VLAN (so you have a tag &amp;amp; trunk established), blackhole the Native VLAN, and I believe, the tagged frames from the AP can pass through the MAC-secured port. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many of the SOHO APs cannot authenticate against RADIUS. Also, the RADIUS server must be configured to accept authentication requests from specific requesters. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you're talking about someone plugging an AP into their PC jack, that's going to go back to creating a policy (the first step to any kind of security) - if a user gets caught, the user gets fired. If management can't accept implementing a policy like that, your company's problems are larger than a/some rogue access points (IMHO).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FWIW&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Feb 2005 04:29:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlan-security/m-p/371217#M22709</guid>
      <dc:creator>scottmac</dc:creator>
      <dc:date>2005-02-04T04:29:26Z</dc:date>
    </item>
  </channel>
</rss>

