Arch Linux

manypopes

Member

Registered: 2013-06-25

Posts: 33

Wifi finds networks but won't connect

I've just installed Arch on a Netbook but I can't get the wireless to work.

lspci -k shows my wireless card as:

Ethernet Controller: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI Express)
Subsystem: Askey Computer Corp. Device 7131
Kernel driver in use: ath5k
Kernel modules: ath5k

This I think implies that everything should just work.
If I install dialog then run wifi-menu, I can find nearby connections easily but when I try to connect I just get "connecting failed"

When I run ip link I get:

wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN mode DEFAULT qlen 1000

If I do ip link set wlp2s0 up then re-check ip link nothing has changed.
dmesg keeps saying "IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready

iw dev wlp2s0 scan works fine and shows all networks

Does anyone have any idea what I'm doing wrong? The exact same happens on an old laptop I have as well as a usb dongle (which I know works on Xubuntu), so I'm hoping there's something systematically wrong with what I'm doing.

mamamia88

Member

Registered: 2012-08-29

Posts: 483

Re: Wifi finds networks but won't connect

You didn't happen to load any networking related daemons during the install process that you forgot about? Otherwise all I can really suggest is to read this super carefully.  https://wiki.archlinux.org/index.php/Wi … up#Atheros

Last edited by mamamia88 (2013-09-05 23:45:00)

manypopes

Member

Registered: 2013-06-25

Posts: 33

Re: Wifi finds networks but won't connect

I've quite sure I've not loaded any daemons.

Looking on that link, I downloaded and installed the madwifi driver (got replaced by ath5k)  from the AUR hoping that it might be compatible. Now that's installed would I have to load different modules? Somewhere on the madwifi site said to load ath_pci as a module, however modprobe doesn't find it.

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,612

Re: Wifi finds networks but won't connect

<ModeratorMode>Moving to Newbie Forum>/ModeratorMode>

As a sanity check, please check the output of sudo iw  wlp2s0 scan

If it displays access points in your vicinity, then we know the hardware and drivers are working and we can continue the discussion as to how to associate with various types of access points.
If it does not work, or cannot see any APs, then we need to start at the lower levels.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

manypopes

Member

Registered: 2013-06-25

Posts: 33

Re: Wifi finds networks but won't connect

Yes iw dev wlp2s0 scan returns all the access points.

BSS bc:f2:af:74:8c:3e(on wlp2s0)
	TSF: 551489231 usec (0d, 00:09:11)
	freq: 2412
	beacon interval: 100 TUs
	capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
	signal: -92.00 dBm
	last seen: 883 ms ago
	SSID: ParrotsLair
	Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 
	DS Parameter set: channel 1
	ERP: <no flags>
	Extended supported rates: 24.0 36.0 48.0 54.0 
	HT capabilities:
		Capabilities: 0x11ef
			RX LDPC
			HT20/HT40
			SM Power Save disabled
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 3839 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: No restriction (0x00)
		HT RX MCS rate indexes supported: 0-15
		HT TX MCS rate indexes are undefined
	HT operation:
		 * primary channel: 1
		 * secondary channel offset: no secondary
		 * STA channel width: 20 MHz
		 * RIFS: 0
		 * HT protection: nonmember
		 * non-GF present: 0
		 * OBSS non-GF present: 0
		 * dual beacon: 0
		 * dual CTS protection: 0
		 * STBC beacon: 0
		 * L-SIG TXOP Prot: 0
		 * PCO active: 0
		 * PCO phase: 0
	Overlapping BSS scan params:
		 * passive dwell: 20 TUs
		 * active dwell: 10 TUs
		 * channel width trigger scan interval: 300 s
		 * scan passive total per channel: 200 TUs
		 * scan active total per channel: 20 TUs
		 * BSS width channel transition delay factor: 5
		 * OBSS Scan Activity Threshold: 0.25 %
	Extended capabilities: HT Information Exchange Supported
	WMM:	 * Parameter version 1
		 * u-APSD
		 * BE: CW 15-1023, AIFSN 3
		 * BK: CW 15-1023, AIFSN 7
		 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
		 * VO: CW 3-7, AIFSN 2, TXOP 1504 usec
	RSN:	 * Version: 1
		 * Group cipher: CCMP
		 * Pairwise ciphers: CCMP
		 * Authentication suites: PSK
		 * Capabilities: (0x0000)
	WPS:	 * Version: 1.0
		 * Wi-Fi Protected Setup State: 2 (Configured)
		 * AP setup locked: 0x01
		 * Response Type: 3 (AP)
		 * UUID: 8b2296bf-2426-5cc3-a9ff-ea7a7d496300
		 * Manufacturer: unknown
		 * Model: HomePlug AV Wireless AP 
		 * Model Number: HomePlug AV Wireless AP
		 * Serial Number: 1.0
		 * Primary Device Type: 6-0050f204-1
		 * Device name: HomePlug AV Wireless AP
		 * Config methods: Ethernet, Label, Display
		 * RF Bands: 0x1
		 * Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
BSS 30:46:9a:2e:e8:d8(on wlp2s0)
	TSF: 6378686361431 usec (73d, 19:51:26)
	freq: 2462
	beacon interval: 100 TUs
	capability: ESS Privacy ShortSlotTime (0x0411)
	signal: -67.00 dBm
	last seen: 260 ms ago
	Information elements from Probe Response frame:
	SSID: home
	Supported rates: 1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 
	DS Parameter set: channel 11
	ERP: <no flags>
	ERP D4.0: <no flags>
	Extended supported rates: 6.0 9.0 12.0 48.0 
	WPS:	 * Version: 1.0
		 * Wi-Fi Protected Setup State: 2 (Configured)
		 * Selected Registrar: 0x0
		 * Response Type: 3 (AP)
		 * UUID: fa8e6b33-6bca-907f-0bab-c535e1c33a62
		 * Manufacturer: Netgear
		 * Model: DGND3300
		 * Model Number: 123456
		 * Serial Number: 1234
		 * Primary Device Type: 6-0050f204-1
		 * Device name: DGND3300
		 * Config methods: Display, PBC
	WMM:	 * Parameter version 1
		 * u-APSD
		 * BE: CW 15-1023, AIFSN 3
		 * BK: CW 15-1023, AIFSN 7
		 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
		 * VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS e8:ab:fa:12:f8:59(on wlp2s0)
	TSF: 155610791122 usec (1d, 19:13:30)
	freq: 2462
	beacon interval: 100 TUs
	capability: ESS Privacy ShortSlotTime (0x0411)
	signal: -79.00 dBm
	last seen: 280 ms ago
	Information elements from Probe Response frame:
	SSID: WiFi-Repeater
	Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 
	DS Parameter set: channel 11
	ERP: <no flags>
	Extended supported rates: 24.0 36.0 48.0 54.0 
	WMM:	 * Parameter version 1
		 * BE: CW 15-1023, AIFSN 3
		 * BK: CW 15-1023, AIFSN 7
		 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
		 * VO: CW 3-7, AIFSN 2, TXOP 1504 usec
	WPS:	 * Version: 1.0
		 * Wi-Fi Protected Setup State: 2 (Configured)
		 * Response Type: 3 (AP)
		 * UUID: 63041253-1019-2006-1228-e8abfa12f859
		 * Manufacturer: Realtek Semiconductor Corp.
		 * Model: RTL8xxx
		 * Model Number: EV-2010-09-20
		 * Serial Number: 123456789012347
		 * Primary Device Type: 6-0050f204-1
		 * Device name: Repeater
		 * Config methods: Ethernet, Label, PBC

All those access points are on my network (my dad has rigged up the house full of wireless repeaters). The "home" SSID is the original wireless point from the router.

If I try to connect with iw dev wlp2s0 connect home key *** nothing appears to happen. dmesg shows "wlp2s0 send auth to <address> (try1/3, 2/3 etc)", then "wlp2s0 authentication with <address> timed out"

Just as a double check, the only thing I need installed is iw? I recall there being other stuff you needed but this time on the wiki I never saw anything else.

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,612

Re: Wifi finds networks but won't connect

I cannot tell whether your device is WEP or WPA.  The technique you are trying to use only works with WEP.   WEP is no longer considered secure and has been deprecated.  I have a very strong hunch you have WPA or WPA2 on your network.

As such, you need wpa_supplicant.   While it is possible to "Hand Fly" wpa_supplicant, you really will want want to configure one of the various network management tools to make your life easier.

Consider the following (in the order I recommend them):
https://wiki.archlinux.org/index.php/Netctl
https://wiki.archlinux.org/index.php/Wicd
https://wiki.archlinux.org/index.php/Networkmanager

If you want to just use wpa_supplicant, there are a couple tools to make it simpler.  I think they are called wpa_cli and wpa_gui.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

manypopes

Member

Registered: 2013-06-25

Posts: 33

Re: Wifi finds networks but won't connect

Two are WEP the third is WPA2. I've installed netctl, wpa_supplicant and dialog. If I try to connect via wifi-menu it says "Connecting Failed" on all three access points.

I also  tried wpa_supplicant -B -i interface -c <(wpa_passphrase essid passphrase) as stated on the wpa_supplicant wiki page but that also timed out when connecting.

dmesg keeps logging "IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready" when things don't connect.

torors

Member

Registered: 2012-09-28

Posts: 107

Re: Wifi finds networks but won't connect

I had similar problems with netctl. Adding "TimeoutDHCP=30" to my profile in /etc/netctl solved the problem.

manypopes

Member

Registered: 2013-06-25

Posts: 33

Re: Wifi finds networks but won't connect

I've just discovered that when netctl start wlp2s0-home fails, journalctl -xn shows

-- Logs begin at Thu 2013-09-05 17:24:28 BST, end at Sat 2013-09-07 15:59:26 BST. --
Sep 07 15:59:25 samsung-n110 network[762]: Successfully initialized wpa_supplicant
Sep 07 15:59:25 samsung-n110 network[762]: Line 6: Too long WEP key 0 '"***"'.
Sep 07 15:59:25 samsung-n110 network[762]: Line 6: failed to parse wep_key0 '"***"'.
Sep 07 15:59:25 samsung-n110 network[762]: Line 8: failed to parse network block.
Sep 07 15:59:25 samsung-n110 network[762]: Failed to read or parse configuration '/run/network/wpa_supplicant_wlp2s0.conf'.
Sep 07 15:59:26 samsung-n110 network[762]: The WPA supplicant did not start for interface 'wlp2s0'
Sep 07 15:59:26 samsung-n110 network[762]: Failed to bring the network up for profile 'wlp2s0-home'
Sep 07 15:59:26 samsung-n110 systemd[1]: netctl@wlp2s0\x2dhome.service: main process exited, code=exited, status=1/FAILURE
Sep 07 15:59:26 samsung-n110 systemd[1]: Failed to start Networking for netctl profile wlp2s0-home.
-- Subject: Unit netctl@wlp2s0\x2dhome.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
-- 
-- Unit netctl@wlp2s0\x2dhome.service has failed.
-- 
-- The result is failed.
Sep 07 15:59:26 samsung-n110 systemd[1]: Unit netctl@wlp2s0\x2dhome.service entered failed state.

Does this mean that my wireless key is too long? It's 26 characters. Also, I hope that this error isn't due to me messing around with wpa_supplicant earlier as I do not remember seeing it before now.

torors

Member

Registered: 2012-09-28

Posts: 107

Re: Wifi finds networks but won't connect

26 characters should not bee too long. If you have som special characters like # or $ in your key, they can cause problems.

manypopes

Member

Registered: 2013-06-25

Posts: 33

Re: Wifi finds networks but won't connect

I've had a small breakthrough, but I'm still not connected.

By starting dhcpcd.service via systemctl then running wifi menu, the connection didn't fail after I entered my key.

Instead of the usual "Connection Failed" message the console just clears itself. ip link shows that wlp2s0 is now UP but DORMANT. dmesg shows "wlp2s0: Authenticated" and "wlp2s0: associated"

Pinging Google shows "ping: Unknown host"
Pinging my router shows "connect: Network is unreachable"

This is the first time wlp2s0 has shown as being UP, but I still don't seem to be connected. Anyone know what's going on?

EDIT:
It seems that waiting for 30 seconds allowed me full connection to the internet. I'm happy with it working however I can still only connect by starting dhcpcd.service then running wifi-menu. Netctl won't work. I'll continue to fiddle around with stuff and try some alternatives to Netctl. Thanks for the help anyway.

Last edited by manypopes (2013-09-09 14:13:51)