<?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: NAR implementation on wireless using ACS 3.3 in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/nar-implementation-on-wireless-using-acs-3-3/m-p/433069#M9182</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not sure NARs are going to work for this. A NAR is essentially a restriction applied at authentication time based on attributes of the client. For wireless that means the mac address - not very useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should probably be looking at ACLs to restrict what the wireless users can do post-authentication.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Better still would be to create a guest vlan and have users dumped into that.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 Jan 2006 14:27:42 GMT</pubDate>
    <dc:creator>darpotter</dc:creator>
    <dc:date>2006-01-17T14:27:42Z</dc:date>
    <item>
      <title>NAR implementation on wireless using ACS 3.3</title>
      <link>https://community.cisco.com/t5/network-access-control/nar-implementation-on-wireless-using-acs-3-3/m-p/433068#M9181</link>
      <description>&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Im having couple of Access points with ACS 3.3 for the authentication.ACS takes users credentials from Active directory for the authenticating users.And using PEAP.&lt;/P&gt;&lt;P&gt;We have also created one more user group and SSID for the guest to give access for internet.This users group are different and are stored locally in ACS.&lt;/P&gt;&lt;P&gt;I want to make sure that this users are not allowed any other access apart from going to internet.How do i achieve this using NAR in ACS.?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Niraj.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:14:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/nar-implementation-on-wireless-using-acs-3-3/m-p/433068#M9181</guid>
      <dc:creator>n.somaiya</dc:creator>
      <dc:date>2020-02-21T18:14:10Z</dc:date>
    </item>
    <item>
      <title>Re: NAR implementation on wireless using ACS 3.3</title>
      <link>https://community.cisco.com/t5/network-access-control/nar-implementation-on-wireless-using-acs-3-3/m-p/433069#M9182</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not sure NARs are going to work for this. A NAR is essentially a restriction applied at authentication time based on attributes of the client. For wireless that means the mac address - not very useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should probably be looking at ACLs to restrict what the wireless users can do post-authentication.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Better still would be to create a guest vlan and have users dumped into that.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2006 14:27:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/nar-implementation-on-wireless-using-acs-3-3/m-p/433069#M9182</guid>
      <dc:creator>darpotter</dc:creator>
      <dc:date>2006-01-17T14:27:42Z</dc:date>
    </item>
  </channel>
</rss>

