[PATCH 0/2] dbus: Do Not Coalesce State Changed Signals

Jouni Malinen j
Mon Oct 24 13:10:27 PDT 2011

On Mon, Oct 24, 2011 at 12:07:41PM -0700, Sam Leffler wrote:
> We agree about having explicit signal.  The way we infer a 4WHS issue
> is no less reliable than we would get if State change signals were NOT
> coalesced.  Having an explicit status code / indication is what I
> suggested >year ago when we first hit this issue.  Having the 802.11
> status / reason codes would definitely improve life when a connection
> manager wants to get directly involved in handling certain events.

Huh.. We don't have that with D-Bus? The reason code is included in the
ctrl_iface CTRL-EVENT-DISCONNECTED event and now that I tried to find
matching D-Bus code, I did not even find any signal going out when we
receive a deauth/disassoc frame from the AP. Is the D-Bus interface
really using just the wpa_state change event for this?

Similarly, there is a ctrl_iface event on possible 4-way handshake
event, but obviously no D-Bus code for that either. Not that this would
really be very reliable indication in the first place.. Actually, I
could make it a bit more reliable now that some APs are starting to use
reason codes 15 or 16 to indicate 4-way handshake timeouts and that
could filter out many false positives here.

Jouni Malinen                                            PGP id EFC895FA

More information about the Hostap mailing list