<?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: 9800L ISE dot1x PEAP timeout in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4967568#M263568</link>
    <description>&lt;P&gt;I already did it, but don't see anything useful, except one message:&amp;nbsp;&lt;BR /&gt;&lt;SPAN&gt;Client made a new Association to an AP/BSSID:&lt;BR /&gt;&lt;/SPAN&gt;Also in the debug I see that WLC is sending radius to ISE, but at the same time there is no traffic in .pcap...&lt;/P&gt;&lt;P&gt;here is the whole output, interesting part is that after the radius message&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 28 Nov 2023 15:33:35 GMT</pubDate>
    <dc:creator>martin0009</dc:creator>
    <dc:date>2023-11-28T15:33:35Z</dc:date>
    <item>
      <title>9800L ISE dot1x PEAP timeout</title>
      <link>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4967481#M263555</link>
      <description>&lt;P&gt;Hello community,&lt;/P&gt;&lt;P&gt;I have a problem with 802.1x PEAP authentication.&lt;BR /&gt;&lt;BR /&gt;The environment is WLC&amp;nbsp;17.9.4&amp;nbsp; and ISE 2.4.&lt;BR /&gt;APs are in local switching.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;When user tries to connect, I see request on ISE and then authentication times out.&lt;BR /&gt;ISE says&amp;nbsp; "5440 Endpoint abandoned EAP session and started new"&lt;/P&gt;&lt;P&gt;The client says "Reason: There was no response to the EAP Response Identity packet."&lt;/P&gt;&lt;P&gt;On the client, using Microsoft network monitor I see EAPOL, EAP req / response&lt;BR /&gt;The client has a manual configuration of wireless network, configured to use WAP enterprise, PEAP/MSCHAPv2.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I went and captured traffic on the WLC, I see EAP req / response, and then RADIUS access-challenge.&lt;BR /&gt;The Radius packet says "Type:protected eap eap-peap"&lt;BR /&gt;The WLC should now create EAPOL EAP-req&amp;nbsp; and send it to the client.&lt;BR /&gt;This never happens and both ISE and client complain about auth timeout.&lt;BR /&gt;I have changed auth timeout timers, but it only takes longer for connection to fail..&lt;BR /&gt;&lt;BR /&gt;Maybe it's something obvious, misconfiguration or something, but I don't see it.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2023 14:02:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4967481#M263555</guid>
      <dc:creator>martin0009</dc:creator>
      <dc:date>2023-11-28T14:02:53Z</dc:date>
    </item>
    <item>
      <title>Re: 9800L ISE dot1x PEAP timeout</title>
      <link>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4967507#M263558</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Client debugging according to&amp;nbsp;&lt;A href="https://logadvisor.cisco.com/logadvisor/wireless/9800/9800ClientConnectivity" target="_blank"&gt;https://logadvisor.cisco.com/logadvisor/wireless/9800/9800ClientConnectivity&lt;/A&gt;&amp;nbsp;may provide extra insights ; you can have client debugs (RadioActive Traces) analyzed with :&amp;nbsp;&lt;A href="https://cway.cisco.com/tools/WirelessDebugAnalyzer/" target="_blank"&gt;https://cway.cisco.com/tools/WirelessDebugAnalyzer/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2023 14:27:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4967507#M263558</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2023-11-28T14:27:24Z</dc:date>
    </item>
    <item>
      <title>Re: 9800L ISE dot1x PEAP timeout</title>
      <link>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4967568#M263568</link>
      <description>&lt;P&gt;I already did it, but don't see anything useful, except one message:&amp;nbsp;&lt;BR /&gt;&lt;SPAN&gt;Client made a new Association to an AP/BSSID:&lt;BR /&gt;&lt;/SPAN&gt;Also in the debug I see that WLC is sending radius to ISE, but at the same time there is no traffic in .pcap...&lt;/P&gt;&lt;P&gt;here is the whole output, interesting part is that after the radius message&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2023 15:33:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4967568#M263568</guid>
      <dc:creator>martin0009</dc:creator>
      <dc:date>2023-11-28T15:33:35Z</dc:date>
    </item>
    <item>
      <title>Re: 9800L ISE dot1x PEAP timeout</title>
      <link>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4967586#M263571</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;- Check full radius logs on ISE too (if not yet done) ,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2023 16:19:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4967586#M263571</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2023-11-28T16:19:57Z</dc:date>
    </item>
    <item>
      <title>Re: 9800L ISE dot1x PEAP timeout</title>
      <link>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4967967#M263607</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;-&lt;U&gt; Added reply&lt;/U&gt; ; probably not related to this issue (because &lt;EM&gt;'radius is radius'&lt;/EM&gt;) ; but your ISE version is way End of Life/End of Support&amp;nbsp;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;for business continuity&amp;nbsp; consider upgrading and or &lt;FONT color="#008000"&gt;&lt;EM&gt;using modern and &lt;U&gt;supported ISE version ,&amp;nbsp;&lt;BR /&gt;&lt;/U&gt;&lt;FONT color="#000000"&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;That being important too when a &lt;STRONG&gt;TAC&lt;/STRONG&gt; case must be created&lt;/FONT&gt;&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Wed, 29 Nov 2023 08:35:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4967967#M263607</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2023-11-29T08:35:42Z</dc:date>
    </item>
    <item>
      <title>Re: 9800L ISE dot1x PEAP timeout</title>
      <link>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4968279#M263620</link>
      <description>&lt;P&gt;I found out that WLC does not send radius to ISE due to the network error:&lt;/P&gt;&lt;P&gt;what could be reason for this?&lt;/P&gt;&lt;P&gt;Once client stops trying, WLC will send messages to ISE and get response, but by that time, the initial session will already expire&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="martin0009_0-1701269935784.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/203654iE48F3043D7A03517/image-size/medium?v=v2&amp;amp;px=400" role="button" title="martin0009_0-1701269935784.png" alt="martin0009_0-1701269935784.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;2023/11/29 15:34:18.448440397 {wncd_x_R0-0}{2}: [radius] [23598]: (info): RADIUS: wlan-group-mgmt-cipher[189] 6 " "&lt;BR /&gt;2023/11/29 15:34:18.448451007 {wncd_x_R0-0}{2}: [radius] [23598]: (ERR): IPv4 SendMessage failed with error Network is unreachable&lt;BR /&gt;2023/11/29 15:34:18.448451699 {wncd_x_R0-0}{2}: [radius] [23598]: (ERR): Error in sending out of the socket Network is unreachable&lt;BR /&gt;2023/11/29 15:34:18.448452083 {wncd_x_R0-0}{2}: [radius] [23598]: (ERR): RADIUS(00000000): Sending a IPv4 Radius Packet failed&lt;BR /&gt;2023/11/29 15:34:18.448466495 {wncd_x_R0-0}{2}: [radius] [23598]: (info): RADIUS: Started 64 sec timeout&lt;BR /&gt;2023/11/29 15:34:18.448762313 {wncd_x_R0-0}{2}: [radius] [23598]: (ERR): Invalid parameter in BSOCK response&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Nov 2023 15:00:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4968279#M263620</guid>
      <dc:creator>martin0009</dc:creator>
      <dc:date>2023-11-29T15:00:09Z</dc:date>
    </item>
    <item>
      <title>Re: 9800L ISE dot1x PEAP timeout</title>
      <link>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4968304#M263623</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; - Looks like traffic blocking by some device ; is there a free path between the WLC and ISE ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Nov 2023 15:51:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4968304#M263623</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2023-11-29T15:51:51Z</dc:date>
    </item>
    <item>
      <title>Re: 9800L ISE dot1x PEAP timeout</title>
      <link>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4968312#M263624</link>
      <description>&lt;P&gt;sorry but are you a bot?&lt;/P&gt;&lt;P&gt;If something was blocking the traffic, wouldn't is see the traffic going out of the interface? and there would not be return traffic?&lt;/P&gt;&lt;P&gt;I don't see traffic going out of WLC, how does the WLC knows that the network is unreachable?&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Nov 2023 15:56:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4968312#M263624</guid>
      <dc:creator>martin0009</dc:creator>
      <dc:date>2023-11-29T15:56:52Z</dc:date>
    </item>
    <item>
      <title>Re: 9800L ISE dot1x PEAP timeout</title>
      <link>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4968326#M263627</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;U&gt;&amp;gt; ..&amp;nbsp;&lt;EM&gt;how does the WLC knows that the network is unreachable?&lt;/EM&gt;&lt;/U&gt;&lt;BR /&gt;&amp;nbsp; &amp;nbsp;That's a bit like biting on the problem&amp;nbsp; ; it just uses standard network protocols ; you could for instance use a tool like&amp;nbsp;&lt;A href="https://www.iea-software.com/products/radiusnt/radlogin4.cfm" target="_blank"&gt;https://www.iea-software.com/products/radiusnt/radlogin4.cfm&lt;/A&gt;&amp;nbsp;and test from a host on the same subnet as the WLC&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Wed, 29 Nov 2023 16:25:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4968326#M263627</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2023-11-29T16:25:03Z</dc:date>
    </item>
    <item>
      <title>Re: 9800L ISE dot1x PEAP timeout</title>
      <link>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4968708#M263646</link>
      <description>&lt;P&gt;9800 is IOS-XE - the radius needs to be reachable via routing table and radius needs to be able to reply back to the WLC.&lt;/P&gt;
&lt;P&gt;So start with "sh ip route" to make sure you have a valid route to reach the radius IP.&amp;nbsp; Make sure you're sending the radius from the correct source IP address - by default it will simply use the outbound interface IP (based on the outbound interface selected according to the routing table).&amp;nbsp; Maybe try pinging the radius from the same source interface for a start to prove network connectivity.&lt;/P&gt;
&lt;P&gt;When doing packet captures it often also helps to include control-plane in case the packets aren't going out the interface you thought they were.&amp;nbsp; That will also show you source and destination IP regardless of outgoing interface.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Nov 2023 02:06:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4968708#M263646</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2023-11-30T02:06:43Z</dc:date>
    </item>
    <item>
      <title>Re: 9800L ISE dot1x PEAP timeout</title>
      <link>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4969077#M263687</link>
      <description>&lt;P&gt;I found a problem, but don't know the reason or the cause.&lt;BR /&gt;check the picture bellow.&amp;nbsp;&lt;BR /&gt;Routing is not a problem, WLC can reach ISE all the time.&lt;BR /&gt;Problem is that WLC waits after receiving "eap identify response" to send RADIUS access request ti ISE.&lt;BR /&gt;And it receives instant reply.&amp;nbsp;&lt;BR /&gt;But in this pcap 5 minutes passed since initial eap identity message.&lt;/P&gt;&lt;P&gt;Whole time WLC is reachable from LAN and responding to pings. There is no routing, as per best practice. There is only one L3 interface on the WLC.&lt;/P&gt;&lt;P&gt;Any ideas what could delay the traffic?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="martin0009_1-1701354531308.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/203739iF76ACD78F59098F4/image-size/medium?v=v2&amp;amp;px=400" role="button" title="martin0009_1-1701354531308.png" alt="martin0009_1-1701354531308.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Nov 2023 14:29:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4969077#M263687</guid>
      <dc:creator>martin0009</dc:creator>
      <dc:date>2023-11-30T14:29:04Z</dc:date>
    </item>
    <item>
      <title>Re: 9800L ISE dot1x PEAP timeout</title>
      <link>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4969087#M263688</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#FF6600"&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;- Possibly&amp;nbsp; :&lt;/FONT&gt;&amp;nbsp;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwi25328" target="_blank"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwi25328&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Nov 2023 14:52:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4969087#M263688</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2023-11-30T14:52:14Z</dc:date>
    </item>
    <item>
      <title>Re: 9800L ISE dot1x PEAP timeout</title>
      <link>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4969131#M263695</link>
      <description>&lt;P&gt;Hi friend&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What cert you use for peap in client?&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Thu, 30 Nov 2023 15:46:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4969131#M263695</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-11-30T15:46:49Z</dc:date>
    </item>
    <item>
      <title>Re: 9800L ISE dot1x PEAP timeout</title>
      <link>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4969161#M263696</link>
      <description>&lt;P&gt;That version of ISE you have is pretty old. &amp;nbsp;My suggestion is that you download an EAP-TEST tool and test it from your laptop. &amp;nbsp;There are versions for Windows and Mac also. &amp;nbsp;Just make sure you add your laptop/ip to the network devices in ISE. &amp;nbsp;Make sure you get a successful auth before you tinker around anymore.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.serverwatch.com/guides/radius-server-test-tools/" target="_blank"&gt;radius-server-test-tools&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Nov 2023 16:28:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4969161#M263696</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2023-11-30T16:28:00Z</dc:date>
    </item>
    <item>
      <title>Re: 9800L ISE dot1x PEAP timeout</title>
      <link>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4969340#M263707</link>
      <description>&lt;P&gt;Weird and makes no sense.&amp;nbsp; Open a TAC case and let them work it out for you.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Nov 2023 23:20:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4969340#M263707</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2023-11-30T23:20:27Z</dc:date>
    </item>
    <item>
      <title>Re: 9800L ISE dot1x PEAP timeout</title>
      <link>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4970824#M263810</link>
      <description>&lt;P&gt;I got successful auth, but the time is high.&lt;BR /&gt;The problem is related to ISE.&lt;BR /&gt;WLC also does weird stuff,&amp;nbsp;&lt;STRONG&gt;test aaa group&amp;nbsp; &amp;nbsp;&lt;/STRONG&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;ISE-GRP&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;lt;USER&amp;gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;=password=&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; new-code&amp;nbsp;&amp;nbsp;&lt;BR /&gt;returns result after a several seconds, definitely below EAP timeout which is set to 30 seconds. I don't see WLC is even tying anything, maybe it thinks RADIUS is dead.&lt;BR /&gt;I will try to check with TAC and post a solution here if I ever find it. (before I build new lab with new ise)&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Dec 2023 08:06:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4970824#M263810</guid>
      <dc:creator>martin0009</dc:creator>
      <dc:date>2023-12-04T08:06:33Z</dc:date>
    </item>
    <item>
      <title>Re: 9800L ISE dot1x PEAP timeout</title>
      <link>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4970852#M263814</link>
      <description>&lt;P&gt;a client only needs to verify server cert.&amp;nbsp;&lt;BR /&gt;but this is not important because we never reach this step.&lt;BR /&gt;I don't want to post picture of EAP process here,&amp;nbsp; the process is failing on the "radius access request" from WLC, and then repose from ISE to WLC.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Dec 2023 09:23:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/9800l-ise-dot1x-peap-timeout/m-p/4970852#M263814</guid>
      <dc:creator>martin0009</dc:creator>
      <dc:date>2023-12-04T09:23:42Z</dc:date>
    </item>
  </channel>
</rss>

