<?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: ISE - WIFI Profiling Issue in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-wifi-profiling-issue/m-p/5312552#M597423</link>
    <description>&lt;P&gt;He want I think make scan of device connect to his network using ISE profiling probe&amp;nbsp;&lt;/P&gt;
&lt;P&gt;He dont use this profiling for any authc.&lt;/P&gt;
&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1291410"&gt;@M_alamin&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Check live log' see if there is any dhcp/dns packet receive from wlc.&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
    <pubDate>Tue, 22 Jul 2025 21:30:42 GMT</pubDate>
    <dc:creator>MHM Cisco World</dc:creator>
    <dc:date>2025-07-22T21:30:42Z</dc:date>
    <item>
      <title>ISE - WIFI Profiling Issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-wifi-profiling-issue/m-p/5312492#M597411</link>
      <description>&lt;P&gt;HI trying to do profiling using MAB over WIFI, i had created initial non-profile auth policy that has ACL from WLC (5508) that allows only DHCP, DNS and IP to ISE PSN, device are hitting this auth profile but keep in unknown state if i hange auth profile to permit access they got profiled successfully which is off course very risky attached is copy of ACL created on WLC knowing my ISE ip is 10.50.3.20 and 10.50.3.30&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="M_alamin_0-1753209043984.png" style="width: 804px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/248809i1A563EDD6F9ECA64/image-dimensions/804x455?v=v2" width="804" height="455" role="button" title="M_alamin_0-1753209043984.png" alt="M_alamin_0-1753209043984.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jul 2025 18:32:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-wifi-profiling-issue/m-p/5312492#M597411</guid>
      <dc:creator>M_alamin</dc:creator>
      <dc:date>2025-07-22T18:32:33Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - WIFI Profiling Issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-wifi-profiling-issue/m-p/5312511#M597412</link>
      <description>&lt;P&gt;Sorry ypu use profiling mac or using mab authc ?&lt;/P&gt;
&lt;P&gt;I need more detail please&amp;nbsp;&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jul 2025 19:04:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-wifi-profiling-issue/m-p/5312511#M597412</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2025-07-22T19:04:21Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - WIFI Profiling Issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-wifi-profiling-issue/m-p/5312522#M597414</link>
      <description>&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/products/collateral/wireless/5500-series-wireless-controllers/eos-eol-notice-c51-740221.html" target="_blank"&gt;https://www.cisco.com/c/en/us/products/collateral/wireless/5500-series-wireless-controllers/eos-eol-notice-c51-740221.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://cs.co/ise-berg#profiling" target="_blank"&gt;https://cs.co/ise-berg#profiling&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What probes are you using on ISE? Is your feed service up to date? What version of ISE? Do you have RADIUS Profiling enabled on the WLAN?&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jul 2025 19:29:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-wifi-profiling-issue/m-p/5312522#M597414</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2025-07-22T19:29:53Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - WIFI Profiling Issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-wifi-profiling-issue/m-p/5312531#M597418</link>
      <description>Ise is 3.3 wlc is 8.5 all profiling probe enable on ise as well as dhcp and http under radius under wlan &lt;BR /&gt;</description>
      <pubDate>Tue, 22 Jul 2025 20:04:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-wifi-profiling-issue/m-p/5312531#M597418</guid>
      <dc:creator>M_alamin</dc:creator>
      <dc:date>2025-07-22T20:04:41Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - WIFI Profiling Issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-wifi-profiling-issue/m-p/5312536#M597420</link>
      <description>Ok so do you actually have DHCP relay configured? Is ISE actually seeing any profiling data? Is the profiling feed service up to date? What patch version of ISE? What exact version of 8.5? You really need to look at getting off of the 5508z&lt;BR /&gt;</description>
      <pubDate>Tue, 22 Jul 2025 20:20:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-wifi-profiling-issue/m-p/5312536#M597420</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2025-07-22T20:20:40Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - WIFI Profiling Issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-wifi-profiling-issue/m-p/5312541#M597421</link>
      <description>Ok wil look at all of that but can you please advice if the acl is correct or its wrong &lt;BR /&gt;</description>
      <pubDate>Tue, 22 Jul 2025 20:47:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-wifi-profiling-issue/m-p/5312541#M597421</guid>
      <dc:creator>M_alamin</dc:creator>
      <dc:date>2025-07-22T20:47:45Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - WIFI Profiling Issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-wifi-profiling-issue/m-p/5312550#M597422</link>
      <description>I mean I have no idea what you are trying to accomplish with that. Why HTTP? Why a permit all?&lt;BR /&gt;</description>
      <pubDate>Tue, 22 Jul 2025 21:17:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-wifi-profiling-issue/m-p/5312550#M597422</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2025-07-22T21:17:40Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - WIFI Profiling Issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-wifi-profiling-issue/m-p/5312552#M597423</link>
      <description>&lt;P&gt;He want I think make scan of device connect to his network using ISE profiling probe&amp;nbsp;&lt;/P&gt;
&lt;P&gt;He dont use this profiling for any authc.&lt;/P&gt;
&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1291410"&gt;@M_alamin&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Check live log' see if there is any dhcp/dns packet receive from wlc.&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jul 2025 21:30:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-wifi-profiling-issue/m-p/5312552#M597423</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2025-07-22T21:30:42Z</dc:date>
    </item>
  </channel>
</rss>

