You are not logged in.
Hi,
New to Arch and systemd (+10yrs of Gentoo/OpenRC) experience and am stumped trying to connect to eduroam here at work.
I've opted to use NetworkManager as its served me well over the years and I've gone through setting up login in details as described.
When I try to connect though I get...
[ 9748.058794] wlp2s0 : authenticate with f8:4f:57:41:05:c0
[ 9748.073695] wlp2s0 : send auth to f8:4f:57:41:05:c0 (try 1/3)
[ 9748.083806] wlp2s0 : authenticated
[ 9748.084739] wlp2s0 : associate with f8:4f:57:41:05c0 (try 1/3)
[ 9748.090722] wlp2s0 : Rx AssocResp from f8:4f:57:41:05:c0 (capab=0x431 status=0 aid=66)
[ 9748.090899] wlp2s0 : associated
[ 9748.456976] wlp2s0 : Limiting TX power to 17 dBM as advertised by f8:4f:57:41:05:c0
[ 9750.264884] wlp2s0 : deauthenticating from f8:4f:57:41:05:c0 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 9761.970906] wlp2s0 : authenticate with f8:4f:57:41:05:c0 (try 1/3)
[ 9761.990339] wlp2s0 : send auth to f8:4f:57:41:05:c0 (try 1/3)
[ 9762.098170] wlp2s0 : send auth to f8:4f:57:41:05:c0 (try 2/3)
[ 9762.103750] wlp2s0 : authenticated
[ 9762.104767] wlp2s0 : associate with f8:4f:57:41:05c0 (try 1/3)
[ 9762.108830] wlp2s0 : Rx AssocResp from f8:4f:57:41:05:c0 (capab=0x431 status=0 aid=66)
[ 9762.109902] wlp2s0 : associated
[ 9762.244632] wlp2s0 : Limiting TX power to 17 dBM as advertised by f8:4f:57:41:05:c0
[ 9764.251588] wlp2s0 : deauthenticating from f8:4f:57:41:05:c0 by local choice (Reason: 3=DEAUTH_LEAVING)
Which indicates authentication and association is happening ok, but my laptop is then disconnecting. I found this thread which suggested that this could be due to conflicting Netwok managing services, but as far as I'm aware I've only got NetworkManager service running (can't paste full output of systemctl as currently laptop isn't on network to copy and paste from I'm afraid). I've somewhat discounted this option though as I can boot and connect to Wifi at home ok.
systemctl | grep -i network
sys-devices-pci0000:00-0000:00:1c.1-0000:02:00.0-net-wlp2s0.device loaded active plugged AR9485 Wireless Network Adapter
sys-subsystem-net-devices-wlp2s0.device loaded active plugged AR9485 Wireless Network Adapter
NetworkManager.service loaded active running Network Manager
network.target loaded active running Network
systemctl | grep -i network
wpa_supplicant.service loaded acrive running WPA supplicant
I thought it might be that NetworkManager and wpa_supplicant were in conflict so stopped wpa_supplicant but this appeared to disable NetworkManager from being able to detect any of the Wifi Networks in the building, so think (but am not sure) that NetworkManager is using wpa_supplicant to manage the WiFi interface.
I've definitely not manually configured the interface, nor have I installed or enabled wicd or anything else like netctl and as I write above I do not have this happening connecting to my WiFi at home yesterday before bringing the laptop to work.
Can anyone suggest what others services I might want to check for that might be causing a conflict or if there is another possible source for this error?
Thank you in advance,
slackline
Offline
Can you post the output of...
systemctl list-unit-files --state=enabled
You can tether a smartphone to your laptop if you have one to get network access.
Offline
Thanks for your time slithery...
Can you post the output of...
systemctl list-unit-files --state=enabled
Sure its...
UNIT FILE STATE
-----------------------------------------------------------------
autovt@.service enabled
dbus-fi.wl.wpa_supplicantl.service enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service enabled
display-manager.service enabled
getty@.service enabled
lightdm.service enabled
NetworkManager-dispatcher.service enabled
NetworkManager.service enabled
sshd.service enabled
wpa_supplicant.service enabled
-----------------------------------------------------------------
remote-fs.target enabled
12 unit files listed
Let me know if there is any more useful information.
You can tether a smartphone to your laptop if you have one to get network access.
Would love to have the time to get that working but requires hassling my network provider to allow me such access and supposed to be working (its on my todo list though once I've got general WiFi working)
Offline
You need to disable the wpa_supplicant service. At the moment you have two different services fighting over control of your adapter.
Offline
You need to disable the wpa_supplicant service. At the moment you have two different services fighting over control of your adapter.
I had already tried that and have done so again with...
systemctl disable --now wpa_supplicant.service
...but now, as with earlier, when I click on the nm-applet icon I am told "WiFi Networks > device not ready" which is why I thought wpa_supplicant was a service dependency of NetworkManager (restarting wpa_supplicant.service enables the WiFi and I see a list of SSIDs). Are you able to advise how to make the WiFi device available to NetworkManager whilst wpa_supplicant is not running?
I've looked under journalctl and have the following...
-- Logs being at Fri 2017-01-05 09:24:32 GMT. --
Jan 08 13:38:41 fisher wpa_supplicant[7479]: wlp2s0: reject scan trigger since one is already pending
Jan 08 13:40:39 fisher systemd[1]: Reloading.
Jan 08 13:40:39 fisher systemd[1]: Stopping WPA supplicant...
Jan 08 13:40:39 fisher wpa_supplicant[7479]: nl80211: deinit ifname=wlp2s0 disablied_lib_rates=0
Jan 08 13:40:39 fisher wpa_supplicant[7479]: wlp22s0: CTRL-EVENT-TERMINATING
Jan 08 13:40:39 fisher NetworkManager[33]: <info> [1515418839.2015] supplicant: wpa_supplicant stopped
Jan 08 13:40:39 fisher systemd[1]: Stopped WPA supplicant.
Jan 08 13:40:39 fisher NetworkManager[33]: <info> [1515418839.2021] device (wlp2s0): supplicant interface state: inactive -> down
Jan 08 13:40:39 fisher NetworkManager[33]: <info> [1515418839.2026] device (wlp2s0): state change: disconnected -> (reason 'supplicant-failed', sys-iface-state: 'managed')
Jan 08 13:40:39 fisher NetworkManager[33]: <info> [1515418849.8089] supplicant: wpa_supplicanht die count reset
If I'm reading/interpreting it right stoping wpa_supplicant from systemctl is noticed by NetworkManager and it then brings down the wlp2s0 interface (which matches with the above of no SSIDs being listed from nm-applet).
Should I perhaps set NetworkManager up to use an alternative dhcp client such as dhcpcd or dhclient? If so how would bringin up the wlp2s0 interface be done?
Thanks again for spending your time helping me with this, its appreciated as I'm confused!
Offline
I guess it would be better to stop NetworkManager after disabling --now wpa_supplicant, and then restart NetworkManager alone.
Should I perhaps set NetworkManager up to use an alternative dhcp client such as dhcpcd or dhclient? If so how would bringin up the wlp2s0 interface be done?
https://wiki.archlinux.org/index.php/Ne … HCP_client
You could try but first be sure that the above is done correctly.
Offline
Have you restarted either the machine or the NetworkManger service since stopping/disable the wpa_supplicant service?
For clarification NM does use wpa_supplicant, but launches it itself when needed. Using the wpa_supplicant service will conflict with NM.
Offline
Ah, I think I'm starting to see where I've gone wrong. I've never knowingly enabled the wpa_supplicant.service but after disabling it and slithery's suggestion I've rebooted and its no longer listed...
UNIT FILE STATE
-----------------------------------------------------------------
autovt@.service enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service enabled
display-manager.service enabled
getty@.service enabled
lightdm.service enabled
NetworkManager-dispatcher.service enabled
NetworkManager.service enabled
sshd.service enabled
-----------------------------------------------------------------
remote-fs.target enabled
12 unit files listed
...and NetworkManager's nm-applet now lists the SSIDs that abound in this building. Trying to connect to eduroam dmesg now shows...
[ 59.718625] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 66.936657] wlp2s0 : authenticate with f8:4f:57:41:05:c0
[ 66.955559] wlp2s0 : send auth to f8:4f:57:41:05:c0 (try 1/3)
[ 66.958154] wlp2s0 : authenticated
[ 66.960873] wlp2s0 : associate with f8:4f:57:41:05c0 (try 1/3)
[ 66.964266] wlp2s0 : Rx AssocResp from f8:4f:57:41:05:c0 (capab=0x431 status=0 aid=112)
[ 66.964400] wlp2s0 : associated
[ 66.965530] wlp2s0 : Limiting TX power to 17 dBM as advertised by f8:4f:57:41:05:c0
[ 69.052985] wlp2s0 : deauthenticating from f8:4f:57:41:05:c0 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 80.755521] wlp2s0 : authenticate with f8:4f:57:41:05:c0 (try 1/3)
[ 80.775776] wlp2s0 : send auth to f8:4f:57:41:05:c0 (try 1/3)
[ 80.777705] wlp2s0 : authenticated
[ 80.780688] wlp2s0 : associate with f8:4f:57:41:05c0 (try 1/3)
[ 80.784931] wlp2s0 : Rx AssocResp from f8:4f:57:41:05:c0 (capab=0x431 status=0 aid=66)
[ 80.785077] wlp2s0 : associated
[ 81.069651] wlp2s0 : Limiting TX power to 17 dBM as advertised by f8:4f:57:41:05:c0
[ 82.839804] wlp2s0 : deauthenticating from f8:4f:57:41:05:c0 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 85.025866] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 85.054465] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
So I've now only got one network service trying to manage the wlp2s0 interface (NetworkManager) and its perhaps(?) using wpa_supplicant in the background/internally/launching it itself, but the interface is still deauthenticating because of an issue on the laptop.
Offline
Stop NM and try https://wiki.archlinux.org/index.php/Wi … nual_setup
Also provide lspci/lsusb (for the WiFi chip in use)
Offline
Ok the WiFi chip is...
lspci -v
...
02:00.0 Networlk controller: Qualcomm Atheros AR9485 Wirless Network Adapter (rev 01)
Subsystem: AzureWave AR9485 Wireless Network Adapter
Flags: bus master, fast devsel, latency -, IRQ 17
Memory at dea00000 (64-bit, non-prefetchable) [size=512K]
Expansion ROM at dea80000 [disabled] [size=64K]
Capabilities: [40] Power Management version 2
Capabilities: [50] MSI: Enable- Count=1/4 Maskable+ 64bit+
I'd used the manual method to initially connect at home successfully before installing NetworkManager (perhaps this is where wpa_supplicant.service got added although I'm pretty sure I never systemctl enable --now wpa_supplicant as I was using the method of passing wpa_passphrase directly to wpa_supplicant).
The WiFi here uses WPA2 Enterprise and is eduroam so I've just had a go at running the script on my work computer to generate a configuration file then manually re-typed it on the laptop as I don't have a USB flash drive to hand here so I can't copy the certificate over (or run the install script directly on the laptop).
Currently the configuration I'm using is...
network={
ssid="eduroam"
key_mgmt=WPA-EAP
pairwise=CCMP
group=CCMP TKIP
eap=PEAP
identity="######"
domain_suffix_match="eduroam.shef.ac.uk"
phase2="auth=MSCHAPV2"
password="########"
}
Which I've saved to /etc/wpa_supplicant/eduroam.conf and have started with....
wpa_supplicant -b -i wlp2s0 -c/etc/wpa_supplicant/eduroam.conf
dhcpcd wlp2s0
...and bingo I'm online. Yay, thank you.
Now how to get eduroam to play ball with NetworkManager? Since I've started wpa_supplicant manually am I able to start the NetworkManager.service without any conflict? Tried it and interface goes down, so have reverted to manually connecting (after a reboot, restarting manually didn't seem to work as reverted to the previous deauthentication, likely because I'd tried starting NetworkManager.service). Going to reboot, start manually, download the eduroam installer script and see if it can configure NetworkManager.
EDIT : No joy, have tried running the eduroam script as user and root and both times fails generating NetworkManager configuration. Will have a go at manually creating one based on the above /etc/wpa_supplicant/eduroam.conf
Last edited by slackline (2018-01-08 16:18:04)
Offline