Reason: 14

English Network/Internet
1

I can’t get my wireless to connect. It says it’s trying, then it fails. See below.

How do I find out what Reason: 14 is?



 2452.826080] wlan0: authenticate with e0:46:9a:2a:1d:8d
 2452.834902] wlan0: send auth to e0:46:9a:2a:1d:8d (try 1/3)
 2452.836612] wlan0: authenticated
 2452.836748] wlan0: associating with AP with corrupt beacon
 2452.837033] wlan0: associate with e0:46:9a:2a:1d:8d (try 1/3)
 2452.840969] wlan0: RX AssocResp from e0:46:9a:2a:1d:8d (capab=0x431 status=0 aid=7)
 2452.863833] wlan0: associated
 2454.426906] wlan0: deauthenticated from e0:46:9a:2a:1d:8d (Reason: 14)
2

Here is the reason list: Basic Choreography :: Chapter 4. WLAN Fundamentals :: Wireless lan security :: Networking :: eTutorials.org

You need to read these and provided added info:

https://forums.opensuse.org/english/get-technical-help-here/wireless/410319-getting-your-wireless-work.html

https://forums.opensuse.org/english/get-technical-help-here/wireless/391535-my-wireless-doesnt-work-primer-what-i-should-do-next.html

You must include your openSUSE version and Desktop used and info on your home wireless network setup.

Thank You,

3

On 10/31/2013 06:36 PM, LouBryan wrote:
>
> I can’t get my wireless to connect. It says it’s trying, then it fails.
> See below.
>
> How do I find out what Reason: 14 is?
>
> Code:
> --------------------
>
>
> 2452.826080] wlan0: authenticate with e0:46:9a:2a:1d:8d
> 2452.834902] wlan0: send auth to e0:46:9a:2a:1d:8d (try 1/3)
> 2452.836612] wlan0: authenticated
> 2452.836748] wlan0: associating with AP with corrupt beacon
> 2452.837033] wlan0: associate with e0:46:9a:2a:1d:8d (try 1/3)
> 2452.840969] wlan0: RX AssocResp from e0:46:9a:2a:1d:8d (capab=0x431 status=0 aid=7)
> 2452.863833] wlan0: associated
> 2454.426906] wlan0: deauthenticated from e0:46:9a:2a:1d:8d (Reason: 14)

As in many cases, I used Google and found
http://etutorials.org/Networking/Wireless+lan+security/Chapter+4.+WLAN+Fundamentals/Basic+Choreography/.

Reason 14 says “MIC failure”. That means that the WPA encryption code is failing
and the packet is corrupt. I would worry about that corrupt beacon from the AP.
Have you tried rebooting the AP?

4

Google, well duh, sometimes the method to the answer is right there and I didn’t even think about it. Thanks. I googled reason 14 and found it.

I can’t reboot the AP because I’m setting up in a lab and connecting to their site. I’ll direct the questions to their end.

Thanks for your help.

5

The more info you provide here the more help we can provide. Good luck with the Lab.

Thank You,

6

On 10/31/2013 08:16 PM, jdmcdaniel3 wrote:
>
> LouBryan;2594847 Wrote:
>> Google, well duh, sometimes the method to the answer is right there and
>> I didn’t even think about it. Thanks. I googled reason 14 and found
>> it.
>>
>> I can’t reboot the AP because I’m setting up in a lab and connecting to
>> their site. I’ll direct the questions to their end.
>>
>> Thanks for your help.
>
> The more info you provide here the more help we can provide. Good luck
> with the Lab.

Although the indication is that the AP is broken, it is still possible that the
AP is non-standard enough to trigger a bug in the driver for the wifi device. As
you failed to provide any info about that device, ther is nothing more we can do.