<?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: why connection related to R1 rule hits VPN rule and vice versa , we still using ISE 2.1 in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/why-connection-related-to-r1-rule-hits-vpn-rule-and-vice-versa/m-p/3211220#M547527</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would use policy sets for each autentication type, e.g VPN, Wired 802.1x, Wired MAB etc. Use NAS IP address or Device Type as the condition on the policy set. For example, in doing so, Wired 802.1x authentications would never originate from the NAS IP address of the VPN device, therefore never process that VPN policy set.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Ultimately you need to make the rules more specific, using other conditions in the policy.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;</description>
    <pubDate>Sun, 05 Nov 2017 17:27:14 GMT</pubDate>
    <dc:creator>Rob Ingram</dc:creator>
    <dc:date>2017-11-05T17:27:14Z</dc:date>
    <item>
      <title>why connection related to R1 rule hits VPN rule and vice versa , we still using ISE 2.1</title>
      <link>https://community.cisco.com/t5/network-access-control/why-connection-related-to-r1-rule-hits-vpn-rule-and-vice-versa/m-p/3210624#M547521</link>
      <description>&lt;P&gt;Hello guys&lt;/P&gt;
&lt;P&gt;pls find attacment&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am confused , why connection related to &lt;STRONG&gt;R1 rule&lt;/STRONG&gt; hits &lt;STRONG&gt;VPN rule&lt;/STRONG&gt; and connection related to&lt;STRONG&gt; VPN Rule&lt;/STRONG&gt; hits&lt;STRONG&gt; R1 Rule&lt;/STRONG&gt; , we still using ISE 2.1&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;pls help me out&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:37:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/why-connection-related-to-r1-rule-hits-vpn-rule-and-vice-versa/m-p/3210624#M547521</guid>
      <dc:creator>Ibrahim Jamil</dc:creator>
      <dc:date>2020-02-21T18:37:57Z</dc:date>
    </item>
    <item>
      <title>Re: why connection related to R1 rule hits VPN rule and vice versa , we still using ISE 2.1</title>
      <link>https://community.cisco.com/t5/network-access-control/why-connection-related-to-r1-rule-hits-vpn-rule-and-vice-versa/m-p/3210644#M547523</link>
      <description>&lt;P&gt;The screenshot of the VPN rule implies there is an AND but there appears to be nothing there.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Add another condition to match against, to make the each of the rules more specific to the device making the connection. E.g Radius:NAS-Port-Type EQUALS Virtual &lt;STRONG&gt;AND&lt;/STRONG&gt; Radius:NAS-IP-Address EQUALS x.x.x.x&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You could also use Policy Sets and make the condition specifc to the type of connection etc.&lt;/P&gt;</description>
      <pubDate>Fri, 03 Nov 2017 19:42:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/why-connection-related-to-r1-rule-hits-vpn-rule-and-vice-versa/m-p/3210644#M547523</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2017-11-03T19:42:43Z</dc:date>
    </item>
    <item>
      <title>Re: why connection related to R1 rule hits VPN rule and vice versa , we still using ISE 2.1</title>
      <link>https://community.cisco.com/t5/network-access-control/why-connection-related-to-r1-rule-hits-vpn-rule-and-vice-versa/m-p/3211081#M547525</link>
      <description>&lt;P&gt;Hello RJI&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;in the Authentication policy do i need also NAS address , NAS is configured for the same rule but in the Authorization policy&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sun, 05 Nov 2017 04:13:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/why-connection-related-to-r1-rule-hits-vpn-rule-and-vice-versa/m-p/3211081#M547525</guid>
      <dc:creator>Ibrahim Jamil</dc:creator>
      <dc:date>2017-11-05T04:13:32Z</dc:date>
    </item>
    <item>
      <title>Re: why connection related to R1 rule hits VPN rule and vice versa , we still using ISE 2.1</title>
      <link>https://community.cisco.com/t5/network-access-control/why-connection-related-to-r1-rule-hits-vpn-rule-and-vice-versa/m-p/3211220#M547527</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would use policy sets for each autentication type, e.g VPN, Wired 802.1x, Wired MAB etc. Use NAS IP address or Device Type as the condition on the policy set. For example, in doing so, Wired 802.1x authentications would never originate from the NAS IP address of the VPN device, therefore never process that VPN policy set.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Ultimately you need to make the rules more specific, using other conditions in the policy.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;</description>
      <pubDate>Sun, 05 Nov 2017 17:27:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/why-connection-related-to-r1-rule-hits-vpn-rule-and-vice-versa/m-p/3211220#M547527</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2017-11-05T17:27:14Z</dc:date>
    </item>
    <item>
      <title>Re: why connection related to R1 rule hits VPN rule and vice versa , we still using ISE 2.1</title>
      <link>https://community.cisco.com/t5/network-access-control/why-connection-related-to-r1-rule-hits-vpn-rule-and-vice-versa/m-p/3211340#M547653</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;do u mean another NAS IP Address also for Authentication policy AND for Authorization policy ????&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Mon, 06 Nov 2017 05:43:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/why-connection-related-to-r1-rule-hits-vpn-rule-and-vice-versa/m-p/3211340#M547653</guid>
      <dc:creator>Ibrahim Jamil</dc:creator>
      <dc:date>2017-11-06T05:43:12Z</dc:date>
    </item>
    <item>
      <title>Re: why connection related to R1 rule hits VPN rule and vice versa , we still using ISE 2.1</title>
      <link>https://community.cisco.com/t5/network-access-control/why-connection-related-to-r1-rule-hits-vpn-rule-and-vice-versa/m-p/3211543#M547654</link>
      <description>&lt;P&gt;Yes, add a new condition to the authorisation rules to make them unique.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Nov 2017 12:51:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/why-connection-related-to-r1-rule-hits-vpn-rule-and-vice-versa/m-p/3211543#M547654</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2017-11-06T12:51:20Z</dc:date>
    </item>
  </channel>
</rss>

