I've just tryed the behavior of wicd in my University network. It connects perfectly: gtk interface doesn't freeze, ncurses interface connects and doesn't crash and of course connects to network.
So i guess the curses crash and the gui freeze are related to the same problem.
About network configuration, the diferences are:
- My network uses static IP addresses, University's uses DHCP
- Autentication in my network is just WPA2 TKIP, University's uses a complex authentication with LEAP (i think),
- My network has a numeric ESSID... but if you can use numeric ESSIDS, this can't be the problem.
Well, I forgot to say that i've been using wicd for about a year and always worked perfectly until I updated to 1.6.2.1 and, of course, I haven't change anything in configuration.
I've just tryed the behavior of wicd in my University network. It connects perfectly: gtk interface doesn't freeze, ncurses interface connects and doesn't crash and of course connects to network.
So i guess the curses crash and the gui freeze are related to the same problem.
About network configuration, the diferences are:
- My network uses static IP addresses, University's uses DHCP
- Autentication in my network is just WPA2 TKIP, University's uses a complex authentication with LEAP (i think),
- My network has a numeric ESSID... but if you can use numeric ESSIDS, this can't be the problem.
Well, I forgot to say that i've been using wicd for about a year and always worked perfectly until I updated to 1.6.2.1 and, of course, I haven't change anything in configuration.