<?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: Options for wireless access lists in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/options-for-wireless-access-lists/m-p/4012951#M454473</link>
    <description>&lt;P&gt;That is correct.&amp;nbsp; AFAIK, dACL's are not supported on the wireless side yet.&amp;nbsp; You have to create the named ACL's on the controller and then you can reference them by name in your ISE policies.&lt;/P&gt;</description>
    <pubDate>Thu, 16 Jan 2020 20:03:37 GMT</pubDate>
    <dc:creator>Colby LeMaire</dc:creator>
    <dc:date>2020-01-16T20:03:37Z</dc:date>
    <item>
      <title>Options for wireless access lists</title>
      <link>https://community.cisco.com/t5/network-access-control/options-for-wireless-access-lists/m-p/4012930#M454470</link>
      <description>&lt;P&gt;Hello Community,&amp;nbsp; Currently we are using&amp;nbsp;Airespace access lists in ISE and using local mode instead of centrally switched.&amp;nbsp; &amp;nbsp;Our cisco rep told us that we shouldn't use airespace access lists and these should be using dacls instead.&amp;nbsp;&amp;nbsp;&lt;SPAN&gt;Everything I have read for wireless, you should use airespace and dacls are for wired.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Is this not true?&amp;nbsp; Are there other ways to deploy access lists when using wireless locally switched?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank you!&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jan 2020 19:43:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/options-for-wireless-access-lists/m-p/4012930#M454470</guid>
      <dc:creator>chad.drier</dc:creator>
      <dc:date>2020-01-16T19:43:36Z</dc:date>
    </item>
    <item>
      <title>Re: Options for wireless access lists</title>
      <link>https://community.cisco.com/t5/network-access-control/options-for-wireless-access-lists/m-p/4012951#M454473</link>
      <description>&lt;P&gt;That is correct.&amp;nbsp; AFAIK, dACL's are not supported on the wireless side yet.&amp;nbsp; You have to create the named ACL's on the controller and then you can reference them by name in your ISE policies.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jan 2020 20:03:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/options-for-wireless-access-lists/m-p/4012951#M454473</guid>
      <dc:creator>Colby LeMaire</dc:creator>
      <dc:date>2020-01-16T20:03:37Z</dc:date>
    </item>
    <item>
      <title>Re: Options for wireless access lists</title>
      <link>https://community.cisco.com/t5/network-access-control/options-for-wireless-access-lists/m-p/4012972#M454475</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/624773"&gt;@Colby LeMaire&lt;/a&gt;&amp;nbsp;is right.&amp;nbsp; I have been going through deploying wireless in our enterprise over the last few weeks.&amp;nbsp; We have 5520 WLCs with ~45 APs.&amp;nbsp; On the WLC setup your ACLs under:Security-&amp;gt;Access Control Lists.&amp;nbsp; Then in the authz profile you intend to use reference them via airespace acl name.&amp;nbsp; Make sure on WLC side your AAA servers, override etc. are configured properly.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jan 2020 20:22:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/options-for-wireless-access-lists/m-p/4012972#M454475</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2020-01-16T20:22:02Z</dc:date>
    </item>
    <item>
      <title>Re: Options for wireless access lists</title>
      <link>https://community.cisco.com/t5/network-access-control/options-for-wireless-access-lists/m-p/4013021#M454477</link>
      <description>&lt;P&gt;While this is true for the 5500 series, it is entirely dependent on the WLC OS.&lt;/P&gt;
&lt;P&gt;The most widely deployed WLC models (5500, 2500, 3500) are built on the AireOS and would require Airespace ACLs, but some models are build on IOS-XE. The IOS-XE models like the 5700 series do support downloadable ACLs.&lt;/P&gt;
&lt;P&gt;The new Catalyst 9800 series WLCs are also built on IOS-XE and support the use of dACLs as shown in this &lt;A href="https://community.cisco.com/t5/security-documents/ise-and-catalyst-9800-series-integration-guide/ta-p/3753060" target="_self"&gt;ISE and Catalyst 9800 Series Integration Guide&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;Greg&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jan 2020 21:21:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/options-for-wireless-access-lists/m-p/4013021#M454477</guid>
      <dc:creator>Greg Gibbs</dc:creator>
      <dc:date>2020-01-16T21:21:20Z</dc:date>
    </item>
    <item>
      <title>Re: Options for wireless access lists</title>
      <link>https://community.cisco.com/t5/network-access-control/options-for-wireless-access-lists/m-p/4013508#M454479</link>
      <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/388087"&gt;@Greg Gibbs&lt;/a&gt;&amp;nbsp; for the great information.&amp;nbsp; &amp;nbsp;This makes a lot of sense because we are currently on the 2504/5508 but we will be migrating to the&amp;nbsp;&lt;SPAN&gt;Catalyst 9800 series WLCs.&amp;nbsp; Thank you!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jan 2020 15:06:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/options-for-wireless-access-lists/m-p/4013508#M454479</guid>
      <dc:creator>chad.drier</dc:creator>
      <dc:date>2020-01-17T15:06:59Z</dc:date>
    </item>
  </channel>
</rss>

