Wifi connects but doesn't work

preschema · 2015-01-25 19:26:12

I'm unable to connect to the internet through wifi on my new laptop. That is, I am able to connect to the network, but not to the internet. It seems that I don't even get an IP address. I am able to connect using ethernet though. And I know it's not an issue with the router because I am able to connect fine on three other devices through wifi.

For example, using netctl:

[adeel@deglise ~]$ sudo netctl start wlp2s0-o2-WLAN46 
[adeel@deglise ~]$ ping google.com
ping: unknown host google.com
[adeel@deglise ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether 20:89:84:fc:f2:05 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
    link/ether 48:d2:24:98:5c:f7 brd ff:ff:ff:ff:ff:ff

I'm pretty sure that wifi did work once, just after rebooting, but I never got it to work again. Before switching to netctl, I was using network-manager-applet, and that wasn't working either: it would show my network in the list, but nothing would happen after clicking the connect button (not even a password prompt).

Here is some more information that may or not be relevant.

The output of lspci -k is

...
02:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
	Subsystem: Lenovo Device 3218
	Kernel driver in use: ath9k
	Kernel modules: ath9k

The output of dmesg | grep wlp | tail -20 is:

[97653.956892] wlp2s0: send auth to 88:03:55:f7:08:66 (try 1/3)
[97653.958805] wlp2s0: authenticated
[97653.961399] wlp2s0: associate with 88:03:55:f7:08:66 (try 1/3)
[97653.989598] wlp2s0: RX AssocResp from 88:03:55:f7:08:66 (capab=0x411 status=0 aid=2)
[97653.989755] wlp2s0: associated
[97665.963355] wlp2s0: deauthenticated from 88:03:55:f7:08:66 (Reason: 3=DEAUTH_LEAVING)
[97667.043509] wlp2s0: authenticate with 88:03:55:f7:08:66
[97667.063940] wlp2s0: send auth to 88:03:55:f7:08:66 (try 1/3)
[97667.066002] wlp2s0: authenticated
[97667.069018] wlp2s0: associate with 88:03:55:f7:08:66 (try 1/3)
[97667.097352] wlp2s0: RX AssocResp from 88:03:55:f7:08:66 (capab=0x411 status=0 aid=2)
[97667.097609] wlp2s0: associated
[97680.078664] wlp2s0: deauthenticated from 88:03:55:f7:08:66 (Reason: 3=DEAUTH_LEAVING)
[97681.154662] wlp2s0: authenticate with 88:03:55:f7:08:66
[97681.177104] wlp2s0: send auth to 88:03:55:f7:08:66 (try 1/3)
[97681.179152] wlp2s0: authenticated
[97681.179816] wlp2s0: associate with 88:03:55:f7:08:66 (try 1/3)
[97681.212189] wlp2s0: RX AssocResp from 88:03:55:f7:08:66 (capab=0x411 status=0 aid=2)
[97681.212526] wlp2s0: associated
[97690.163979] wlp2s0: deauthenticated from 88:03:55:f7:08:66 (Reason: 3=DEAUTH_LEAVING)

Thanks in advance for any suggestions.

Last edited by preschema (2015-01-25 19:29:33)

tomk · 2015-01-25 19:58:53

I don't see anything there that would lead to the conclusion that you can connect to the network - why do you think that? Your dmesg excerpt does show various "associated" messages, but they are always followed by "deauthenticated" ones.

Anyway, standard wifi debugging advice is to disable any network utilities that may be installed - netctl, networkmanager, etc - and configure the connection manually. The details are available on the wiki's wifi page.

preschema · 2015-01-25 20:01:46

Well, the output of ip link seemed to suggest that the connection was up, but I guess I'm reading it wrong. I believe I've tried doing it manually as well, but let me try again and post the results.

Head_on_a_Stick · 2015-01-25 20:09:27

Which desktop environment/window manager are you using?

Based on these threads, you may have to install gnome-keyring if you're using GNOME or Cinnamon.

preschema · 2015-01-25 20:25:37

Head_on_a_Stick wrote:

Which desktop environment/window manager are you using?
Based on these threads, you may have to install gnome-keyring if you're using GNOME or Cinnamon.

I do have gnome-keyring installed.

So I've followed on the manual instructions on the wiki with the same result (apparent connection but no ping):

[root@deglise ~]
# wpa_supplicant -D nl80211,wext -i wlp2s0 -c <(wpa_passphrase "o2-WLAN46" "XXXXXXXXXXXXXXXXX")
Successfully initialized wpa_supplicant
wlp2s0: SME: Trying to authenticate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Trying to associate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Associated with 88:03:55:f7:08:66
wlp2s0: WPA: Key negotiation completed with 88:03:55:f7:08:66 [PTK=CCMP GTK=CCMP]
wlp2s0: CTRL-EVENT-CONNECTED - Connection to 88:03:55:f7:08:66 completed [id=0 id_str=]
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=88:03:55:f7:08:66 reason=3
wlp2s0: SME: Trying to authenticate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Trying to associate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Associated with 88:03:55:f7:08:66
wlp2s0: WPA: Key negotiation completed with 88:03:55:f7:08:66 [PTK=CCMP GTK=CCMP]
wlp2s0: CTRL-EVENT-CONNECTED - Connection to 88:03:55:f7:08:66 completed [id=0 id_str=]
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=88:03:55:f7:08:66 reason=3
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp2s0: SME: Trying to authenticate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Trying to associate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Associated with 88:03:55:f7:08:66
wlp2s0: WPA: Key negotiation completed with 88:03:55:f7:08:66 [PTK=CCMP GTK=CCMP]
wlp2s0: CTRL-EVENT-CONNECTED - Connection to 88:03:55:f7:08:66 completed [id=0 id_str=]
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=88:03:55:f7:08:66 reason=3
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp2s0: SME: Trying to authenticate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Trying to associate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Associated with 88:03:55:f7:08:66
wlp2s0: WPA: Key negotiation completed with 88:03:55:f7:08:66 [PTK=CCMP GTK=CCMP]
wlp2s0: CTRL-EVENT-CONNECTED - Connection to 88:03:55:f7:08:66 completed [id=0 id_str=]
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=88:03:55:f7:08:66 reason=3
wlp2s0: SME: Trying to authenticate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Trying to associate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Associated with 88:03:55:f7:08:66
wlp2s0: WPA: Key negotiation completed with 88:03:55:f7:08:66 [PTK=CCMP GTK=CCMP]
wlp2s0: CTRL-EVENT-CONNECTED - Connection to 88:03:55:f7:08:66 completed [id=0 id_str=]
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=88:03:55:f7:08:66 reason=3
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp2s0: SME: Trying to authenticate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Trying to associate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Associated with 88:03:55:f7:08:66
wlp2s0: WPA: Key negotiation completed with 88:03:55:f7:08:66 [PTK=CCMP GTK=CCMP]
wlp2s0: CTRL-EVENT-CONNECTED - Connection to 88:03:55:f7:08:66 completed [id=0 id_str=]
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=88:03:55:f7:08:66 reason=3
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp2s0: SME: Trying to authenticate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Trying to associate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Associated with 88:03:55:f7:08:66
wlp2s0: WPA: Key negotiation completed with 88:03:55:f7:08:66 [PTK=CCMP GTK=CCMP]
wlp2s0: CTRL-EVENT-CONNECTED - Connection to 88:03:55:f7:08:66 completed [id=0 id_str=]
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=88:03:55:f7:08:66 reason=3
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp2s0: SME: Trying to authenticate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Trying to associate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Associated with 88:03:55:f7:08:66
wlp2s0: WPA: Key negotiation completed with 88:03:55:f7:08:66 [PTK=CCMP GTK=CCMP]
wlp2s0: CTRL-EVENT-CONNECTED - Connection to 88:03:55:f7:08:66 completed [id=0 id_str=]

[root@deglise ~]# iw dev wlp2s0 link
Connected to 88:03:55:f7:08:66 (on wlp2s0)
	SSID: o2-WLAN46
	freq: 2432
	RX: 165903 bytes (1096 packets)
	TX: 1131 bytes (14 packets)
	signal: -31 dBm
	tx bitrate: 1.0 MBit/s

	bss flags:	short-slot-time
	dtim period:	1
	beacon int:	100
[root@deglise ~]# dhcpcd wlp2s0
dhcpcd[13922]: version 6.6.7 starting
dhcpcd[13922]: DUID 00:01:00:01:1c:46:69:8f:20:89:84:fc:f2:05
dhcpcd[13922]: wlp2s0: IAID 24:98:5c:f7
dhcpcd[13922]: wlp2s0: rebinding lease of 192.168.1.115
dhcpcd[13922]: wlp2s0: invalid UDP packet from 87.240.176.20
dhcpcd[13922]: wlp2s0: soliciting an IPv6 router
dhcpcd[13922]: wlp2s0: Router Advertisement from fe80::1
dhcpcd[13922]: wlp2s0: leased 192.168.1.115 for 604800 seconds
dhcpcd[13922]: wlp2s0: adding route to 192.168.1.0/24
dhcpcd[13922]: wlp2s0: adding default route via 192.168.1.1
dhcpcd[13922]: forked to background, child pid 13967
[root@deglise ~]# ping google.com
ping: unknown host google.com
[root@deglise ~]# ping 8.8.8.8
connect: Network is unreachable

jonny · 2015-01-25 20:27:45

Can be the same problem reported here?

Last edited by jonny (2015-01-25 20:29:13)

preschema · 2015-01-25 20:30:17

jonny wrote:

Can be the same problem reported here?

I'm not using NetworkManager, and I've had this problem for a couple weeks already.

tomk · 2015-01-25 20:58:57

Can you ping 192.168.1.1? Can you ping google's (or anybody's) IP address instead of their domain name?

preschema · 2015-01-25 21:00:18

tomk wrote:

Can you ping 192.168.1.1? Can you ping google's (or anybody's) IP address instead of their domain name?

No, I can't ping either 192.168.1.1 or 8.8.8.8.

Head_on_a_Stick · 2015-01-25 21:13:08

Try running the wpa_supplicant command without the `-D nl80211,wext` bit but with a `-B` flag.

It seems to connecting and then disconnecting with "reason=3" (whatever that means).

Similar problem, with a possible solution here:
http://askubuntu.com/questions/464597/1 … d-reason-3

preschema · 2015-01-25 21:32:24

I'm still getting the disconnections...

[root@deglise ~]# wpa_supplicant -i wlp2s0 -c <(wpa_passphrase "o2-WLAN46" "1234123412341234")
Successfully initialized wpa_supplicant
wlp2s0: SME: Trying to authenticate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Trying to associate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Associated with 88:03:55:f7:08:66
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=88:03:55:f7:08:66 reason=3 locally_generated=1
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp2s0: SME: Trying to authenticate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Trying to associate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Associated with 88:03:55:f7:08:66
wlp2s0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
wlp2s0: WPA: Could not verify EAPOL-Key MIC - dropping packet
wlp2s0: Authentication with 88:03:55:f7:08:66 timed out.
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=88:03:55:f7:08:66 reason=3 locally_generated=1
wlp2s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="o2-WLAN46" auth_failures=1 duration=10 reason=WRONG_KEY
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=88:03:55:f7:08:66 reason=3 locally_generated=1
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=88:03:55:f7:08:66 reason=3 locally_generated=1
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=88:03:55:f7:08:66 reason=3 locally_generated=1
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="o2-WLAN46"
wlp2s0: Associated with 88:03:55:f7:08:66
wlp2s0: WPA: Key negotiation completed with 88:03:55:f7:08:66 [PTK=CCMP GTK=CCMP]
wlp2s0: CTRL-EVENT-CONNECTED - Connection to 88:03:55:f7:08:66 completed [id=0 id_str=]
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=88:03:55:f7:08:66 reason=3 locally_generated=1
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp2s0: SME: Trying to authenticate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Trying to associate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Associated with 88:03:55:f7:08:66
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=88:03:55:f7:08:66 reason=3 locally_generated=1
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp2s0: SME: Trying to authenticate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Trying to associate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Associated with 88:03:55:f7:08:66
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=88:03:55:f7:08:66 reason=3 locally_generated=1
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlp2s0: SME: Trying to authenticate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Trying to associate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
wlp2s0: Associated with 88:03:55:f7:08:66
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=88:03:55:f7:08:66 reason=3 locally_generated=1
wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="o2-WLAN46" auth_failures=1 duration=10 reason=CONN_FAILED
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN

preschema · 2015-01-25 21:41:27

Hmm, I ran a killall wpa_supplicant and then

[root@deglise ~]# wpa_supplicant -i wlp2s0 -Dwext -c <(wpa_passphrase "o2-WLAN46" "1234123412341234")
Successfully initialized wpa_supplicant
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
wlp2s0: Trying to associate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
ioctl[SIOCSIWFREQ]: Device or resource busy
wlp2s0: Association request to the driver failed
wlp2s0: Associated with 88:03:55:f7:08:66
wlp2s0: WPA: Key negotiation completed with 88:03:55:f7:08:66 [PTK=CCMP GTK=CCMP]
wlp2s0: CTRL-EVENT-CONNECTED - Connection to 88:03:55:f7:08:66 completed [id=0 id_str=]
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=88:03:55:f7:08:66 reason=0
wlp2s0: Trying to associate with 88:03:55:f7:08:66 (SSID='o2-WLAN46' freq=2432 MHz)
ioctl[SIOCSIWFREQ]: Device or resource busy
wlp2s0: Association request to the driver failed
wlp2s0: Associated with 88:03:55:f7:08:66
wlp2s0: WPA: Key negotiation completed with 88:03:55:f7:08:66 [PTK=CCMP GTK=CCMP]
wlp2s0: CTRL-EVENT-CONNECTED - Connection to 88:03:55:f7:08:66 completed [id=0 id_str=]

it actually seems to stay connected. But it's still not working. I ran dhcpcd wlp2s0 and still can't ping. Does that mean dhcpcd is the problem now?

Last edited by preschema (2015-01-25 21:41:50)

Head_on_a_Stick · 2015-01-25 21:57:26

It won't connect until it has an ip address from your dhcp client -- what is the output from:

# dhcpcd

EDIT: the `-Dwext` flag is unnecessary (the driver is allocated automatically), but the `-B` (daemonise) flag is needed to automatically re-connect if the service is dropped.

Last edited by Head_on_a_Stick (2015-01-25 21:59:04)

preschema · 2015-01-25 22:00:54

[root@deglise ~]# dhcpcd
dhcpcd[21122]: version 6.6.7 starting
dhcpcd[21122]: wlp2s0: adding address fe80::cbb3:d535:e393:9489
dhcpcd[21122]: DUID 00:01:00:01:1c:46:69:8f:20:89:84:fc:f2:05
dhcpcd[21122]: enp1s0: IAID 84:fc:f2:05
dhcpcd[21122]: wlp2s0: IAID 24:98:5c:f7
dhcpcd[21122]: wlp2s0: soliciting a DHCP lease
dhcpcd[21122]: wlp2s0: offered 192.168.1.6 from 192.168.1.1
dhcpcd[21122]: wlp2s0: soliciting an IPv6 router
dhcpcd[21122]: enp1s0: soliciting a DHCP lease
dhcpcd[21122]: enp1s0: soliciting an IPv6 router
dhcpcd[21122]: enp1s0: offered 192.168.1.106 from 192.168.1.1
dhcpcd[21122]: enp1s0: Router Advertisement from fe80::1
dhcpcd[21122]: wlp2s0: Router Advertisement from fe80::1
dhcpcd[21122]: wlp2s0: leased 192.168.1.6 for 604800 seconds
dhcpcd[21122]: wlp2s0: adding route to 192.168.1.0/24
dhcpcd[21122]: wlp2s0: adding default route via 192.168.1.1
dhcpcd[21122]: forked to background, child pid 21176

I just noticed something strange actually...

[root@deglise ~]# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    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: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 20:89:84:fc:f2:05 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.106/24 brd 192.168.1.255 scope global enp1s0
       valid_lft forever preferred_lft forever
    inet6 fe80::2289:84ff:fefc:f205/64 scope link 
       valid_lft forever preferred_lft forever
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 48:d2:24:98:5c:f7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.6/24 brd 192.168.1.255 scope global wlp2s0
       valid_lft forever preferred_lft forever
    inet6 fe80::cbb3:d535:e393:9489/64 scope link 
       valid_lft forever preferred_lft forever

Is it really supposed to say link/ether for the wireless interface? At http://192.168.1.1 I can see the connected IP's, and it lists two connections from my hostname, both LAN: 192.168.1.106 and 192.168.1.6. For some reason it seems to be behaving like an ethernet interface?!

Head_on_a_Stick · 2015-01-25 22:04:03

preschema wrote:

Is it really supposed to say link/ether for the wireless interface?

Mine says that too.

From your output, you should be connected and able to ping (eg) 8.8.8.8 with no problems.

I don't know why you can't.

preschema · 2015-01-25 22:06:14

Hmm. If I disconnect my ethernet cable and run ip addr show again, the ip address disappears from the output (under wlp2s0)... that can't be right.

I tried it without the -Dwext flag as well and it's the same thing.

Last edited by preschema (2015-01-25 22:08:57)

preschema · 2015-01-25 22:19:32

So, if I unplug my ethernet cable, killall wpa_supplicant, killall dhcpcd, and run

[root@deglise ~]# wpa_supplicant -B -i wlp2s0 -c <(wpa_passphrase "o2-WLAN46" "1234123412341234")
Successfully initialized wpa_supplicant
[root@deglise ~]# dhcpcd wlp2s0
dhcpcd[24528]: version 6.6.7 starting
dhcpcd[24528]: wlp2s0: adding address fe80::cbb3:d535:e393:9489
dhcpcd[24528]: DUID 00:01:00:01:1c:46:69:8f:20:89:84:fc:f2:05
dhcpcd[24528]: wlp2s0: IAID 24:98:5c:f7
dhcpcd[24528]: wlp2s0: rebinding lease of 192.168.1.6
dhcpcd[24528]: wlp2s0: soliciting an IPv6 router
dhcpcd[24528]: wlp2s0: Router Advertisement from fe80::1
dhcpcd[24528]: wlp2s0: leased 192.168.1.6 for 604800 seconds
dhcpcd[24528]: wlp2s0: adding route to 192.168.1.0/24
dhcpcd[24528]: wlp2s0: adding default route via 192.168.1.1
dhcpcd[24528]: forked to background, child pid 24575

and then run `ip addr show`, I don't see any IP address under wlp2s0. If I run it again and again continuously, I eventually see an IP address appear before disappearing again immediately. I was only getting an IP address when I had my ethernet cable plugged in.

Let me try dhclient instead of dhcpcd I guess.

Last edited by preschema (2015-01-25 22:20:11)

Head_on_a_Stick · 2015-01-25 22:22:30

Anything in `dmesg` or `journalctl` when un/plugging the cable?

preschema · 2015-01-25 22:46:05

After unplugging

[root@deglise ~]# dmesg
...
[ 1028.900064] alx 0000:01:00.0 enp1s0: Link Down

[root@deglise ~]# journalctl
...
Jan 25 23:42:03 deglise kernel: alx 0000:01:00.0 enp1s0: Link Down
Jan 25 23:42:03 deglise dhcpcd[3498]: enp1s0: carrier lost
Jan 25 23:42:03 deglise avahi-daemon[300]: Withdrawing address record for 192.16
Jan 25 23:42:03 deglise avahi-daemon[300]: Leaving mDNS multicast group on inter
Jan 25 23:42:03 deglise avahi-daemon[300]: Interface enp1s0.IPv4 no longer relev
Jan 25 23:42:03 deglise dhcpcd[3498]: enp1s0: deleting route to 192.168.1.0/24
Jan 25 23:42:03 deglise dhcpcd[3498]: enp1s0: deleting default route via 192.168

After plugging in again

[root@deglise ~]# dmesg
...
[ 1169.253625] alx 0000:01:00.0 enp1s0: NIC Up: 100 Mbps Full

[root@deglise ~]# journalctl
...
Jan 25 23:44:23 deglise dhcpcd[3498]: enp1s0: carrier acquired
Jan 25 23:44:23 deglise kernel: alx 0000:01:00.0 enp1s0: NIC Up: 100 Mbps Full
Jan 25 23:44:23 deglise dhcpcd[3498]: enp1s0: IAID 84:fc:f2:05
Jan 25 23:44:23 deglise dhcpcd[3498]: enp1s0: soliciting an IPv6 router
Jan 25 23:44:24 deglise dhcpcd[3498]: enp1s0: rebinding lease of 192.168.1.106
Jan 25 23:44:24 deglise dhcpcd[3498]: enp1s0: Router Advertisement from fe80::1
Jan 25 23:44:29 deglise dhcpcd[3498]: enp1s0: leased 192.168.1.106 for 604800 se
Jan 25 23:44:29 deglise avahi-daemon[300]: Joining mDNS multicast group on inter
Jan 25 23:44:29 deglise avahi-daemon[300]: New relevant interface enp1s0.IPv4 fo
Jan 25 23:44:29 deglise dhcpcd[3498]: enp1s0: adding route to 192.168.1.0/24
Jan 25 23:44:29 deglise avahi-daemon[300]: Registering new address record for 19
Jan 25 23:44:29 deglise dhcpcd[3498]: enp1s0: adding default route via 192.168.1

preschema · 2015-01-25 23:02:33

Using dhclient gives me an IP address, but I still can't connect. I don't even know what to try next.

Arch Linux

#1 2015-01-25 19:26:12

Wifi connects but doesn't work

#2 2015-01-25 19:58:53

Re: Wifi connects but doesn't work

#3 2015-01-25 20:01:46

Re: Wifi connects but doesn't work

#4 2015-01-25 20:09:27

Re: Wifi connects but doesn't work

#5 2015-01-25 20:25:37

Re: Wifi connects but doesn't work

#6 2015-01-25 20:27:45

Re: Wifi connects but doesn't work

#7 2015-01-25 20:30:17

Re: Wifi connects but doesn't work

#8 2015-01-25 20:58:57

Re: Wifi connects but doesn't work

#9 2015-01-25 21:00:18

Re: Wifi connects but doesn't work

#10 2015-01-25 21:13:08

Re: Wifi connects but doesn't work

#11 2015-01-25 21:32:24

Re: Wifi connects but doesn't work

#12 2015-01-25 21:41:27

Re: Wifi connects but doesn't work

#13 2015-01-25 21:57:26

Re: Wifi connects but doesn't work

#14 2015-01-25 22:00:54

Re: Wifi connects but doesn't work

#15 2015-01-25 22:04:03

Re: Wifi connects but doesn't work

#16 2015-01-25 22:06:14

Re: Wifi connects but doesn't work

#17 2015-01-25 22:19:32

Re: Wifi connects but doesn't work

#18 2015-01-25 22:22:30

Re: Wifi connects but doesn't work

#19 2015-01-25 22:46:05

Re: Wifi connects but doesn't work

#20 2015-01-25 23:02:33

Re: Wifi connects but doesn't work

Board footer