<?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: Reauthentication Timer in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/reauthentication-timer/m-p/3803934#M485128</link>
    <description>&lt;P&gt;I probably should have mentioned we are doing MAB authentication not dot1x&lt;/P&gt;</description>
    <pubDate>Mon, 18 Feb 2019 09:41:10 GMT</pubDate>
    <dc:creator>Jason Weids</dc:creator>
    <dc:date>2019-02-18T09:41:10Z</dc:date>
    <item>
      <title>Reauthentication Timer</title>
      <link>https://community.cisco.com/t5/network-access-control/reauthentication-timer/m-p/3802671#M485118</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Why do devices that are unknown or that have no authorization policy constantly try to reauth every minute? Surely once they have failed &amp;amp; denied access a few times then you don't want them constantly sending radius requests. Is there a way to change the reauth timer so it only reauth when the port transitions to "up connected"?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Jason&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Feb 2019 11:07:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/reauthentication-timer/m-p/3802671#M485118</guid>
      <dc:creator>Jason Weids</dc:creator>
      <dc:date>2019-02-15T11:07:05Z</dc:date>
    </item>
    <item>
      <title>Re: Reauthentication Timer</title>
      <link>https://community.cisco.com/t5/network-access-control/reauthentication-timer/m-p/3802745#M485124</link>
      <description>&lt;P&gt;Unless you are doing a complete whitelisted setup, you really shouldn't be denying access to the network.&amp;nbsp; Every device should have an authorization policy applied.&amp;nbsp; The default policy should be a Limited Access policy with a DACL applied to allow access to the PSNs and DNS.&amp;nbsp; DNS is there to allow redirection to a portal if you want.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Feb 2019 13:35:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/reauthentication-timer/m-p/3802745#M485124</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2019-02-15T13:35:37Z</dc:date>
    </item>
    <item>
      <title>Re: Reauthentication Timer</title>
      <link>https://community.cisco.com/t5/network-access-control/reauthentication-timer/m-p/3802750#M485125</link>
      <description>If you are not using an ISE authorization policy result that pushes reauthentication timer then the fallback will be whatever you have configured on the host port.&lt;BR /&gt;dot1x reauthentication&lt;BR /&gt;dot1x timeout reauth-period (seconds)&lt;BR /&gt;Those commands will enable periodic re-authentication and set the number of seconds between re-authentication attempts.&lt;BR /&gt;&lt;BR /&gt;HTH!</description>
      <pubDate>Fri, 15 Feb 2019 13:45:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/reauthentication-timer/m-p/3802750#M485125</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2019-02-15T13:45:06Z</dc:date>
    </item>
    <item>
      <title>Re: Reauthentication Timer</title>
      <link>https://community.cisco.com/t5/network-access-control/reauthentication-timer/m-p/3803364#M485126</link>
      <description>&lt;P&gt;I agree with&amp;nbsp;&lt;A href="https://community.cisco.com/t5/user/viewprofilepage/user-id/192011" target="_blank"&gt;paul&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Security/TrustSec_1-99/Dot1X_Deployment/Dot1x_Dep_Guide.html#wp387307" target="_blank"&gt;dot1x timeout quiet-period&lt;/A&gt;&amp;nbsp;seems what you asked for.&lt;/P&gt;</description>
      <pubDate>Sat, 16 Feb 2019 21:16:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/reauthentication-timer/m-p/3803364#M485126</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2019-02-16T21:16:49Z</dc:date>
    </item>
    <item>
      <title>Re: Reauthentication Timer</title>
      <link>https://community.cisco.com/t5/network-access-control/reauthentication-timer/m-p/3803932#M485127</link>
      <description>&lt;P&gt;We are whitelisting. Nothing should be allowed to connect to the wired network in our environment unless it is a "known/trusted" device. The devices we are seeing which are not authorised are filling our live radius logs &amp;amp; it is these I want to limit.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Feb 2019 09:37:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/reauthentication-timer/m-p/3803932#M485127</guid>
      <dc:creator>Jason Weids</dc:creator>
      <dc:date>2019-02-18T09:37:49Z</dc:date>
    </item>
    <item>
      <title>Re: Reauthentication Timer</title>
      <link>https://community.cisco.com/t5/network-access-control/reauthentication-timer/m-p/3803934#M485128</link>
      <description>&lt;P&gt;I probably should have mentioned we are doing MAB authentication not dot1x&lt;/P&gt;</description>
      <pubDate>Mon, 18 Feb 2019 09:41:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/reauthentication-timer/m-p/3803934#M485128</guid>
      <dc:creator>Jason Weids</dc:creator>
      <dc:date>2019-02-18T09:41:10Z</dc:date>
    </item>
    <item>
      <title>Re: Reauthentication Timer</title>
      <link>https://community.cisco.com/t5/network-access-control/reauthentication-timer/m-p/3803937#M485129</link>
      <description>&lt;P&gt;Can you do this with MAB authentication?&lt;/P&gt;</description>
      <pubDate>Mon, 18 Feb 2019 09:42:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/reauthentication-timer/m-p/3803937#M485129</guid>
      <dc:creator>Jason Weids</dc:creator>
      <dc:date>2019-02-18T09:42:52Z</dc:date>
    </item>
    <item>
      <title>Re: Reauthentication Timer</title>
      <link>https://community.cisco.com/t5/network-access-control/reauthentication-timer/m-p/3804074#M485130</link>
      <description>Even in a whitelisted setup I would still not deny as the last rule in the wired MAB policy set.  Allow the connection and put a DACL on to limit access to the ISE PSNs and maybe other security products to allow a device not whitelisted to be profiled/scanned to gather information about it.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 18 Feb 2019 13:36:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/reauthentication-timer/m-p/3804074#M485130</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2019-02-18T13:36:18Z</dc:date>
    </item>
    <item>
      <title>Re: Reauthentication Timer</title>
      <link>https://community.cisco.com/t5/network-access-control/reauthentication-timer/m-p/3812406#M485131</link>
      <description>&lt;P&gt;That really helpfull, That might be what you would do but in our environment we only allow authorised devices on the wired network.&lt;/P&gt;</description>
      <pubDate>Fri, 01 Mar 2019 10:24:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/reauthentication-timer/m-p/3812406#M485131</guid>
      <dc:creator>Jason Weids</dc:creator>
      <dc:date>2019-03-01T10:24:42Z</dc:date>
    </item>
  </channel>
</rss>

