<?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: IAS matching wrong policy in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/ias-matching-wrong-policy/m-p/1248342#M33215</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You should also specify the NAS IP Address for each of your policy.  This way the policy will match the mangement ip address of the readius client.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 21 Jun 2009 14:14:06 GMT</pubDate>
    <dc:creator>Scott Fella</dc:creator>
    <dc:date>2009-06-21T14:14:06Z</dc:date>
    <item>
      <title>IAS matching wrong policy</title>
      <link>https://community.cisco.com/t5/wireless/ias-matching-wrong-policy/m-p/1248340#M33213</link>
      <description>&lt;P&gt;The IAS policy to authenticate users (we have one for VPN and another for wireless), will stop at the first policy that matches the user to the group even though the NAS port type is set to IEEE 802.11. Users were telling me that if they were removed from the group that granted VPN access, then they could hit wireless (but then not be able to get on VPN). &lt;/P&gt;&lt;P&gt;	Â&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone experienced this?	&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 00:42:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ias-matching-wrong-policy/m-p/1248340#M33213</guid>
      <dc:creator>shh5455</dc:creator>
      <dc:date>2021-07-04T00:42:08Z</dc:date>
    </item>
    <item>
      <title>Re: IAS matching wrong policy</title>
      <link>https://community.cisco.com/t5/wireless/ias-matching-wrong-policy/m-p/1248341#M33214</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Edit the properties of the Controller Remote Access Policy. Make sure to add the NAS-Port Type - Wireless - IEEE 802.11&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008082d5b5.shtml" target="_blank"&gt;http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008082d5b5.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Jun 2009 19:43:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ias-matching-wrong-policy/m-p/1248341#M33214</guid>
      <dc:creator>wdrootz</dc:creator>
      <dc:date>2009-06-16T19:43:30Z</dc:date>
    </item>
    <item>
      <title>Re: IAS matching wrong policy</title>
      <link>https://community.cisco.com/t5/wireless/ias-matching-wrong-policy/m-p/1248342#M33215</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You should also specify the NAS IP Address for each of your policy.  This way the policy will match the mangement ip address of the readius client.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 21 Jun 2009 14:14:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ias-matching-wrong-policy/m-p/1248342#M33215</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2009-06-21T14:14:06Z</dc:date>
    </item>
  </channel>
</rss>

