<?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: Use NAS-IP Address to look up network device in ISE instead of source address in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/use-nas-ip-address-to-look-up-network-device-in-ise-instead-of/m-p/3892319#M542528</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/523113"&gt;rmueller@cisco.com&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Nope - the NAS-IP-Address is not used in ISE's inbound RADIUS packet processing.&amp;nbsp; It's one of the reason's why Source NAT (SNAT) NAD breaks CoA, because ISE will never be able to perform the CoA to a device whose IP address has been source NAT'd.&amp;nbsp; ISE can send the CoA out, but the NAD's reply will be a SNAT'd UDP packet ... ISE will think the ACK never arrived.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Craig Hyps famously had a phrase "SNAT for NAD is bad - SNAT for CoA is OK" - but you have to understand the IP packet flow to know what that means.&lt;/P&gt;</description>
    <pubDate>Wed, 17 Jul 2019 23:42:37 GMT</pubDate>
    <dc:creator>Arne Bier</dc:creator>
    <dc:date>2019-07-17T23:42:37Z</dc:date>
    <item>
      <title>Use NAS-IP Address to look up network device in ISE instead of source address</title>
      <link>https://community.cisco.com/t5/network-access-control/use-nas-ip-address-to-look-up-network-device-in-ise-instead-of/m-p/3889270#M542473</link>
      <description>&lt;P dir="ltr"&gt;Hi all,&lt;/P&gt;
&lt;P dir="ltr"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P dir="ltr"&gt;to my knowledge, currently ISE uses per default the source ip address of the RADIUS-request&amp;nbsp;to look up the network device. This can cause issues if there are NAT-devices between the network access device and the ISE.&lt;/P&gt;
&lt;P dir="ltr"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P dir="ltr"&gt;Is there a known way to use the&amp;nbsp;&lt;SPAN&gt;NAS-IP address within the RADIUS-packet to look up the network device instead?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P dir="ltr"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P dir="ltr"&gt;&lt;SPAN&gt;Roland&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jul 2019 13:58:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/use-nas-ip-address-to-look-up-network-device-in-ise-instead-of/m-p/3889270#M542473</guid>
      <dc:creator>rmueller@cisco.com</dc:creator>
      <dc:date>2019-07-12T13:58:14Z</dc:date>
    </item>
    <item>
      <title>Re: Use NAS-IP Address to look up network device in ISE instead of source address</title>
      <link>https://community.cisco.com/t5/network-access-control/use-nas-ip-address-to-look-up-network-device-in-ise-instead-of/m-p/3889787#M542485</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;I believe you're talking about wired devices.&lt;BR /&gt;What devices' models are you using?&lt;BR /&gt;&lt;BR /&gt;Here a link that might help:&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_usr_radatt/configuration/xe-16/sec-usr-radatt-xe-16-book/sec-rad-nas-ip-cfg.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_usr_radatt/configuration/xe-16/sec-usr-radatt-xe-16-book/sec-rad-nas-ip-cfg.html&lt;/A&gt;</description>
      <pubDate>Sun, 14 Jul 2019 03:30:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/use-nas-ip-address-to-look-up-network-device-in-ise-instead-of/m-p/3889787#M542485</guid>
      <dc:creator>Francesco Molino</dc:creator>
      <dc:date>2019-07-14T03:30:37Z</dc:date>
    </item>
    <item>
      <title>Re: Use NAS-IP Address to look up network device in ISE instead of source address</title>
      <link>https://community.cisco.com/t5/network-access-control/use-nas-ip-address-to-look-up-network-device-in-ise-instead-of/m-p/3892319#M542528</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/523113"&gt;rmueller@cisco.com&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Nope - the NAS-IP-Address is not used in ISE's inbound RADIUS packet processing.&amp;nbsp; It's one of the reason's why Source NAT (SNAT) NAD breaks CoA, because ISE will never be able to perform the CoA to a device whose IP address has been source NAT'd.&amp;nbsp; ISE can send the CoA out, but the NAD's reply will be a SNAT'd UDP packet ... ISE will think the ACK never arrived.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Craig Hyps famously had a phrase "SNAT for NAD is bad - SNAT for CoA is OK" - but you have to understand the IP packet flow to know what that means.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jul 2019 23:42:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/use-nas-ip-address-to-look-up-network-device-in-ise-instead-of/m-p/3892319#M542528</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2019-07-17T23:42:37Z</dc:date>
    </item>
  </channel>
</rss>

