CHROMIUM: Bump up logging level for blacklist decisions
Chrome OS relies on its connection manager, shill, to bump up the
logging level in wpa_supplicant during 'interesting' times via its
WiFi::SetConnectionDebugging method. The method sets wpa_supplicant
debug level to 'info' (quieter) or 'debug' (verbose).
It's not clear SetConnectionDebugging is being called on execution
paths of interest - in particular, APs we are connected to at one
instant show up as blacklisted in the scan after an unexpected
disconnect, like so: (<> implies redacted/placeholder)
wlan0: New scan results available (own=1 ext=0)
wlan0: Radio work 'scan'@<> done in <> seconds
wlan0: Selecting BSS from priority group <>
// This SSID was one we were connected to before, and there was
// no mention of blacklisting it in the log lines prior to this.
wlan0: 0: <> ssid='<>' wpa_ie_len=0 rsn_ie_len=<> caps=<> level=<> freq=<> wps
wlan0: skip - blacklisted (count=2 limit=0)
wlan0: 1: <> ssid='<>' wpa_ie_len=0 rsn_ie_len=<> caps=<> level=<> freq=<> wps
Ensure that we always print blacklist adding/clearing decisions - its
only 3 lines anyways.
BUG=chromium:771501
TEST=(TBD)
Change-Id: I4ea4b01239dc95c4a1e4619f1d4ddb0c4b8eb63b
Signed-off-by: Kirtika Ruchandani <kirtika@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/699640
Reviewed-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Eric Caruso <ejcaruso@chromium.org>
1 file changed
