<?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 Radius for clients behind NAT in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/radius-for-clients-behind-nat/m-p/4525594#M572005</link>
    <description>&lt;P&gt;I'm tasting Dot1X / Posture / General RADIUS in my lab, and I want to have some clients with a private VLAN behind NAT, are there any considerations to keep in mind when I use ISE as the radius server?&lt;/P&gt;</description>
    <pubDate>Sat, 01 Jan 2022 21:44:09 GMT</pubDate>
    <dc:creator>SMD28316</dc:creator>
    <dc:date>2022-01-01T21:44:09Z</dc:date>
    <item>
      <title>Radius for clients behind NAT</title>
      <link>https://community.cisco.com/t5/network-access-control/radius-for-clients-behind-nat/m-p/4525594#M572005</link>
      <description>&lt;P&gt;I'm tasting Dot1X / Posture / General RADIUS in my lab, and I want to have some clients with a private VLAN behind NAT, are there any considerations to keep in mind when I use ISE as the radius server?&lt;/P&gt;</description>
      <pubDate>Sat, 01 Jan 2022 21:44:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/radius-for-clients-behind-nat/m-p/4525594#M572005</guid>
      <dc:creator>SMD28316</dc:creator>
      <dc:date>2022-01-01T21:44:09Z</dc:date>
    </item>
    <item>
      <title>Re: Radius for clients behind NAT</title>
      <link>https://community.cisco.com/t5/network-access-control/radius-for-clients-behind-nat/m-p/4526164#M572025</link>
      <description>&lt;P&gt;There is nothing really specific required to handle clients behind NAT, but the profiling information ISE has for these clients may be off or partial. As long as the radius authentication being sent from the network device itself isn't natted, then you will handle it like regular endpoint authentication.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;If the switch communicating with ISE is behind nat, then it's a whole different can of worms.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jan 2022 03:18:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/radius-for-clients-behind-nat/m-p/4526164#M572025</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2022-01-04T03:18:15Z</dc:date>
    </item>
  </channel>
</rss>

