Arch Linux

Kirito

Member

Registered: 2013-05-15

Posts: 17

[Solved]Lost wireless connectivity. Wicd not connecting after shutdown

Earlier today I was editing my resolv.conf file to add custom dns and it wasn't taking so I cleared xfce4 session cache and rebooted. Ever since, my wireless hasn't worked(yes, I reverted the changes but that didn't help). After a while of trying to fix it I  just ended up uninstalling all the networking programs that didn't come with the base install (networkmanager, wpa_supplicant, etc)and starting over from step 1 of configuration. Eventually, I ended up getting a wireless connection after a reboot(hurray! at least for a while)

I am using wicd on xfce4 and it had connected just fine the first time. I shutdown and booted back up a few minutes later and then nothing again. It detects the network, the key is right but it doesn't connect. Wired works fine though.

Here is the log output:

2013/05/19 19:46:11 :: DHCP connection successful
2013/05/19 19:46:11 :: not verifying
2013/05/19 19:46:11 :: Connecting thread exiting.
2013/05/19 19:46:15 :: Sending connection attempt result success
2013/05/19 19:46:15 :: Autoconnecting...
2013/05/19 19:46:15 :: No wired connection present, attempting to autoconnect to wireless network
2013/05/19 19:46:17 :: trying to automatically connect to...linksys
2013/05/19 19:46:17 :: Connecting to wireless network linksys
2013/05/19 19:46:18 :: Putting interface down
2013/05/19 19:46:18 :: Releasing DHCP leases...
2013/05/19 19:46:18 :: Setting false IP...
2013/05/19 19:46:18 :: Stopping wpa_supplicant
2013/05/19 19:46:18 :: Flushing the routing table...
2013/05/19 19:46:18 :: Putting interface up...
2013/05/19 19:46:20 :: Generating psk...
2013/05/19 19:46:20 :: Attempting to authenticate...
2013/05/19 19:46:21 :: Running DHCP with hostname Excalibur
2013/05/19 19:46:21 :: dhcpcd[2188]: sending commands to master dhcpcd process
2013/05/19 19:46:21 :: 
2013/05/19 19:46:21 :: 
2013/05/19 19:46:21 :: DHCP connection successful
2013/05/19 19:46:21 :: not verifying
2013/05/19 19:46:21 :: Connecting thread exiting.
2013/05/19 19:46:25 :: Sending connection attempt result success
2013/05/19 19:46:51 :: Connecting to wireless network linksys
2013/05/19 19:46:51 :: Putting interface down
2013/05/19 19:46:51 :: Releasing DHCP leases...
2013/05/19 19:46:51 :: Setting false IP...
2013/05/19 19:46:51 :: Stopping wpa_supplicant
2013/05/19 19:46:51 :: Flushing the routing table...
2013/05/19 19:46:51 :: Putting interface up...
2013/05/19 19:46:53 :: Generating psk...
2013/05/19 19:46:53 :: Attempting to authenticate...
2013/05/19 19:46:54 :: Running DHCP with hostname Excalibur
2013/05/19 19:46:54 :: dhcpcd[2902]: sending commands to master dhcpcd process
2013/05/19 19:46:54 :: 
2013/05/19 19:46:54 :: 
2013/05/19 19:46:54 :: DHCP connection successful
2013/05/19 19:46:54 :: not verifying
2013/05/19 19:46:54 :: Connecting thread exiting.

It says it has a sucessful dhcp connection but then exits? I also tested this with my phone hotspot using WPA2 as well, just like my wifi. It does the same thing, only the app on the phone shows a successful connection to it, but internet still doesn't work. Any idea where to go next?

Last edited by Kirito (2013-05-20 03:15:09)

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: [Solved]Lost wireless connectivity. Wicd not connecting after shutdown

It says that it is sending commands to the master dhcpcd process.  I take this to mean you have something else that is also trying to control networking.  This is probably dhcpcd.service or dhcpcd@<network>.service.

Check the output of "systemctl --type=service" and see what else you may have running that might conflict.

Kirito

Member

Registered: 2013-05-15

Posts: 17

Re: [Solved]Lost wireless connectivity. Wicd not connecting after shutdown

It says that it is sending commands to the master dhcpcd process.  I take this to mean you have something else that is also trying to control networking.  This is probably dhcpcd.service or dhcpcd@<network>.service.

Check the output of "systemctl --type=service" and see what else you may have running that might conflict.

Sure enough. Boy to I feel pretty dumb right now lol. Thought I had it disabled but I guess I only stopped it before. Thanks for the prompt help, sorry if this was clutter x.x