Scan request looks ignored when wpa_state is in scanning state with dbus interface

Jouni Malinen j at w1.fi
Fri Mar 4 10:54:39 PST 2016


On Thu, Feb 25, 2016 at 06:34:01PM +0530, Johncy Bennette wrote:
> AP-Problem.log
> 
> I switched off the router around the time
> 1456401394.205710: dbus: flush_object_timeout_handler: Timeout -
> sending changed properties of object
> /fi/w1/wpa_supplicant1/Interfaces/1
> 
> Around the time 1456401598.821077: wlan0: Setting scan request:
> 1.000000 sec I gave the scan command.
> 
> The dbus sequence I follow is,
> AddNetwork
> SelectNetwork

Which version of wpa_supplicant are you using here? Could you please try
with a more recent version (or even better, snapshot of hostap.git)? The
debug log should show that type of D-Bus operations like this:
dbus: fi.w1.wpa_supplicant1.Interface.AddNetwork (/fi/w1/wpa_supplicant1/Interfaces/1) [a{sv}]
dbus: Register network object '/fi/w1/wpa_supplicant1/Interfaces/1/Networks/0'
...
dbus: fi.w1.wpa_supplicant1.Interface.SelectNetwork (/fi/w1/wpa_supplicant1/Interfaces/1) [o]

The debug log you sent here does not show any sign of such operations
being executed..

> When there is problem connecting ie at the time of reconnect,
> SelectNetwork with the object obtained as part of AddNetwork
> Then I wait for "completed" signal from dbus
> udhcpc -iwlan0 if connected.
> 
> I could see from the log,
> 1456401549.760162: Fast associate: Old scan results
> After this there is continous scan requests ignored.

New scan requests are not issued because there is already an ongoing
sched_scan operation. That should have been updated if a new network was
added and selected, but the debug log you sent did not show such
operations, so it is difficult to say what exactly happened here.

-- 
Jouni Malinen                                            PGP id EFC895FA



More information about the Hostap mailing list