touch-packages team mailing list archive

[Mathieu Trudel-Lapierre <mathieu.tl@xxxxxxxxx>]

Reassigning to wpasupplicant, which is what does the selection, past the
user telling which SSID to use.

Now, I find this highly unlikely to happen. wpasupplicant and NM know
about signal levels and use that almost exclusively to select the "best"
AP within a SSID to connect to. It's not the *only* criteria, but for
the purpose of most bug reports it's fine to treat things as if it was.

Usually, what happens is that the selected AP really was the strongest
(or the strongest detected) signal AP when the connection was
established, and it hasn't roamed to a better one because the
differences in signal aren't significant enough.

There isn't enough information here to know whether it is the case.
Could you please attach at least /var/log/syslog to the bug report; or
even better: use 'apport-collect 1476003' to automatically gather the
relevant information to this bug report from your system, then we can
look at the logs to try to see if the other APs are detected, and which
signal levels they may have.

To do this, we'll most likely also need debug-level logs from NetworkManager. You can use the command:
sudo nmcli g logging level debug domains wifi,supplicant

To enable debug-level logging, which will write extra details to
/var/log/syslog about the state of wireless on your system.

** Changed in: wpasupplicant (Ubuntu)
       Status: New => Incomplete

** Package changed: wpasupplicant (Ubuntu) => wpa (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1476003

Title:
  Doesn't default/autoconnect to strongest BSSID within same SSID

Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 15.04
  network-manager 0.9.10.0-4ubuntu15.1

  Expectation: automatically connect to the strongest broadcasting
  device within the same SSID (unless stated otherwise when editing
  connection)

  What happened instead: I now have to manually force the BSSID by
  editing the connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1476003/+subscriptions