<?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: 'authentication control-direction in' in authentication CLOSED mode in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/authentication-control-direction-in-in-authentication-closed/m-p/4104485#M561264</link>
    <description>&lt;P&gt;Neither ISE or Switch are the root cause of the issue. This is the behavior of some hosts (Printers, Cameras, PCs, ...) that will go into sleeping mode and they need a WoL magic packet from the switch to wake up, so &lt;STRONG&gt;&lt;SPAN style="left: 595.901px; top: 263.695px; font-size: 16.6px; font-family: serif; transform: scaleX(1.12996);"&gt;authentication control-direction&lt;/SPAN&gt; in&lt;/STRONG&gt; can help in such scenarios.&lt;/P&gt;</description>
    <pubDate>Tue, 16 Jun 2020 22:12:56 GMT</pubDate>
    <dc:creator>Romzy</dc:creator>
    <dc:date>2020-06-16T22:12:56Z</dc:date>
    <item>
      <title>'authentication control-direction in' in authentication CLOSED mode</title>
      <link>https://community.cisco.com/t5/network-access-control/authentication-control-direction-in-in-authentication-closed/m-p/2652377#M55998</link>
      <description>&lt;P&gt;Switch: 4510R+E, running a DEV version based off 3.6.0&lt;/P&gt;&lt;P&gt;ISE: 1.2.0.899 patch 7&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hi, I have been working on a weird issue where some of my clients would randomly drop their IP address and the only way I could get it back was to move their port to authentication open mode. I need to run in closed mode because I change VLANs via MAB.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have been working with TAC, and they suggested I add the command 'authentication control-direction in' to my switchport config (below). With the couple tests Ive done, this seems to help. But I would like to understand why. Doesn't the control-direction command somewhat nullify the premise of running in closed mode? I.E. It allows some communication before the device is authorized. Thanks.&lt;/P&gt;&lt;P&gt;interface GigabitEthernet2/18&lt;BR /&gt;&amp;nbsp;switchport access vlan 34&lt;BR /&gt;&amp;nbsp;switchport mode access&lt;BR /&gt;&amp;nbsp;switchport voice vlan 66&lt;BR /&gt;&amp;nbsp;logging event link-status&lt;BR /&gt;&amp;nbsp;authentication event fail action next-method&lt;BR /&gt;&amp;nbsp;authentication event server dead action authorize vlan 34&lt;BR /&gt;&amp;nbsp;authentication event server dead action authorize voice&lt;BR /&gt;&amp;nbsp;authentication event server alive action reinitialize&amp;nbsp;&lt;BR /&gt;&amp;nbsp;authentication host-mode multi-auth&lt;BR /&gt;&amp;nbsp;authentication order mab dot1x&lt;BR /&gt;&amp;nbsp;authentication priority dot1x mab&lt;BR /&gt;&amp;nbsp;authentication port-control auto&lt;BR /&gt;&amp;nbsp;authentication violation restrict&lt;BR /&gt;&amp;nbsp;mab&lt;BR /&gt;&amp;nbsp;dot1x pae authenticator&lt;BR /&gt;&amp;nbsp;dot1x timeout tx-period 10&lt;BR /&gt;&amp;nbsp;service-policy input QoS-Input-Policy&lt;BR /&gt;&amp;nbsp;service-policy output QoS-Host-Port-Output-Policy&lt;BR /&gt;end&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 05:38:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authentication-control-direction-in-in-authentication-closed/m-p/2652377#M55998</guid>
      <dc:creator>Josh Morris</dc:creator>
      <dc:date>2019-03-11T05:38:40Z</dc:date>
    </item>
    <item>
      <title>Add this line to the DACL. it</title>
      <link>https://community.cisco.com/t5/network-access-control/authentication-control-direction-in-in-authentication-closed/m-p/2652378#M56001</link>
      <description>&lt;P&gt;Add this line to the DACL. it will resolve it.&lt;/P&gt;&lt;P&gt;permit udp any eq bootpc any eq bootps&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Apr 2015 16:35:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authentication-control-direction-in-in-authentication-closed/m-p/2652378#M56001</guid>
      <dc:creator>Dave Saunders</dc:creator>
      <dc:date>2015-04-15T16:35:44Z</dc:date>
    </item>
    <item>
      <title>Thanks Dave. I'm assuming you</title>
      <link>https://community.cisco.com/t5/network-access-control/authentication-control-direction-in-in-authentication-closed/m-p/2652379#M56002</link>
      <description>&lt;P&gt;Thanks Dave. I'm assuming you mean add this line to the Auth-Default-ACL that gets applied prior to authorization. IN the 4510, it already allows that traffic. Here is the default ACL...&lt;/P&gt;&lt;P&gt;Extended IP access list Auth-Default-ACL&lt;BR /&gt;&amp;nbsp; &amp;nbsp; 10 permit udp any any eq domain&lt;BR /&gt;&amp;nbsp; &amp;nbsp; 20 permit tcp any any eq domain&lt;BR /&gt;&amp;nbsp; &amp;nbsp; 30 permit udp any eq bootps any&lt;BR /&gt;&amp;nbsp; &amp;nbsp; 40 permit udp any any eq bootpc&lt;BR /&gt;&amp;nbsp; &amp;nbsp; 50 permit udp any eq bootpc any&lt;BR /&gt;&amp;nbsp; &amp;nbsp; 60 deny ip any any&lt;/P&gt;</description>
      <pubDate>Thu, 16 Apr 2015 12:18:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authentication-control-direction-in-in-authentication-closed/m-p/2652379#M56002</guid>
      <dc:creator>Josh Morris</dc:creator>
      <dc:date>2015-04-16T12:18:33Z</dc:date>
    </item>
    <item>
      <title>I also needed to use this</title>
      <link>https://community.cisco.com/t5/network-access-control/authentication-control-direction-in-in-authentication-closed/m-p/2652380#M56003</link>
      <description>&lt;P&gt;I also needed to use this command to keep devices authenticated. It was happening with a CCTV system that was an embedded Linux OS. It was on MAB and because it wasn't transmitting any traffic (unlike a noisy windows box) then the switch wouldn't be able to reauth it&amp;nbsp;as it had no mac address to be able to auth, so would show up with an 'unknown' in the MAC field.&lt;/P&gt;&lt;P&gt;Basically it allows traffic to flow out of the port. This enabled the device to be able to receive HTTP traffic and made it respond and then the switch could auth it again once the device&amp;nbsp;sent a frame.&lt;/P&gt;&lt;P&gt;when you do a&amp;nbsp;&lt;EM&gt;&lt;STRONG&gt;show authentication sessions&lt;/STRONG&gt;&lt;/EM&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;you will notice a&amp;nbsp;&lt;STRONG&gt;Oper control dir: both&lt;/STRONG&gt;&amp;nbsp;will change to&amp;nbsp;&lt;STRONG&gt;Oper control dir: in&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 16 Apr 2015 14:23:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authentication-control-direction-in-in-authentication-closed/m-p/2652380#M56003</guid>
      <dc:creator>phosawyer</dc:creator>
      <dc:date>2015-04-16T14:23:09Z</dc:date>
    </item>
    <item>
      <title>Re: 'authentication control-direction in' in authentication CLOSED mode</title>
      <link>https://community.cisco.com/t5/network-access-control/authentication-control-direction-in-in-authentication-closed/m-p/3192924#M56004</link>
      <description>&lt;P&gt;Hi I also have similar issue with MAB (authentication closed mode)&amp;nbsp;for one&amp;nbsp;legacy printer model (just sometimes).&lt;/P&gt;&lt;P&gt;- ISE 1.2, Cisco Switches (C3560, 2960X with IOS 12.2(55)SE7)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can it be ISE / IOS bug issue, if so, can help to share the Bug ID?&lt;/P&gt;&lt;P&gt;Please also suggest how to verify the default rule "Auth-Default-ACL".&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Tue, 03 Oct 2017 12:14:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authentication-control-direction-in-in-authentication-closed/m-p/3192924#M56004</guid>
      <dc:creator>yenaungoo</dc:creator>
      <dc:date>2017-10-03T12:14:39Z</dc:date>
    </item>
    <item>
      <title>Re: 'authentication control-direction in' in authentication CLOSED mode</title>
      <link>https://community.cisco.com/t5/network-access-control/authentication-control-direction-in-in-authentication-closed/m-p/4104485#M561264</link>
      <description>&lt;P&gt;Neither ISE or Switch are the root cause of the issue. This is the behavior of some hosts (Printers, Cameras, PCs, ...) that will go into sleeping mode and they need a WoL magic packet from the switch to wake up, so &lt;STRONG&gt;&lt;SPAN style="left: 595.901px; top: 263.695px; font-size: 16.6px; font-family: serif; transform: scaleX(1.12996);"&gt;authentication control-direction&lt;/SPAN&gt; in&lt;/STRONG&gt; can help in such scenarios.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jun 2020 22:12:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authentication-control-direction-in-in-authentication-closed/m-p/4104485#M561264</guid>
      <dc:creator>Romzy</dc:creator>
      <dc:date>2020-06-16T22:12:56Z</dc:date>
    </item>
  </channel>
</rss>

