<?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: Catalyst 9800 vWLC ACL in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/catalyst-9800-vwlc-acl/m-p/4789185#M252754</link>
    <description>&lt;P&gt;Yes, you need one ACE for everything that you want to allow and deny.&lt;/P&gt;</description>
    <pubDate>Wed, 08 Mar 2023 05:28:25 GMT</pubDate>
    <dc:creator>Karsten Iwen</dc:creator>
    <dc:date>2023-03-08T05:28:25Z</dc:date>
    <item>
      <title>Catalyst 9800 vWLC ACL</title>
      <link>https://community.cisco.com/t5/wireless/catalyst-9800-vwlc-acl/m-p/4787002#M252601</link>
      <description>&lt;P&gt;I'm trying to configure an ACL on Catalyst 9800 vWLC GUI but I can't figure out why there isnt'a a 'any' option for ports and protocols in extended ACLs? Default value for protocol field is adp and for source or destination port is None. Will None work instead any and how I can set the protocol to any? Maybe is there a image bug? I'm using 17.6.4 right now&lt;/P&gt;</description>
      <pubDate>Sat, 04 Mar 2023 10:14:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/catalyst-9800-vwlc-acl/m-p/4787002#M252601</guid>
      <dc:creator>filip.nikolic</dc:creator>
      <dc:date>2023-03-04T10:14:21Z</dc:date>
    </item>
    <item>
      <title>Re: Catalyst 9800 vWLC ACL</title>
      <link>https://community.cisco.com/t5/wireless/catalyst-9800-vwlc-acl/m-p/4787012#M252605</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;-&amp;nbsp; A possible way to go forward is to examine the running config after you define an (extended) ACL in the GUI ; (t)(w)hen reviewing the resulting&amp;nbsp; ACL statements in the running config and 'staying' on the CLI you might be able to achieve what you want&amp;nbsp; and or check if you can include option&lt;STRONG&gt; 'any'&lt;/STRONG&gt; when defining or completing an ACL through querying command completion with&lt;U&gt;&lt;FONT color="#008000"&gt;&lt;STRONG&gt; ?&lt;/STRONG&gt; &lt;/FONT&gt;&lt;/U&gt;(e.g.)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Sat, 04 Mar 2023 10:55:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/catalyst-9800-vwlc-acl/m-p/4787012#M252605</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2023-03-04T10:55:07Z</dc:date>
    </item>
    <item>
      <title>Re: Catalyst 9800 vWLC ACL</title>
      <link>https://community.cisco.com/t5/wireless/catalyst-9800-vwlc-acl/m-p/4787059#M252623</link>
      <description>&lt;P&gt;I must admit I had *never* looked at ACLs in the GUI before now!&lt;/P&gt;
&lt;P&gt;But now I have and it looks normal to me. Configuration -&amp;gt; Security -&amp;gt; ACL&lt;BR /&gt;There's all the normal options there.&amp;nbsp; I see "ahp" (not adp) at the top of the protocol list.&amp;nbsp; If you're not seeing the full list on the drop-down then that's probably a browser problem.&amp;nbsp; Try different browsers, different version of browser and make sure you're not blocking cookies etc.&amp;nbsp; It sometimes also helps to clear all cookies and history then close and re-start your browser.&amp;nbsp; Personally I'd recommend CLI for ACLs.&lt;/P&gt;</description>
      <pubDate>Sat, 04 Mar 2023 14:43:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/catalyst-9800-vwlc-acl/m-p/4787059#M252623</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2023-03-04T14:43:01Z</dc:date>
    </item>
    <item>
      <title>Re: Catalyst 9800 vWLC ACL</title>
      <link>https://community.cisco.com/t5/wireless/catalyst-9800-vwlc-acl/m-p/4787070#M252626</link>
      <description>&lt;P&gt;You need to choose "ip" as the protocol. This implies any ip based protocols and also all ports for udp/tcp:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="KarstenIwen_0-1677946138690.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/178071iEB8C353F6352827C/image-size/medium?v=v2&amp;amp;px=400" role="button" title="KarstenIwen_0-1677946138690.png" alt="KarstenIwen_0-1677946138690.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 04 Mar 2023 16:09:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/catalyst-9800-vwlc-acl/m-p/4787070#M252626</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2023-03-04T16:09:09Z</dc:date>
    </item>
    <item>
      <title>Re: Catalyst 9800 vWLC ACL</title>
      <link>https://community.cisco.com/t5/wireless/catalyst-9800-vwlc-acl/m-p/4789006#M252751</link>
      <description>&lt;P&gt;Thank you but if I choose ip as a destination protocol how should I block lets say ICMP? Should I create a new ACE just for ICMP?&lt;/P&gt;</description>
      <pubDate>Tue, 07 Mar 2023 22:51:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/catalyst-9800-vwlc-acl/m-p/4789006#M252751</guid>
      <dc:creator>filip.nikolic</dc:creator>
      <dc:date>2023-03-07T22:51:18Z</dc:date>
    </item>
    <item>
      <title>Re: Catalyst 9800 vWLC ACL</title>
      <link>https://community.cisco.com/t5/wireless/catalyst-9800-vwlc-acl/m-p/4789185#M252754</link>
      <description>&lt;P&gt;Yes, you need one ACE for everything that you want to allow and deny.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2023 05:28:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/catalyst-9800-vwlc-acl/m-p/4789185#M252754</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2023-03-08T05:28:25Z</dc:date>
    </item>
    <item>
      <title>Re: Catalyst 9800 vWLC ACL</title>
      <link>https://community.cisco.com/t5/wireless/catalyst-9800-vwlc-acl/m-p/4789426#M252772</link>
      <description>&lt;P&gt;Yes - it sounds like you need to familiarise yourself with the basics of ACLs:&lt;BR /&gt;&lt;A href="https://community.cisco.com/t5/networking-knowledge-base/access-control-lists-acl-explained/ta-p/4182349" target="_blank"&gt;https://community.cisco.com/t5/networking-knowledge-base/access-control-lists-acl-explained/ta-p/4182349&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_data_acl/configuration/xe-16-9/sec-data-acl-xe-16-9-book/sec-access-list-ov.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_data_acl/configuration/xe-16-9/sec-data-acl-xe-16-9-book/sec-access-list-ov.html&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_data_acl/configuration/xe-16-9/sec-data-acl-xe-16-9-book/sec-access-list-ov.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/ios-firewall/23602-confaccesslists.html&lt;BR /&gt;&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2023 10:31:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/catalyst-9800-vwlc-acl/m-p/4789426#M252772</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2023-03-08T10:31:06Z</dc:date>
    </item>
  </channel>
</rss>

