diff options
author | Lubomir Rintel <lkundrak@v3.sk> | 2018-11-21 11:22:08 +0100 |
---|---|---|
committer | Lubomir Rintel <lkundrak@v3.sk> | 2018-11-29 17:50:00 +0100 |
commit | 3a999475efa40fcba3ffc7bd918236d89417598a (patch) | |
tree | 2c5ddf022edb33c9c14fbdf66f7918930198e141 /po/th.po | |
parent | 64b95d567ba89cb904a1795a16f9910552382b87 (diff) | |
download | NetworkManager-3a999475efa40fcba3ffc7bd918236d89417598a.tar.gz |
wifi/olpc-mesh: allow autoconnect
There's no reason the mesh shouldn't autoconnect. Almost.
The mesh and regular Wi-Fi shares the same radio. There, in the first
place, probably shouldn't have been separate NMDevices. Not sure whether
we can fix it at this point, but we can surely avoid unnecessary
competition between the two devices: give the regular Wi-Fi priority and
only connect mesh if the regular companion stays disconnected.
For the record; connections shipped on XO-1 laptops all have
autoconnect=off and thus are not affected by this.
Diffstat (limited to 'po/th.po')
0 files changed, 0 insertions, 0 deletions