Comment 180 for bug 272185

Following posted directions for Windows (http://www.it.northwestern.edu/oncampus/wireless/wireless-connections/wireless-win.html), wireless is 802.1x/WPA2, PEAP, MSCHAPv2. I figured out PEAPv0 while getting wpa_supplicant to work under Puppy Linux (it worked flawlessly, but on a different laptop, so the driver and networking hardware may be an issue). I've never had to deal with certificates in Ubuntu at the times when the connection worked. When it doesn't work, I am presented with the dialog box asking for a certificate. I don't believe I'm supposed to need a certificate. Under Windows, the procedure is that I am asked to authenticate myself with a password and then I'm connected. (Actually, even Windows sometimes has trouble connecting. I have found Lenovo's Access Connections to work reliably as does wpa_supplicant in Puppy Linux.)

I'm not a networking guru and I'm not a Ubuntu expert so I may miss something. The important thing from my perspective is that some of the time the wireless connection just works, and it works for hours, and it reconnects if I click on the GUI. Other times it will not connect no matter what I try.