can not connect to wireless networks

Asked by Giulio Roman

I run a fresh installed Gentoo system and have already tried to get help from my community, but unsuccessfully; here is the url of my post into the official Gentoo discussion forum: http://forums.gentoo.org/viewtopic-t-944500.html
My problem is the following:

I log in as root and start X, then execute "wicd-client" in the xterm.
I get immediately these two differents pop-up error messages:
1) Could not connect to wicd's D-Bus interface. Check the wicd log for error messages
2) The wicd daemon has shut down. The UI will not function properly until it is restarted.

I close the wicd-client window and need also to interrupt the execution of wicd-client by pressing CTRL+C into the xterm

I try:
# rc-update show | grep dbus
And get:
                 dbus | default

Then I try:
# ps aux | grep dbus
And get:
101 12350 0.0 0.1 3020 1064 ? Ss 17:06 0:00 /usr/bin/dbus-daemon --system
root 12528 0.0 0.0 3540 544 tty1 S 17:06 0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session
root 12529 0.0 0.0 3004 988 ? Ss 17:06 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session

Then, I try to restart the wicd daemon from xterm, but I get this error:
"It seems like the daemon is already running. If it is not, please remove /var/run/wicd/wicd.pid and try again"

I write:
# ps aux | grep wicd
And get:
root 12583 4.7 0.7 23204 7216 ? S 17:07 0:02 /usr/bin/python2 -O /usr/share/wicd/daemon/wicd-daemon.py
root 12587 0.8 0.7 12824 7756 ? S 17:07 0:00 /usr/bin/python2 -O /usr/share/wicd/daemon/monitor.py

I kill the first process (i.e. 12583) and then can successfully restart the wicd daemon ("wicd" in xterm).

After that I re-open wicd-client without getting errors.

When I try to connect any network, both secured and unsecured, on the bottom of the wicd-client window I see the messages of the connection attempt ("autenticating...", "obtaining ip address", "done connecting"), but at the end the message displayed is "Not connected", and not "Connected to MY-SSID 192.168.1.125", like it happens with Wicd on another Linux distro running on the same machine.

I can't neither connect with wicd-curses.

Here is the tail of /var/log/wicd/wicd.log
http://pastebin.com/np8TWAWb

Thanks

Question information

Language:
English Edit question
Status:
Expired
For:
wicd Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said :
#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Giulio Roman (leonixyz) said :
#2

My connection works at startup since I edited the wpa_supplicant.conf configuration file, and inserted SSID and PSK manually...

But Wicd stil doesn't work...

Revision history for this message
David Paleino (dpaleino) said :
#3

How did you edit it?

Given this update, I guess the problem is to be found in the choice of the encryption template.

Still, I don't understand where your problem lies.

Revision history for this message
Giulio Roman (leonixyz) said :
#4

i created this file /etc/wpa_supplicant/wpa_supplicant.conf

---------------------------------------------------------------
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=1
network={
  ssid="MY-SSID"
  psk="MY-PSK"
  priority=5
}
---------------------------------------------------------------

and added these commands at startup
--------------------------------------
ifconfig wlan0 up
dhcpcd wlan0
wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf
--------------------------------------

but if I try to connect without this, just with Wicd, i get always the same error.
I've like to keep wicd because it's more flexible if I travel I don't need always to edit configuration files and launch commands into the shell...

Revision history for this message
David Paleino (dpaleino) said :
#5

And what encryption template is WICD (or you ;)) trying to use?

Did you try both "WPA 1/2 (Passphrase)" and "WPA 1/2 (Hex [0-9/A-F])"? You could also try "WPA 1/2 (Preshared Hex Key)".

Unfortunately, the current encryption template system is a bit inflexible, so if you need one particular parameter you must create a whole new template. I plan to change that in the future though.

Ciao,
David

Revision history for this message
Launchpad Janitor (janitor) said :
#6

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.