Comment 177 for bug 272185

Unfortunately Dan's fix (using the Jaunty networking packages in Intrepid) does not work for me. My laptop is a Lenovo X200s with a 5100 AGN adapter, using iwlagn. My university network uses WPA2, PEAP (ver 0), MS-CHAP2. I have always had erratic connections using Intrepid --- sometimes the laptop connected, sometimes it didn't and I would keep getting the certificate dialog. That pattern persists with the Jaunty packages. Just now I had a connection, I took the laptop to a new location and it refused to connect. The probability of making a connection may be a little higher, but it's hard to tell and it is still not reliable.

Let me ask a question that would help in debugging: Is there any way to force network-manager to try to connect wirelessly? Sometimes wireless is activated (wlan0 is up) and I am in range of a node, but the "wireless network" selection is grayed out in the NM dialog box (from the panel) and I am don't know how to force NM to try to connect. Restarting NM doesn't help. Any thoughts about what to do? Maybe I'm missing something obvious. Thanks.