Does anybody can explain the meaning of reason code 7?

Yingang Fu yingang.fu
Sat Dec 17 21:12:57 PST 2011

hi, all

Does?anybody can explain the meaning of reason code 7(Client attempted to transfer data before it was associated)?
I'm puzzled. I encountered a deauthentication problem which print out the reason code is 7.

I used a phone to connect to an AP and downloading a file to the phone. Does reason code 7 meaning that the phone attempt to
transfer data to AP but the association has not been established?

Thanks in advance!


 ???? "hostap-request at" <hostap-request at>
???? hostap at 
????? 2011?12?18?, ???, ?? 1:00
??: HostAP Digest, Vol 104, Issue 30
Send HostAP mailing list submissions to
??? hostap at

To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to
??? hostap-request at

You can reach the person managing the list at
??? hostap-owner at

When replying, please edit your Subject line so it is more specific
than "Re: Contents of HostAP digest..."

Today's Topics:

?  1. Re: [PATCH] Force disconnect a P2P Client/STA from GO/AP side
? ? ? (Jouni Malinen)


Message: 1
Date: Sat, 17 Dec 2011 18:17:22 +0200
From: Jouni Malinen <j at>
Subject: Re: [PATCH] Force disconnect a P2P Client/STA from GO/AP side
To: hostap at
Message-ID: <20111217161722.GE11553 at>
Content-Type: text/plain; charset=us-ascii

On Wed, Dec 14, 2011 at 06:12:49AM -0800, Jithu Jance wrote:
> This patch adds a new command "disconnect_sta <mac addr>" to force disconnect
> a STA/P2P Client from AP/P2P GO side. Note that P2P Client/STA may connect back 
> immediately since AP profile may not be disabled at the client/STA side. Currently, this
> is primarily useful for testing purposes.

Why would a new command be needed for this? hostapd already has
deauthenticate and disassociate ctrl_iface commands. Wouldn't one of
those be suitable for this need, too?

> This will be much more useful in scenarios where client side doesn't reconnect back (after disconnection). 
> This will allow the applications to tear-down connections from the P2P-GO side as well.
> For e.g, if mobile acts a GO and it has around 2-3 connections, this cmd will allow to 
> explicitly tear down a particular client from GO side. But again, this depends on the client side
> application framework. For temporary connections such as WiFi-Direct where roaming
> cases are extremely rare, Client side application framework may choose to disable P2P
> Client interface on getting the CTRL-EVENT-DISCONNECTED event rather than retrying 
> to connect.

This does not sound like something that I would trust on. If the needed
functionality is to kick a P2P client away from the group, that client
would need to be prevented from reconnecting. Just sending a
Deauthentication frame to it does not guarantee anything. And well, even
this is not really suitable from the security view point if the stations
in the group share the same PSK. Unfortunately, P2P specification does
not provide a very good mechanism for handling this type of operations

> diff --git a/hostapd/hostapd_cli.c b/hostapd/hostapd_cli.c
> index 527860c..5eeefea 100644
> --- a/hostapd/hostapd_cli.c
> +++ b/hostapd/hostapd_cli.c
> @@ -732,6 +749,7 @@ static struct hostapd_cli_cmd hostapd_cli_commands[] = {
> +??? { "disconnect_sta", hostapd_cli_cmd_disconnect_sta },
>? ??? { "new_sta", hostapd_cli_cmd_new_sta },
>? ??? { "deauthenticate", hostapd_cli_cmd_deauthenticate },
>? ??? { "disassociate", hostapd_cli_cmd_disassociate },

Those deauth/disassoc commands should be used rather than adding a new
command. Sure, they would need to be moved from hostapd/ctrl_iface.c to
src/ap/ctrl_iface_ap.c, but that is better than introducing duplicated

Jouni Malinen? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? PGP id EFC895FA


HostAP mailing list
HostAP at

End of HostAP Digest, Vol 104, Issue 30
-------------- next part --------------
An HTML attachment was scrubbed...

More information about the Hostap mailing list