I am still experiencing this issue. In a nutshell:
- I have 2 wireless cards b43 (MacBook Air internal) and ath9k (Alfa, USB
interface & high-gain antenna).
- On slightly weak wireless network signals (-65 to -75 dB) connman keeps
putting my card into scanning mode, thinking I'm roaming. The connection
becomes a nightmare to use. This happens with both cards, and I can
reproduce it on a variety of hotspots.
- If I use plain wpa_supplicant, instantiated by myself or systemd-networkd
(which in turn instantiates wpa_supplicant) with default parameters, my
wireless works fine. I can hold the connection for many hours.
- I think the offending line is #define BGSCAN_DEFAULT "simple:30:-65:300"
What's the reason to change wpa_supplicant defaults to a much more
aggressive roaming threshold?
---------- Forwarded message ----------
From: Tomasz Bursztyka <tomasz.bursztyka(a)linux.intel.com>
Date: Wed, Aug 13, 2014 at 8:17 AM
Subject: Re: Background scan issues?
Thanks. I agree that it looks hardware related. But several people in
the Arch Linux forums were complaining about the same issue, so it
might be a widespread Linux driver shortcoming worth considering.
Wait, using only ConnMan or not? Because if that happens only with
Maybe finally we have an issue there.
Surprisingly if I run wpa_supplicant with this settings:
(using netctl) my connection is
Here's the log for connman and wpa_supplicant:
How can I make connman instantiate wpa_supplicant with the -ddt option?
Best is you stop both connman and wpa_supplicant and you restart them by
hand, wpa_supplicant first.
./wpa_supplicant -u -ddt &> wpa_supplicant.log
then on another terminal: CONNMAN_SUPPLICANT_DEBUG=1 connmand -n -d &>
and you paste the *.log files.
connman mailing list