Wicd has issues when multiple access points share an SSID

I had trouble reproducing these issues, possibly because the microwave was running while I did this, so I had to take some additional steps to reproduce it these issues.

Here are the steps I took.

1. I executed "rm -rf /var/log/wicd/*" inside konsole and then "reboot".
2. I logged into KDM, opened the Wicd GUI to verify to which access point it was connected and closed the Wicd GUI. It was in proximity to the Actiontec access point and was connected to channel 11, which indicates that the was connected to the Actiontec access point, which was good. I also opened Chromium and verified that I had a connection to the network via the actiontec's html-based configuration GUI.
3. I brought the laptop into proximity to the Linksys router and opened the Wicd GUI. It did not drop my connection. At this time, the microwave was going and I noticed that Wicd was reporting a higher -dBM for the Linksys access point than it was for the Actiontec access point (-52 dBm Actiontec, -60 dBm Linksys), which is atypical.
4. To fix this, I moved my laptop within 0.2 meters of the linksys access point and clicked refresh in the Wicd GUI. The GUI indicated that the Linksys access point was at -29 dBm, which was a typical level for the router. I promptly lost my internet connection.
5. I then attempted to connect to the Actiontec access point (channel 11) and it connected to the Linksys access point (channel 1). I verified in Chromium that I had a connection to the network via the actiontec's html-based configuration GUI.

I have attached the contents of /var/log/wicd/wicd.log after this exercise.

I have a very similar problem with the WLAN in my university. It has a lot of access points to cover the whole area. So I usually can reach several access points with the same SSIDs working on different channels.
Normally I would like to connect to the access point with the highest connectivity, but when I click connect on the item in wicd's list, it seems to pick one of the access points at random. In order to get a good connection (to the right AP) I have to reconnect a few times.

This is on gentoo with a 2.6.32-tuxonice kernel and wicd 1.7.0.

I think my issue is related. The only difference is that in my case, wicd insists on connecting to the weaker signal. Even if I disconnect and manually select the stronger one, it connects to the weaker, more distant point.

What it seems to be doing is connecting to the main access point and refusing to connect to the secondary one which was set up because the signal from the main access point is relatively weak upstairs. So even though I am sitting right next to the booster point (100% strength), wicd insists on connecting directly to the primary access point downstairs (35%).

Both points are configured identically in the wicd preferences, with the option to use the same settings for all points which share the same essid checked.

I'm not sure if this is a regression as I don't think I saw this with earlier versions of wicd but I have also changed linux distro and hardware so it is hard to tell.

The problematic case for me involves a laptop with Intel Centrino 1000 wireless using iwlagn and wicd 1.7.0-13 in arch linux 3.1.5-1.

I would be happy to provide further information if that would be helpful.

I have the same issue with wicd. I'm using the latest stable version 1.7.1.

At University, the wlan has many many access points with the same SSID. I was in my lab about an hour ago, and I had set up wicd to connect automatically to the university's secure (PEAP + TKIP + MSCHAPv2 + certificate) wireless network.

I moved under 30 meters to another room, resumed my laptop and bam! wicd could not find the wireless network I had saved my settings to, because that access point wasn't available in that other room, even though another wlan with same SSID had a good signal in that room. As a result: wicd did not connect to anything automatically and I had to set everything up again.

I've used network-manager on this laptop before (but now that I've moved to xfce, I want to stay away from gnome stuff). It works without problems with any access point and associates all under the same SSID.

Could it be possible to have wicd store the connection / authentication info for a broad SSID with many access points so it doesn't fail to connect everytime?

It should already work like this.

Just to be sure: can you avoid suspending + resuming the laptop when you move under another AP's range?
It might be that your problem is related to suspend+resume.

Unfortunately, I don't have any multi-AP network handy, so I can't really try to reproduce this.

Can confirm that it's still happening with Wicd 1.7.4 on Ubuntu 16.04.4. It's a particularly annoying issue as multiple hotels/hostels tend to have a setup with multiple APs having the same SSID.

Can confirm that this is still a bug in the system. Now at Ubuntu 20.10.
Wicd 1.7.4+tb2-6

Understood that this is a stalled development project, and has not been updated since 2016. Simply adding that there's another person with the same issue.