Issue connecting to wifi with dhcpcd [solved]

frig · 2013-08-17 12:19:51

Initial Problem:
Hello, i cant connect to my home-wifi from my notebook using a wireless chip from intel (specification follows). Connecting from a fedora installation works flawlessly.
wpa_supplicant errors occasionaly with error-code 0 and 3 from the userside. I am currently on my way to work thus i would appreciate if someone posts the required logs debug so i can acquire them once i'am back at home.
Thanks in advance, the hardware specifications and kernel etc. will follow once i'am back at home. Further information >> it occured first after a wpa_supplicant update but i cant remembrr it happened directly afterwards.

wpa_supplicant -d -i wlan0 -c /etc/wpa_supplicant.conf

uri: http://pastebin.com/YELsscA8
after around 30 seconds i start in dhcpcd, trying wpa_supplicant -D XXX doesn't provide noteworthy different output, at least i think so

dhcpcd -dd wlan0

http://pastebin.com/hsKhuDHy

Solution:
Switching from dhcpcd to dhclient to assign the ip-address through dhcp did the trick.

Last edited by frig (2013-08-18 23:00:00)

Trilby · 2013-08-17 12:22:35

The wireless page on the wiki has the commands which will provide useful diagnostic information. When you get home follow that page including the manual connection steps, and post the output of each of the commands here.

nomorewindows · 2013-08-17 12:46:29

Do you have the firmware installed?

WonderWoofy · 2013-08-17 13:31:54

Firmware is indeed important, but these days, the linux package depends on it.

@OP, what specifically is the hardware in your machine? Can you do lapci -vnn and then post just the part about the wireless card? (That command will print info about all your pci devices).

frig · 2013-08-17 13:43:10

i actually connect manually through wpa_supplicant and dhcpcd (using a simple !#/bin/sh script) and the wireless wikipage didn't provide sufficient troubleshooting information as well as i couldn't find any realy helpful pages on google or ddg thus asking in the forum. i'll post everything you asked once i'm home. the linux-firmware package is always installed and i actually used intel-ucode until it was discluded as it went into linux-firmware(?)

Trilby · 2013-08-17 14:25:21

frig wrote:

the wireless wikipage didn't provide sufficient troubleshooting information

Huh? It didn't provide information that helped you - but if you share that information we might be able to help by using that information; if you don't, we can't.

Last edited by Trilby (2013-08-17 14:25:39)

nomorewindows · 2013-08-17 15:50:20

frig wrote:

i actually connect manually through wpa_supplicant and dhcpcd (using a simple !#/bin/sh script) and the wireless wikipage didn't provide sufficient troubleshooting information as well as i couldn't find any realy helpful pages on google or ddg thus asking in the forum. i'll post everything you asked once i'm home. the linux-firmware package is always installed and i actually used intel-ucode until it was discluded as it went into linux-firmware(?)

You most likely need firmware related to the wireless card (most likely ipw2x00-fw).

frig · 2013-08-18 00:02:07

back at home

outputs:

lspci -vnn

http://pastebin.com/i6Eqdf00
pasted everything, just in case

wpa_supplicant -d -i wlan0 -c /etc/wpa_supplicant.conf

uri: http://pastebin.com/YELsscA8
after around 30 seconds i start in dhcpcd, trying wpa_supplicant -D XXX doesn't provide noteworthy different output, at least i think so

dhcpcd -dd wlan0

http://pastebin.com/hsKhuDHy

dmesg | tail

http://pastebin.com/DbE69KHV

lsmod

http://pastebin.com/dbvSbpHz

iwconfig wlan0
wlan0     IEEE 802.11bgn  ESSID:off/any  
          Mode:Managed  Frequency:2.462 GHz  Access Point: Not-Associated   
          Tx-Power=15 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off

uname -a
Linux nfrig 3.10.6-2-ARCH

wpa_supplicant --version
v2.0

dhcpcd --version
6.0.5

Huh? It didn't provide information that helped you

I tried all the wiki troubleshooting-thingies, most of them didn't matter before a certain update (i cant actually remember >.<) but i tried them once again and didn't notice any difference.

Just to make it clear, the network itself is not the problem, since connecting from a broadcom-wireless (my wife's arch-install) and from different mobilephones and any other wireless-enabled gadgets is working absolutely flawlessly.

I installed the ipw2100-fw package, i tried compiling a kernel for my specific notebook but i just didn't had the time to do it excessive enough to be productive, thus i'm using the generic-kernel as described above. Powersaving is turned off on the wireless adapter. Broken hardware is probably no issue because the mainboard was replaced around 2 months ago and as it's working on several other linux-distribution.
I have to admit, i probably wouldn't bother, if archlinux wasn't that much of a comfort in contrary to those 'user-friendly' distributions.
Oh and wired works like it should but since it's another adapter it probably doesn't matter at all.

WonderWoofy · 2013-08-18 00:12:47

nomorewindows wrote:

You most likely need firmware related to the wireless card (most likely ipw2x00-fw).

How did you come to assume what the OP "most likely" needs when there was still no mention of the wireless card model in question?!

Trilby · 2013-08-18 01:05:13

frig, there is a lot of information there, but still not the step-by-step procedure in the manual connection steps, so this leaves many questions. Your wpa_supplicant.conf may not be properly formatted or have the right information, or it could be any number of other things.

So here's a step by step that should provide some information:

ip link set wlan0 down
killall dhcpcd wlan0
ip link set wlan0 up
ip a
wpa_passphrase <yournetwork> <yourpassphrase> > tmp.wpa
wpa_supplicant -B -i wlan0 -c tmp.wpa
ip a
dhcpcd wlan0

Run those, and post any output or errors. Just saying you ran these and you "didn't notice any difference" doesn't help us. The idea of going through the manual steps is to get the output and see which step fails. So if you won't share that information I for one certainly can't help, and I'd be surprised if anyone else could.

Last edited by Trilby (2013-08-18 01:08:43)

frig · 2013-08-18 09:03:57

Manual procedure:

ip link set wlan0 down

killall dhcpcd wlan0
 dhcpcd: no process found
 wlan0: no process found

ip link set wlan0 up

ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:90:f5:d3:b9:ea brd ff:ff:ff:ff:ff:ff
    inet6 XXX scope global dynamic 
       valid_lft 40sec preferred_lft 30sec
    inet6 XXX scope link 
       valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether 4c:eb:42:90:98:9f brd ff:ff:ff:ff:ff:ff

wpa_passphrase "wanja" "passphrase" > /home/frig/bla.wpa

cat /home/frig/bla.wpa
network={
	ssid="wanja"
	#psk="passphrase"
	psk=00fd0b84ad0243a22cec2cbbbf3ecbe2db4206eb10fadf8cbf8901b7bf921476
}
#/etc/wpa_supplicant.conf looks the same because every entry is made through wpa_passphrase "SSID" "PASSPHRASE"

wpa_supplicant -B -i wlan0 -c /home/frig/bla.wpa
Successfully initialized wpa_supplicant

ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:90:f5:d3:b9:ea brd ff:ff:ff:ff:ff:ff
    inet6 XXX/64 scope global dynamic 
       valid_lft 37sec preferred_lft 27sec
    inet6 XXX/64 scope link 
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 4c:eb:42:90:98:9f brd ff:ff:ff:ff:ff:ff
    inet6 XXX/64 scope global dynamic 
       valid_lft 37sec preferred_lft 27sec
    inet6 XXX/64 scope link 
       valid_lft forever preferred_lft forever

dhcpcd wlan0
dhcpcd[1184]: version 6.0.5 starting
dhcpcd[1187]: wlan0: starting wpa_supplicant
dhcpcd[1184]: wlan0: waiting for carrier
dhcpcd[1184]: wlan0: carrier acquired
dhcpcd[1184]: wlan0: soliciting an IPv6 router
dhcpcd[1184]: wlan0: soliciting a DHCP lease
dhcpcd[1184]: wlan0: carrier lost
dhcpcd[1184]: wlan0: carrier acquired
dhcpcd[1184]: wlan0: soliciting an IPv6 router
dhcpcd[1184]: wlan0: soliciting a DHCP lease
dhcpcd[1184]: wlan0: carrier lost
dhcpcd[1184]: timed out
dhcpcd[1184]: exited

Sometimes the wireless_action_part of my statusbar shows green wireless (meaning its up and about to connect) but actually never acquiring a IP, i somehow think its dhcpcd/dhcp related since most of the time starting with dhcpcd wpa_supplicant starts to rescanning and disconnecting (output previous post).
The script i use to connect to my wireless is nothing more than a combination of the above used commands (except ip a and wpa_passphrase)

With kind regards,
frig

Strike0 · 2013-08-18 10:47:08

Executing wpa_supplicant with the background option does not produce particularly useful debugging output on the console. Better leave -B and use -d next time.

There seem to be a number of users with dhcpcd problems recently, and a number of options in the dhcpcd.conf file to try. But instead: what happens, if you use dhclient to request the IP or just assign it manually? Does the connection stay up?

frig · 2013-08-18 13:13:12

a debugging output of wpa_supplicant and dhcpcd is in my previous post (pastebin) using the same options except debugging.
I tried dhclient once because of your mentioned frequently arriving errors, resulting in no actual difference but i'll try once again. I'll try manually assigned ip's once i'm home. I didn't do this before because my cheap wireless-router makes trouble with assigned ip's and dhcp-assigned ip's.

With kind regards,
frig

Last edited by frig (2013-08-18 13:15:17)

nomorewindows · 2013-08-18 14:11:47

WonderWoofy wrote:

nomorewindows wrote:
You most likely need firmware related to the wireless card (most likely ipw2x00-fw).
How did you come to assume what the OP "most likely" needs when there was still no mention of the wireless card model in question?!

Never mind...why does the ipw come in a separate package than iwlwifi firmware comes in linux-firmware? So the firmware is in linux-firmware not ipw. Intel must've switched over at some time later. Anyhow, we need more than just dmesg|tail. We need to see the entire dmesg, so we can find the line that states that the firmware did in fact load.

frig · 2013-08-18 15:33:31

Well i'm somehow a bit disappointed.
First: The problem is solved.
How i did it: I actually just killed all dhcpcd and wpa_supplicant PID's and changed the initialization script to use dhclient instead, and that just did the trick.
Thus it actually was a problem in dhcpcd. Thus my wireless works and was not actually related to anything else rather than a problem with dhcpcd.
I changed the first post and topic to resemble the actual problem.

Thanks for the fast help.

With kind regards,
frig

P.S.
I'm still interested in solving the issue with dhcpcd or at least the reason for the issue, so if still some hints are available i'm ready to check.

full dmesg output a try with dhcpcd included.

http://pastebin.com/dpD10r8g

Last edited by frig (2013-08-18 23:04:12)

nomorewindows · 2013-08-18 23:18:08

I use wicd and it seems like I switched to dhclient some time ago.
From the looks of it, intel-ucode is not updating anything for your processor. If it were, there would be a line that states that there is an updated revision.

Last edited by nomorewindows (2013-08-18 23:20:45)

frig · 2013-08-18 23:35:15

oh i actually forgot to mention, that the dmesg output is from a fresh install and i did not install the ucode package until now. >.<

Arch Linux

#1 2013-08-17 12:19:51

Issue connecting to wifi with dhcpcd [solved]

#2 2013-08-17 12:22:35

Re: Issue connecting to wifi with dhcpcd [solved]

#3 2013-08-17 12:46:29

Re: Issue connecting to wifi with dhcpcd [solved]

#4 2013-08-17 13:31:54

Re: Issue connecting to wifi with dhcpcd [solved]

#5 2013-08-17 13:43:10

Re: Issue connecting to wifi with dhcpcd [solved]

#6 2013-08-17 14:25:21

Re: Issue connecting to wifi with dhcpcd [solved]

#7 2013-08-17 15:50:20

Re: Issue connecting to wifi with dhcpcd [solved]

#8 2013-08-18 00:02:07

Re: Issue connecting to wifi with dhcpcd [solved]

#9 2013-08-18 00:12:47

Re: Issue connecting to wifi with dhcpcd [solved]

#10 2013-08-18 01:05:13

Re: Issue connecting to wifi with dhcpcd [solved]

#11 2013-08-18 09:03:57

Re: Issue connecting to wifi with dhcpcd [solved]

#12 2013-08-18 10:47:08

Re: Issue connecting to wifi with dhcpcd [solved]

#13 2013-08-18 13:13:12

Re: Issue connecting to wifi with dhcpcd [solved]

#14 2013-08-18 14:11:47

Re: Issue connecting to wifi with dhcpcd [solved]

#15 2013-08-18 15:33:31

Re: Issue connecting to wifi with dhcpcd [solved]

#16 2013-08-18 23:18:08

Re: Issue connecting to wifi with dhcpcd [solved]

#17 2013-08-18 23:35:15

Re: Issue connecting to wifi with dhcpcd [solved]

Board footer