The umd-secure network encryption options have changed substantially in the last two years. As far as I know, you need to use MSCHAP.
- Y On Mon, Aug 15, 2011 at 10:09 AM, Andres Cimmarusti <cand...@umd.edu> wrote: > Hello there, > > I'm trying to connect to umd-secure using wicd but everything I try > keeps failing. At first I thought wicd just didn't have the > functionality to handle this type of encryption scheme, but then I > found out you have create a template for it. In fact I found one > specifically for umd-secure posted on the list sometime ago: > > http://www.mail-archive.com/um-linux@listserv.umd.edu/msg02800.html > > I tried this and it keeps failing saying: Bad Password....which is > absurd because I've used the same password to log in to the in-browser > authentication for the unsecure wireless. > > Furthermore, Network-Manager has absolutely no trouble connecting. But > since I'm moving away from gnome I would like to use wicd, if > possible. > > I'm running latest wicd v1.7.0 on debian testing, latest stable kernel > 3.0.1 > > Any assistance is appreciated! > > Andres > > PS: as a side note, umd-secure allows you connection using > wpa-peap-tkip-mschapv2 encryption as well, although it says it is less > preferred. wicd has a built-in template for this and I've been able to > connect with this....but it incredibly unstable and will disconnect > frequently. >
