You are not logged in.
I have a weird situation with wicd that I've tested on multiple machines and multiple wireless networks.
If I set up a connection to a WPA 2 protected wireless network using the wicd gui, and then I click connect, every single time wicd will go through the motions of putting the interface up and failing authentication.
However, I've told wicd to automatically connect to the network, and specified in the configuration it should automatically re-try to connect. And this works....
When I close the wicd gui, it will then sometimes automatically connect to the network it just failed to. Other times I will have to reboot.
I don't know where to look for more details about what wicd is doing, or why it is doing this. It gets a bit concerning when I go to a client's office and I can't connect to their network, though for about 10 minutes sometimes. So I'd really like to get some help on this one.
Thanks
Offline
I use wicd for the roaming feature, but if you reuse common networks over and over again, you can use netctl profiles. Of course, wicd and netctl won't operate over each other (primarily for the same interface). If you aren't using dhclient, I would recommend using it. There was some documents that stated that dhclient was better with wicd than dhcpcd, but this may be across the board.
Last edited by nomorewindows (2013-09-20 15:11:58)
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
That's quite an interesting problem... Just some questions for better understanding:
0. Does wicd-curses behave like the GUI with respect to that?
1. If you uncheck the autoconnect option, reboot and try to connect manually, does wicd give you the same error?
2. Does the problem occur with, say, WEP-protected networks?
Offline
Wicd-curses does the same and auto-connect doesn't make any difference.
In the end I uninstalled it and I'm now using netcl via wifi-menu
Offline