<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>hi, all</span></div><div><span><br></span></div><div><span>Does anybody can explain the meaning of reason code 7(</span><span style="background-color: rgb(241, 241, 241); font-family: verdana, geneva, lucida, 'lucida grande', arial, helvetica, sans-serif; font-size: 13px; ">Client attempted to transfer data before it was associated</span><span style="font-size: 12pt; ">)?</span></div><div><span style="font-size: 12pt; ">I'm puzzled. I encountered a deauthentication problem which print out the reason code is 7.</span></div><div><span style="font-size: 12pt; "><br></span></div><div>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</div><div>transfer data to AP but the association has not been established?</div><div><br></div><div><span
style="font-size: 12pt; ">Thanks in advance!</span></div><div><span style="font-size: 12pt; "><br></span></div><div><span style="font-size: 12pt; ">Yingang</span></div><div><span style="font-size: 12pt; "><br></span></div><div><br></div> <div style="font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "> <div style="font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "> <font size="2" face="Arial"> <hr size="1"> <b><span style="font-weight:bold;">发件人：</span></b> "hostap-request@lists.shmoo.com" <hostap-request@lists.shmoo.com><br> <b><span style="font-weight: bold;">收件人：</span></b> hostap@lists.shmoo.com <br> <b><span style="font-weight: bold;">发送日期：</span></b> 2011年12月18日, 星期日, 上午 1:00<br> <b><span style="font-weight: bold;">主题:</span></b> HostAP Digest, Vol 104, Issue 30<br> </font> <br>Send HostAP mailing list submissions to<br> <a
ymailto="mailto:hostap@lists.shmoo.com" href="mailto:hostap@lists.shmoo.com">hostap@lists.shmoo.com</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="http://lists.shmoo.com/mailman/listinfo/hostap" target="_blank">http://lists.shmoo.com/mailman/listinfo/hostap</a><br>or, via email, send a message with subject or body 'help' to<br> <a ymailto="mailto:hostap-request@lists.shmoo.com" href="mailto:hostap-request@lists.shmoo.com">hostap-request@lists.shmoo.com</a><br><br>You can reach the person managing the list at<br> <a ymailto="mailto:hostap-owner@lists.shmoo.com" href="mailto:hostap-owner@lists.shmoo.com">hostap-owner@lists.shmoo.com</a><br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of HostAP digest..."<br><br><br>Today's Topics:<br><br> 1. Re: [PATCH] Force disconnect a P2P Client/STA from GO/AP side<br>
(Jouni Malinen)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Sat, 17 Dec 2011 18:17:22 +0200<br>From: Jouni Malinen <<a ymailto="mailto:j@w1.fi" href="mailto:j@w1.fi">j@w1.fi</a>><br>Subject: Re: [PATCH] Force disconnect a P2P Client/STA from GO/AP side<br>To: <a ymailto="mailto:hostap@lists.shmoo.com" href="mailto:hostap@lists.shmoo.com">hostap@lists.shmoo.com</a><br>Message-ID: <<a ymailto="mailto:20111217161722.GE11553@w1.fi" href="mailto:20111217161722.GE11553@w1.fi">20111217161722.GE11553@w1.fi</a>><br>Content-Type: text/plain; charset=us-ascii<br><br>On Wed, Dec 14, 2011 at 06:12:49AM -0800, Jithu Jance wrote:<br>> This patch adds a new command "disconnect_sta <mac addr>" to force disconnect<br>> a STA/P2P Client from AP/P2P GO side. Note that P2P Client/STA may connect back <br>> immediately since AP profile may not be disabled at the
client/STA side. Currently, this<br>> is primarily useful for testing purposes.<br><br>Why would a new command be needed for this? hostapd already has<br>deauthenticate and disassociate ctrl_iface commands. Wouldn't one of<br>those be suitable for this need, too?<br><br>> This will be much more useful in scenarios where client side doesn't reconnect back (after disconnection). <br>> This will allow the applications to tear-down connections from the P2P-GO side as well.<br>> For e.g, if mobile acts a GO and it has around 2-3 connections, this cmd will allow to <br>> explicitly tear down a particular client from GO side. But again, this depends on the client side<br>> application framework. For temporary connections such as WiFi-Direct where roaming<br>> cases are extremely rare, Client side application framework may choose to disable P2P<br>> Client interface on getting the CTRL-EVENT-DISCONNECTED event rather than retrying
<br>> to connect.<br><br>This does not sound like something that I would trust on. If the needed<br>functionality is to kick a P2P client away from the group, that client<br>would need to be prevented from reconnecting. Just sending a<br>Deauthentication frame to it does not guarantee anything. And well, even<br>this is not really suitable from the security view point if the stations<br>in the group share the same PSK. Unfortunately, P2P specification does<br>not provide a very good mechanism for handling this type of operations<br>reliably.<br><br>> diff --git a/hostapd/hostapd_cli.c b/hostapd/hostapd_cli.c<br>> index 527860c..5eeefea 100644<br>> --- a/hostapd/hostapd_cli.c<br>> +++ b/hostapd/hostapd_cli.c<br>> @@ -732,6 +749,7 @@ static struct hostapd_cli_cmd hostapd_cli_commands[] = {<br>> + { "disconnect_sta", hostapd_cli_cmd_disconnect_sta },<br>> { "new_sta",
hostapd_cli_cmd_new_sta },<br>> { "deauthenticate", hostapd_cli_cmd_deauthenticate },<br>> { "disassociate", hostapd_cli_cmd_disassociate },<br><br>Those deauth/disassoc commands should be used rather than adding a new<br>command. Sure, they would need to be moved from hostapd/ctrl_iface.c to<br>src/ap/ctrl_iface_ap.c, but that is better than introducing duplicated<br>functionality.<br><br>-- <br>Jouni Malinen PGP id EFC895FA<br><br><br>------------------------------<br><br>_______________________________________________<br>HostAP mailing list<br><a ymailto="mailto:HostAP@lists.shmoo.com" href="mailto:HostAP@lists.shmoo.com">HostAP@lists.shmoo.com</a><br><a href="http://lists.shmoo.com/mailman/listinfo/hostap"
target="_blank">http://lists.shmoo.com/mailman/listinfo/hostap</a><br><br><br>End of HostAP Digest, Vol 104, Issue 30<br>***************************************<br><br><br> </div> </div> </div></body></html>