Network ESSID configured to "Use settings...essid" does not autoconnect
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
wicd |
New
|
Undecided
|
Unassigned | ||
wicd (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
At work, we have a network consisting of dozens of access points, each with two separate ESSIDs, one for 2.4Ghz and one for 5Ghz with separate BSSIDs. An autoconnect to any will result in dhcp retrieving the same IP, etc.
wicd will only autoconnect to a BSSID which I had previously selected and asked it to connect.
Changing wicd-daemon as follows gets the behavior I had expected:
rholt@work:
=== modified file 'wicd/wicd-
--- wicd/wicd-daemon.py 2015-02-12 17:01:42 +0000
+++ wicd/wicd-daemon.py 2015-04-07 02:05:39 +0000
@@ -1404,7 +1404,8 @@
for x, network in enumerate(
- if self.config.
+ essid_key = "essid:%s" % network['essid']
+ if self.config.
if self.debug_mode:
if bool(network.
With this change, wicd connects to the strongest AP signal at the time without me having to bring up the cli and select it.
This had an added benefit with my wifi tethering. When my Android phone sets up a hotspot, the BSSID changes each time, so now wicd-daemon connects to my phone without me needing to bring up the cli at all.
Related branches
Changed in ubuntu: | |
status: | New → Confirmed |
affects: | ubuntu → wicd (Ubuntu) |
Sorry, my initial add said "two separate ESSIDs" when it should have said "two identical ESSIDs".