<?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 CWA on ISE and switches in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cwa-on-ise-and-switches/m-p/2341462#M135182</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Uros&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt; ACL is used to determine which traffic should be bridged by default from unauthenticated&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;endpoints onto the access VLAN. Since you should allow all access first and enforce policy later, you&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;should apply ACL-ALLOW to permit all traffic through the switch port. You have already created a&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;default ISE authorization to allow all traffic for now since we want complete visibility and not impact&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;the existing end user experience yet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;! An ACL must be configured to prepend dACLs from AAA server.&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;ip access-group ACL-ALLOW in&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;Note: &lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;"&lt;/STRONG&gt;Prior to software versions 12.2(55)SE on DSBU switches, a port ACL is required for dynamic ACLs&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;from a RADIUS AAA server to be applied. Failure to have a default ACL will result in assigned dACLs&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;being ignored by the switch. With 12.2(55)SE a default ACL will be automatically generated and&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;applied&lt;STRONG&gt;"&lt;/STRONG&gt;.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 22 Aug 2013 07:21:09 GMT</pubDate>
    <dc:creator>Muhammad Munir</dc:creator>
    <dc:date>2013-08-22T07:21:09Z</dc:date>
    <item>
      <title>CWA on ISE and switches</title>
      <link>https://community.cisco.com/t5/network-access-control/cwa-on-ise-and-switches/m-p/2341459#M135150</link>
      <description>&lt;P&gt;I was able to configure the CWA on the switch and Cisco ISE. It is working as expected. I followed the guide on the link bellow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/products/ps11640/products_configuration_example09186a0080ba6514.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/ps11640/products_configuration_example09186a0080ba6514.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I only have one question. I&lt;SPAN style="font-size: 10pt;"&gt; try to understand why ACL must be configured on the port on the switch. Guide uses ACL with name webauth which permit all traffic. If port is authorized it receives dACL from ISE, otherwise port is in unauthorize state and denies all traffic. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE style="font-size: 11px; overflow: auto; max-width: 650px; min-width: 400px; height: auto; color: #000000;"&gt;interface GigabitEthernet1/0/12&lt;BR /&gt;description ISE1 - dot1x clients - UCS Eth0&lt;BR /&gt;switchport access vlan 100&lt;BR /&gt;switchport mode access&lt;BR /&gt;ip access-group webauth in&lt;BR /&gt;authentication order mab&lt;BR /&gt;authentication priority mab&lt;BR /&gt;authentication port-control auto&lt;BR /&gt;mab&lt;BR /&gt;spanning-tree portfast&lt;BR /&gt;end&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE style="font-size: 11px; overflow: auto; max-width: 650px; min-width: 400px; height: auto; color: #000000;"&gt;ip access-list extended webauth&lt;BR /&gt;permit ip any any&lt;/PRE&gt;</description>
      <pubDate>Tue, 26 Mar 2019 00:30:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cwa-on-ise-and-switches/m-p/2341459#M135150</guid>
      <dc:creator>urosbajzelj</dc:creator>
      <dc:date>2019-03-26T00:30:54Z</dc:date>
    </item>
    <item>
      <title>CWA on ISE and switches</title>
      <link>https://community.cisco.com/t5/network-access-control/cwa-on-ise-and-switches/m-p/2341460#M135156</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I remember well, older IOS versions do not apply a dACL on port if there is none already configured (locally).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Aug 2013 05:27:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cwa-on-ise-and-switches/m-p/2341460#M135156</guid>
      <dc:creator>Octavian Szolga</dc:creator>
      <dc:date>2013-08-21T05:27:40Z</dc:date>
    </item>
    <item>
      <title>CWA on ISE and switches</title>
      <link>https://community.cisco.com/t5/network-access-control/cwa-on-ise-and-switches/m-p/2341461#M135168</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for the answer. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It must be this because I tested this solution with and without access-list on the port and the result was always the same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Aug 2013 05:41:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cwa-on-ise-and-switches/m-p/2341461#M135168</guid>
      <dc:creator>urosbajzelj</dc:creator>
      <dc:date>2013-08-21T05:41:31Z</dc:date>
    </item>
    <item>
      <title>CWA on ISE and switches</title>
      <link>https://community.cisco.com/t5/network-access-control/cwa-on-ise-and-switches/m-p/2341462#M135182</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Uros&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt; ACL is used to determine which traffic should be bridged by default from unauthenticated&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;endpoints onto the access VLAN. Since you should allow all access first and enforce policy later, you&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;should apply ACL-ALLOW to permit all traffic through the switch port. You have already created a&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;default ISE authorization to allow all traffic for now since we want complete visibility and not impact&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;the existing end user experience yet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;! An ACL must be configured to prepend dACLs from AAA server.&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;ip access-group ACL-ALLOW in&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;Note: &lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;"&lt;/STRONG&gt;Prior to software versions 12.2(55)SE on DSBU switches, a port ACL is required for dynamic ACLs&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;from a RADIUS AAA server to be applied. Failure to have a default ACL will result in assigned dACLs&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;being ignored by the switch. With 12.2(55)SE a default ACL will be automatically generated and&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;applied&lt;STRONG&gt;"&lt;/STRONG&gt;.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Aug 2013 07:21:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cwa-on-ise-and-switches/m-p/2341462#M135182</guid>
      <dc:creator>Muhammad Munir</dc:creator>
      <dc:date>2013-08-22T07:21:09Z</dc:date>
    </item>
    <item>
      <title>CWA on ISE and switches</title>
      <link>https://community.cisco.com/t5/network-access-control/cwa-on-ise-and-switches/m-p/2341463#M135194</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="margin-left: 1in; text-indent: 0.5in;"&gt;&lt;STRONG style="text-decoration: underline; "&gt;Why ACL must be configured on the port on the switch&lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;Question:&lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;I only have one question. I try to understand why ACL must be configured on the port on the switch. Guide uses ACL with name webauth which permit all traffic. If port is authorized it receives dACL from ISE, otherwise port is in unauthorize state and denies all traffic.&lt;SPAN style="text-decoration: underline;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;What is Web Authentication?&lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;Web authentication is opposed to local web authentication, which is the usual web authentication on the switch itself. In that system, upon dot1x/mab failure, the switch wills failover to the webauth profile and will redirect client traffic to a web page on the switch.&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;Role of ACL: &lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;The redirectACL sent back with the central webauth profile determines which traffic (HTT or HTTPS) is redirected to the ISE. The downloadable ACL allows you to define what traffic is allowed. You should typically allow for DNS, HTTP(S), and 8443 and deny the rest. Otherwise, the switch redirects HTTP traffic but allows other protocols.&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;&lt;STRONG&gt;Port ACLs &lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;Port ACLs are ACLs that are applied to Layer 2 interfaces on a switch. Port ACLs are supported only on physical interfaces and not on EtherChannel interfaces and can be applied only on interfaces in the inbound direction. These access lists are supported: &lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;•Standard IP access lists using source addresses &lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;•Extended IP access lists using source and destination addresses and optional protocol type information &lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;•MAC extended access lists using source and destination MAC addresses and optional protocol type information &lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;The switch examines ACLs associated with all inbound features configured on a given interface and permits or denies packet forwarding based on how the packet matches the entries in the ACL. In this way, ACLs control access to a network or to part of a network.&amp;nbsp; Figure is an example of using port ACLs to control access to a network when all workstations are in the same VLAN. ACLs applied at the Layer 2 input would allow Host A to access the Human Resources network, but prevent Host B from accessing the same network. Port ACLs can only be applied to Layer 2 interfaces in the inbound direction. &lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;Figure 31-1 Using ACLs to Control Traffic to a Network &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;When you apply a port ACL to a trunk port, the ACL filters traffic on all VLANs present on the trunk port. When you apply a port ACL to a port with voice VLAN, the ACL filters traffic on both data and voice VLANs. &lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;With port ACLs, you can filter IP traffic by using IP access lists and non-IP traffic by using MAC addresses. You can filter both IP and non-IP traffic on the same Layer 2 interface by applying both an IP access list and a MAC access list to the interface. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;For More information, please check&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; text-align: justify; line-height: normal;"&gt;&lt;A href="http://www.cisco.com/en/US/docs/switches/lan/catalyst2960/software/release/12.2_55_se/configuration/guide/swacl.html%23wp1715468"&gt;http://www.cisco.com/en/US/docs/switches/lan/catalyst2960/software/release/12.2_55_se/configuration/guide/swacl.html#wp1715468&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Aug 2013 10:52:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cwa-on-ise-and-switches/m-p/2341463#M135194</guid>
      <dc:creator>aqjaved</dc:creator>
      <dc:date>2013-08-22T10:52:20Z</dc:date>
    </item>
    <item>
      <title>CWA on ISE and switches</title>
      <link>https://community.cisco.com/t5/network-access-control/cwa-on-ise-and-switches/m-p/2341464#M135220</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Rated Munir and Aqeel answer. You must go through. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Aug 2013 04:15:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cwa-on-ise-and-switches/m-p/2341464#M135220</guid>
      <dc:creator>Ravi Singh</dc:creator>
      <dc:date>2013-08-27T04:15:55Z</dc:date>
    </item>
  </channel>
</rss>

