[PATCH v2] Adding disassociate reason as property in dbus

Avichal Agarwal avichal.a at samsung.com
Fri Jul 10 02:04:25 EDT 2015

Dear Jouni 
Many Times connection got unsuccessful due to Assoc-reject . Through this we can provide the exact information about the problem in connection to MW , so that MW can act  according to the problem. This will also  help a lot in resolving the inter-operability  issues.

Dear Dan
We should change the name of property to assocreject , because assoc-reject event is generated at the time of association.

Avichal Agarwal 

------- Original Message -------
Sender : Jouni Malinen<j at w1.fi>
Date : Jul 07, 2015 22:05 (GMT+05:30)
Title : Re: [PATCH v2] Adding disassociate reason as property in dbus

On Tue, Jul 07, 2015 at 10:45:55AM -0500, Dan Williams wrote:
> Would you like the patch more if it *also* showed the reason for a
> disassociation from associated state?  I'd say there's a case for
> both...

I don't know what the use case is for this new property change signal
(which, I'd assume, is the goal here.. getting out a D-Bus signal on
some specific events related to connection status) and as such,
including the disassociation case does not make any difference to me as
long as there are conflicts between the documentation and
implementation. If the commit message (and the D-Bus property name) were
to accurately describe what thisbeing done and what it is useful for, I
would have no issues with either of these cases.

Please keep in mind that disassociation happens only if there was an
association and the association reject event indicates that the attempt
to associate was rejected. These are very different cases from the view
point of association/disassociation management frames.

Jouni Malinen                                            PGP id EFC895FA
HostAP mailing list
HostAP at lists.shmoo.com

More information about the HostAP mailing list