<?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: DOT1X-1-INVALID_WPA_KEY_STATE: Received EAPOL-key message wh in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/4906042#M259683</link>
    <description>&lt;P&gt;Hey Scott, I'm having similar issues I believe. I'm using PSK and WPA2+WPA3. These are messages I'm seeing from our controller:&lt;/P&gt;&lt;P class=""&gt;*Dot1x_NW_MsgTask_0: Aug 15 17:01:35.938: %LOG-3-Q_IND: [SA]1x_eapkey.c:3080 Received EAPOL-key message while in invalid state (4) - version 2, type 3, descriptor 2, client x.x.x.x.x.x[...It occurred 2 times.!]&lt;/P&gt;&lt;P class=""&gt;*Dot1x_NW_MsgTask_4: Aug 15 17:01:34.691: %DOT1X-3-INVALID_WPA_KEY_STATE: [SA]1x_eapkey.c:3080 Received EAPOL-key message while in invalid state (4) - version 2, type 3, descriptor 2, client x.x.x.x.x.x&lt;/P&gt;</description>
    <pubDate>Wed, 16 Aug 2023 02:45:08 GMT</pubDate>
    <dc:creator>charlesnicholas</dc:creator>
    <dc:date>2023-08-16T02:45:08Z</dc:date>
    <item>
      <title>DOT1X-1-INVALID_WPA_KEY_STATE: Received EAPOL-key message while in invalid</title>
      <link>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859414#M31650</link>
      <description>&lt;P&gt;I'm working on with a customer on a 2106 controller with 1130 series ap's. Everyting seems fine until the client does a reauthentication. At this point the clients send a stream of authentication attempts to the RADIUS server (40 or so a second). The RADIUS (Microsoft IAS) is passing the authetication. The Controller has the error: DOT1X-1-INVALID_WPA_KEY_STATE: Received EAPOL-key message while in invalid state (0) - version 1, type 3, descriptor 254 with the mac address of the offending client in the log, at the same rate of the authentication storm. The clients have current drivers. We are using the Microsoft supplicant and have the Microsoft updates (SP2 and relevant wireless patches) installed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm currently testing using the Intel supplicant, but have not been doing it long enough to see if it is an issue with that supplicant. &lt;/P&gt;</description>
      <pubDate>Sat, 03 Jul 2021 22:18:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859414#M31650</guid>
      <dc:creator>SHANNON WYATT</dc:creator>
      <dc:date>2021-07-03T22:18:30Z</dc:date>
    </item>
    <item>
      <title>Re: DOT1X-1-INVALID_WPA_KEY_STATE: Received EAPOL-key message wh</title>
      <link>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859415#M31653</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, Any progress with this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Apr 2008 03:24:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859415#M31653</guid>
      <dc:creator>m-ketchum</dc:creator>
      <dc:date>2008-04-10T03:24:17Z</dc:date>
    </item>
    <item>
      <title>Re: DOT1X-1-INVALID_WPA_KEY_STATE: Received EAPOL-key message wh</title>
      <link>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859416#M31655</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Honestly this was so long ago I don't remember what I did to resolve the issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Apr 2008 08:27:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859416#M31655</guid>
      <dc:creator>SHANNON WYATT</dc:creator>
      <dc:date>2008-04-10T08:27:33Z</dc:date>
    </item>
    <item>
      <title>Re: DOT1X-1-INVALID_WPA_KEY_STATE: Received EAPOL-key message wh</title>
      <link>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859417#M31656</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,How did u resolve the isssue ..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Jun 2008 13:50:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859417#M31656</guid>
      <dc:creator>murtaza786</dc:creator>
      <dc:date>2008-06-23T13:50:24Z</dc:date>
    </item>
    <item>
      <title>Re: DOT1X-1-INVALID_WPA_KEY_STATE: Received EAPOL-key message wh</title>
      <link>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859418#M31657</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It was so long ago that I don't remember.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Jun 2008 14:09:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859418#M31657</guid>
      <dc:creator>SHANNON WYATT</dc:creator>
      <dc:date>2008-06-23T14:09:52Z</dc:date>
    </item>
    <item>
      <title>Re: DOT1X-1-INVALID_WPA_KEY_STATE: Received EAPOL-key message wh</title>
      <link>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859419#M31658</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Does anyone solve this issue??&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Sep 2008 12:20:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859419#M31658</guid>
      <dc:creator>acgri1982</dc:creator>
      <dc:date>2008-09-16T12:20:48Z</dc:date>
    </item>
    <item>
      <title>Re: DOT1X-1-INVALID_WPA_KEY_STATE: Received EAPOL-key message wh</title>
      <link>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859420#M31659</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is your radius local to the clients or are they authenticating through the WAN?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Sep 2008 16:11:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859420#M31659</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2008-09-16T16:11:59Z</dc:date>
    </item>
    <item>
      <title>Re: DOT1X-1-INVALID_WPA_KEY_STATE: Received EAPOL-key message wh</title>
      <link>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859421#M31660</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is local, in the same LAN. And Cisco Controller is configured with LocalEAP&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Sep 2008 18:19:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859421#M31660</guid>
      <dc:creator>acgri1982</dc:creator>
      <dc:date>2008-09-16T18:19:13Z</dc:date>
    </item>
    <item>
      <title>Re: DOT1X-1-INVALID_WPA_KEY_STATE: Received EAPOL-key message wh</title>
      <link>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859422#M31661</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What type of encryption are you using and also what authentication method?  Do you have the same issue if users are on an ssid that is open.. no type of encryption or authentication?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Sep 2008 18:23:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859422#M31661</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2008-09-16T18:23:06Z</dc:date>
    </item>
    <item>
      <title>Re: DOT1X-1-INVALID_WPA_KEY_STATE: Received EAPOL-key message wh</title>
      <link>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859423#M31662</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In WLANs &amp;gt; Edit -&amp;gt; Security Layer 2 I'm choosing WPA+WPA2 with TKIP and PSK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In WLANs &amp;gt; Edit -&amp;gt; AAA Servers, I mark enabled "Local EAP Authentication" with "LocalEAP" EAP profile name.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then, in Local Net Users &amp;gt; Edit, I fill the fields.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this configuration correct?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Sep 2008 18:31:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859423#M31662</guid>
      <dc:creator>acgri1982</dc:creator>
      <dc:date>2008-09-16T18:31:45Z</dc:date>
    </item>
    <item>
      <title>Re: DOT1X-1-INVALID_WPA_KEY_STATE: Received EAPOL-key message wh</title>
      <link>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859424#M31663</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Okay.... for this wlan ssid, you selected WPA+WPA2.  Here you should define either WPA w/ tkip or WPA2 w/ AES.... or both.  WPA2 performs better than WPA, but that depends on your client supporting WPA2.  Since you selected PSK, you must of entered a pre-shared key.  So in the AAA server tab, you don't have to enable local eap authentication.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For local eap, you need to choose wpa+wpa2 and 802.1x.  This will also require a certificate on the WLC.  I won't go into this too much because you are using PSK.  Now on the client side, you would configure the ssid and either wpa tkip or wpa2 aes and psk... not enterprise.  Enter you pre-shared key in the client and you should be good to go!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Sep 2008 00:25:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/859424#M31663</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2008-09-17T00:25:48Z</dc:date>
    </item>
    <item>
      <title>Re: DOT1X-1-INVALID_WPA_KEY_STATE: Received EAPOL-key message wh</title>
      <link>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/4906042#M259683</link>
      <description>&lt;P&gt;Hey Scott, I'm having similar issues I believe. I'm using PSK and WPA2+WPA3. These are messages I'm seeing from our controller:&lt;/P&gt;&lt;P class=""&gt;*Dot1x_NW_MsgTask_0: Aug 15 17:01:35.938: %LOG-3-Q_IND: [SA]1x_eapkey.c:3080 Received EAPOL-key message while in invalid state (4) - version 2, type 3, descriptor 2, client x.x.x.x.x.x[...It occurred 2 times.!]&lt;/P&gt;&lt;P class=""&gt;*Dot1x_NW_MsgTask_4: Aug 15 17:01:34.691: %DOT1X-3-INVALID_WPA_KEY_STATE: [SA]1x_eapkey.c:3080 Received EAPOL-key message while in invalid state (4) - version 2, type 3, descriptor 2, client x.x.x.x.x.x&lt;/P&gt;</description>
      <pubDate>Wed, 16 Aug 2023 02:45:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/dot1x-1-invalid-wpa-key-state-received-eapol-key-message-while/m-p/4906042#M259683</guid>
      <dc:creator>charlesnicholas</dc:creator>
      <dc:date>2023-08-16T02:45:08Z</dc:date>
    </item>
  </channel>
</rss>

