You are not logged in.

#1 2017-07-16 23:38:23

esuhl
Member
From: UK
Registered: 2009-09-16
Posts: 140

[SOLVED] Network unavailable after update (netctl + wpa_supplicant...

I have an Asus EEE 901 netbook that I hadn't used it since Christmas, so I ran an update.  It took a few hours, but I didn't see any error messages, and I can't see any in /var/log/pacman.log.

However, I can no longer connect to my network.  I'd been using netctl, wpa_supplicant and wifi-menu.

Running sudo wifi-menu results in the following:

Scanning for networks... failed
No networks found

I checked the netctl profile with sudo netctl status esuhllan, and got this:

● netctl@esuhllan.service - Networking for netctl profile esuhllan
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sun 2017-07-16 22:48:15 BST; 2min 43s ago
     Docs: man:netctl.profile(5)
  Process: 817 ExecStart=/usr/lib/network/network start esuhllan (code=exited, status=1/FAILURE)
 Main PID: 817 (code=exited, status=1/FAILURE)

Jul 16 22:48:09 eee901 systemd[1]: Starting Networking for netctl profile esuhllan...
Jul 16 22:48:09 eee901 network[817]: Starting network profile 'esuhllan'...
Jul 16 22:48:15 eee901 network[817]: Failed to bring the network up for profile 'esuhllan'
Jul 16 22:48:15 eee901 systemd[1]: netctl@esuhllan.service: Main process exited, code=exited, status=1/FAILURE
Jul 16 22:48:15 eee901 systemd[1]: Failed to start Networking for netctl profile esuhllan.
Jul 16 22:48:15 eee901 systemd[1]: netctl@esuhllan.service: Unit entered failed state.
Jul 16 22:48:15 eee901 systemd[1]: netctl@esuhllan.service: Failed with result 'exit-code'.

The output of journalctl -xe includes this:

-- Unit netctl@esuhllan.service has begun starting up.
Jul 16 22:51:20 eee901 network[968]: Starting network profile 'esuhllan'...
Jul 16 22:51:20 eee901 network[968]: Could not create a wpa config file for interface 'wlan0'
Jul 16 22:51:20 eee901 network[968]: Failed to bring the network up for profile 'esuhllan'
Jul 16 22:51:20 eee901 systemd[1]: netctl@esuhllan.service: Main process exited, code=exited, status=1/FAILURE
Jul 16 22:51:20 eee901 systemd[1]: Failed to start Networking for netctl profile esuhllan.
-- Subject: Unit netctl@esuhllan.service has failed
-- Defined-By: systemd
-- Support: [url]https://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- 
-- Unit netctl@esuhllan.service has failed.
-- 
-- The result is failed.
Jul 16 22:51:20 eee901 systemd[1]: netctl@esuhllan.service: Unit entered failed state.
Jul 16 22:51:20 eee901 systemd[1]: netctl@esuhllan.service: Failed with result 'exit-code'.

I think my network profile in /etc/netctl/esuhllan is fine:

Description='Automatically generated profile by wifi-menu'
Interface=wlan0
Connection=wireless
Security=wpa
ESSID=<my-wireless-SSID>
IP=dhcp
Key=<my-wireless-passphrase>

But... doesn't udev give semi-arbitrary names to network interfaces now?  The only udev rule file I have is /etc/udev/rules.d/80-net-setup-link.rules which is entirely commented out:

# This file masks persistent renaming rules for network devices. If you
# delete this file, /usr/lib/udev/rules.d/80-net-name-slot.rules may
# rename network devices according to ID_NET_NAME_{ONBOARD,SLOT,PATH}
# properties of your network devices, with priority in that order. See
# the output of 'udevadm test-builtin net_id /sys/class/net/$interface'
# for details on what that new name might be.
# 
# [url]http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames[/url]

As suggested, I ran sudo udevadm test-builtin net_id /sys/class/net/$interface, and this is the output:

calling: test-builtin
=== trie on-disk ===
tool version:          233
file size:         8697912 bytes
header size             80 bytes
strings            1872152 bytes
nodes              6825680 bytes
Load module index
Found container virtualization none.
timestamp of '/etc/systemd/network' changed
timestamp of '/usr/lib/systemd/network' changed
Parsed configuration file /usr/lib/systemd/network/99-default.link
Created link configuration context.
Unload module index
Unloaded link configuration context.

I tried deleting (moving) /etc/udev/rules.d/80-net-setup-link.rules, and the wlan0 interface is re-named to wlp1so.  I updated the netctl profile with the new name, but seem to be getting the same errors.

I'm not really sure what to do next.  Can anyone help? :-)

Last edited by esuhl (2017-07-18 00:20:38)

Offline

#2 2017-07-17 05:39:33

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,880

Re: [SOLVED] Network unavailable after update (netctl + wpa_supplicant...

Follow https://wiki.archlinux.org/index.php/Wi … nual_setup precisely.
Watch outputs for errors. If stuck, ask back with the condition you face.

Offline

#3 2017-07-18 00:20:03

esuhl
Member
From: UK
Registered: 2009-09-16
Posts: 140

Re: [SOLVED] Network unavailable after update (netctl + wpa_supplicant...

Ah, thanks!

I installed rfkill and unblocked the wireless interface, and it works again! :-)

# rfkill unblock wifi

Offline

Board footer

Powered by FluxBB