Re: [gentoo-user] wicd will not connect to wireless network
On Sun, Feb 26, 2012 at 07:09:26PM +0100, Penguin Lover Willie WY Wong squawked: I wonder if it would be advisable to file a bug to have wicd provide net? (Is there any reason why this would be a bad idea?) Ah, in fact it seems that having wicd provide net is already in the works: https://bugs.gentoo.org/show_bug.cgi?id=405775 W -- Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire et vice versa ~~~ I. Newton
Re: [gentoo-user] wicd will not connect to wireless network
On 26 February 2012 17:00, Dan Johansson dan.johans...@dmj.nu wrote: On Sunday 26 February 2012 13.43:13 Dan Johansson wrote: On Sunday 26 February 2012 10.52:58 Willie WY Wong wrote: You guys are almost certainly running into the same problem as the one I mentioned in the thread I just started. Try `pkill dhcpcd` and associate again. Unfortunately I couldn't figure out why all of a sudden dhcpcd decides to start on boot. Yes, that was it, killing the dhcpcd made it possible to bring the interface up and associate with the AP. As openrc was one of the packages upgraded yesterday (0.9.8.4 - 0.9.9.1) I assume (guess) that is why dhcpcd gets started at boot. Now I just have to figure out a way to stop this from happening. The problems seems to be that dhcpcd was started automatically as soon as a service needed the network - in my case dhcpcd was started due to /etc/init.d/sshd. At the moment I have solved it with putting rc_dhcpcd_provide=!net in /etc/rc.conf which prevents dhcpcd to start when sshd is started and wicd can now do it's magic. Ah, I could really have done with this thread earlier, but gmail had decided that it was spam :-/ What is strange is that it seems to work for some networks, but not for others, and I can't figure out how to predict on which dhcpd with succeed and on which it will not. I have access to three APs here (each with different SSIDs), and I can only connect to one of them; the other two have the dhcp failure. Very strange.
Re: [gentoo-user] wicd will not connect to wireless network
On Mon, 27 Feb 2012 15:58:59 + James Broadhead jamesbroadh...@gmail.com wrote: On 26 February 2012 17:00, Dan Johansson dan.johans...@dmj.nu wrote: On Sunday 26 February 2012 13.43:13 Dan Johansson wrote: On Sunday 26 February 2012 10.52:58 Willie WY Wong wrote: You guys are almost certainly running into the same problem as the one I mentioned in the thread I just started. Try `pkill dhcpcd` and associate again. Unfortunately I couldn't figure out why all of a sudden dhcpcd decides to start on boot. Yes, that was it, killing the dhcpcd made it possible to bring the interface up and associate with the AP. As openrc was one of the packages upgraded yesterday (0.9.8.4 - 0.9.9.1) I assume (guess) that is why dhcpcd gets started at boot. Now I just have to figure out a way to stop this from happening. The problems seems to be that dhcpcd was started automatically as soon as a service needed the network - in my case dhcpcd was started due to /etc/init.d/sshd. At the moment I have solved it with putting rc_dhcpcd_provide=!net in /etc/rc.conf which prevents dhcpcd to start when sshd is started and wicd can now do it's magic. Ah, I could really have done with this thread earlier, but gmail had decided that it was spam :-/ What is strange is that it seems to work for some networks, but not for others, and I can't figure out how to predict on which dhcpd with succeed and on which it will not. I have access to three APs here (each with different SSIDs), and I can only connect to one of them; the other two have the dhcp failure. Very strange. Yes, it gets curioser and curioser. I reported yesterday that kernel-3.2.5 worked fine with openrc-0.9.9.* Well actually it doesn't work fine, it's sorta flakey. Takes a while to get a DHCP address on wireless, often drops the connection but is solid on wired. I added provide net to the depend() section of /etc/init.d/wicd and all those issues went away. Still haven't tested on kernel-3.2.6 yet, have too many things open that must stay open to be able to reboot right now. Whatever the root cause is, it's certainly not obvious. -- Alan McKinnnon alan.mckin...@gmail.com
Re: [gentoo-user] wicd will not connect to wireless network
On Sun, 26 Feb 2012 10:19:56 +0100 Dan Johansson dan.johans...@dmj.nu wrote: Hi, After running an update yesterday (about 50 packages) on my ~x86 laptop, wicd stopped working, and no wicd was not updated neither was any other network related packages. Today after a reboot my wireless network refused to start from wicd, starting it manually works. This is a part of the wicd.log: 2012/02/26 09:53:51 :: enctype is wpa 2012/02/26 09:53:51 :: Generating psk... 2012/02/26 09:53:51 :: ['/usr/bin/wpa_passphrase', 'DMJ', 'Do_not_care_about_this'] 2012/02/26 09:53:51 :: Attempting to authenticate... 2012/02/26 09:53:51 :: ['wpa_supplicant', '-B', '-i', 'wlan0', '-c', '/var/lib/wicd/configurations/000f90ac2780', '-D', dbus.String(u'wext', variant_level=1)] 2012/02/26 09:53:51 :: ['iwconfig', 'wlan0', 'essid', '--', 'DMJ'] 2012/02/26 09:53:51 :: iwconfig wlan0 channel 13 2012/02/26 09:53:51 :: iwconfig wlan0 ap 00:0F:90:AC:27:80 2012/02/26 09:53:51 :: WPA_CLI RESULT IS DISCONNECTED 2012/02/26 09:53:52 :: WPA_CLI RESULT IS COMPLETED 2012/02/26 09:53:52 :: Running DHCP with hostname mutgdjoda1 2012/02/26 09:53:52 :: /sbin/dhcpcd -h mutgdjoda1 --noipv4ll wlan0 2012/02/26 09:53:52 :: dhcpcd[12434]: sending commands to master dhcpcd process 2012/02/26 09:53:52 :: 2012/02/26 09:53:52 :: 2012/02/26 09:53:52 :: DHCP connection successful 2012/02/26 09:53:52 :: not verifying 2012/02/26 09:53:52 :: Connecting thread exiting. 2012/02/26 09:53:52 :: ifconfig wlan0 2012/02/26 09:53:52 :: IP Address is: None 2012/02/26 09:53:52 :: Sending connection attempt result success 2012/02/26 09:53:52 :: ifconfig eth0 2012/02/26 09:53:52 :: iwconfig wlan0 2012/02/26 09:53:52 :: Forced disconnect on 2012/02/26 09:53:52 :: /sbin/dhcpcd -k wlan0 Running the commands by hand everything works: # wpa_supplicant -B -i wlan0 -c /var/lib/wicd/configurations/000f90ac2780 -D wext # wpa_cli status Selected interface 'wlan0' bssid=00:0f:90:ac:27:80 ssid=DMJ id=0 mode=station pairwise_cipher=TKIP group_cipher=TKIP key_mgmt=WPA-PSK wpa_state=COMPLETED ip_address=192.168.1.21 # /sbin/dhcpcd -h mutgdjoda1 --noipv4ll wlan0 dhcpcd[28962]: sending commands to master dhcpcd process # ifconfig wlan0 wlan0: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500 metric 1 inet 192.168.1.21 netmask 255.255.255.0 broadcast 192.168.1.255 ether 00:18:de:e1:c9:71 txqueuelen 1000 (Ethernet) RX packets 128 bytes 21081 (20.5 KiB) RX errors 0 dropped 20 overruns 0 frame 0 TX packets 143 bytes 24546 (23.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 And my wireless connection works! Anny suggestions what's wrong? Regards, I'm having similar issues with an Intel N6300 since a reboot. In my case it fails with this: [ 76.232020] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (reason=3) Which means something deauthed the connection in the meantime. This happens with kernel 3.2.6, but rebooting into 3.2.5 works just fine. It doesn't make a whole lot of sense. If you are also running 3.2.6, try 3.2.5 - if that works we are onto something. -- Alan McKinnnon alan.mckin...@gmail.com
Re: [gentoo-user] wicd will not connect to wireless network
On Sun, Feb 26, 2012 at 11:34:01AM +0200, Penguin Lover Alan McKinnon squawked: On Sun, 26 Feb 2012 10:19:56 +0100 Dan Johansson dan.johans...@dmj.nu wrote: After running an update yesterday (about 50 packages) on my ~x86 laptop, wicd stopped working, and no wicd was not updated neither was any other network related packages. Today after a reboot my wireless network refused to start from wicd, starting it manually works. This is a part of the wicd.log: I'm having similar issues with an Intel N6300 since a reboot. In my case it fails with this: [ 76.232020] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (reason=3) Which means something deauthed the connection in the meantime. This happens with kernel 3.2.6, but rebooting into 3.2.5 works just fine. You guys are almost certainly running into the same problem as the one I mentioned in the thread I just started. Try `pkill dhcpcd` and associate again. Unfortunately I couldn't figure out why all of a sudden dhcpcd decides to start on boot. Cheers, W -- Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire et vice versa ~~~ I. Newton
Re: [gentoo-user] wicd will not connect to wireless network
On Sunday 26 February 2012 10.52:58 Willie WY Wong wrote: On Sun, Feb 26, 2012 at 11:34:01AM +0200, Penguin Lover Alan McKinnon squawked: On Sun, 26 Feb 2012 10:19:56 +0100 Dan Johansson dan.johans...@dmj.nu wrote: After running an update yesterday (about 50 packages) on my ~x86 laptop, wicd stopped working, and no wicd was not updated neither was any other network related packages. Today after a reboot my wireless network refused to start from wicd, starting it manually works. This is a part of the wicd.log: I'm having similar issues with an Intel N6300 since a reboot. In my case it fails with this: [ 76.232020] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (reason=3) Which means something deauthed the connection in the meantime. This happens with kernel 3.2.6, but rebooting into 3.2.5 works just fine. You guys are almost certainly running into the same problem as the one I mentioned in the thread I just started. Try `pkill dhcpcd` and associate again. Unfortunately I couldn't figure out why all of a sudden dhcpcd decides to start on boot. Yes, that was it, killing the dhcpcd made it possible to bring the interface up and associate with the AP. As openrc was one of the packages upgraded yesterday (0.9.8.4 - 0.9.9.1) I assume (guess) that is why dhcpcd gets started at boot. Now I just have to figure out a way to stop this from happening. -- Dan Johansson, http://www.dmj.nu *** This message is printed on 100% recycled electrons! ***
Re: [gentoo-user] wicd will not connect to wireless network
On Sunday 26 February 2012 13.43:13 Dan Johansson wrote: On Sunday 26 February 2012 10.52:58 Willie WY Wong wrote: On Sun, Feb 26, 2012 at 11:34:01AM +0200, Penguin Lover Alan McKinnon squawked: On Sun, 26 Feb 2012 10:19:56 +0100 Dan Johansson dan.johans...@dmj.nu wrote: After running an update yesterday (about 50 packages) on my ~x86 laptop, wicd stopped working, and no wicd was not updated neither was any other network related packages. Today after a reboot my wireless network refused to start from wicd, starting it manually works. This is a part of the wicd.log: I'm having similar issues with an Intel N6300 since a reboot. In my case it fails with this: [ 76.232020] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (reason=3) Which means something deauthed the connection in the meantime. This happens with kernel 3.2.6, but rebooting into 3.2.5 works just fine. You guys are almost certainly running into the same problem as the one I mentioned in the thread I just started. Try `pkill dhcpcd` and associate again. Unfortunately I couldn't figure out why all of a sudden dhcpcd decides to start on boot. Yes, that was it, killing the dhcpcd made it possible to bring the interface up and associate with the AP. As openrc was one of the packages upgraded yesterday (0.9.8.4 - 0.9.9.1) I assume (guess) that is why dhcpcd gets started at boot. Now I just have to figure out a way to stop this from happening. The problems seems to be that dhcpcd was started automatically as soon as a service needed the network - in my case dhcpcd was started due to /etc/init.d/sshd. At the moment I have solved it with putting rc_dhcpcd_provide=!net in /etc/rc.conf which prevents dhcpcd to start when sshd is started and wicd can now do it's magic. -- Dan Johansson, http://www.dmj.nu *** This message is printed on 100% recycled electrons! ***
Re: [gentoo-user] wicd will not connect to wireless network
On Sun, Feb 26, 2012 at 06:00:46PM +0100, Penguin Lover Dan Johansson squawked: Yes, that was it, killing the dhcpcd made it possible to bring the interface up and associate with the AP. As openrc was one of the packages upgraded yesterday (0.9.8.4 - 0.9.9.1) I assume (guess) that is why dhcpcd gets started at boot. Now I just have to figure out a way to stop this from happening. The problems seems to be that dhcpcd was started automatically as soon as a service needed the network - in my case dhcpcd was started due to /etc/init.d/sshd. At the moment I have solved it with putting rc_dhcpcd_provide=!net in /etc/rc.conf which prevents dhcpcd to start when sshd is started and wicd can now do it's magic. I wonder if it would be advisable to file a bug to have wicd provide net? (Is there any reason why this would be a bad idea?) Cheers, W -- Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire et vice versa ~~~ I. Newton
