Arch Linux

esquire70

Member

Registered: 2014-10-25

Posts: 13

netctl automation

I am following the netctl wiki here. Right now, I can execute

netctl start home

and connect. After installing ifplugd and wpa_actiond, executing the following

systemctl enable netctl-auto@wlan0.service
systemctl enable netctl-ifplugd@wlan0.service

and rebooting,

systemctl | grep netctl

shows that these services are loaded, active, and running but I can't connect. Can you help me understand what I am doing wrong? Thanks.

lucke

Member

From: Poland

Registered: 2004-11-30

Posts: 4,018

Re: netctl automation

ifplugd is for wired interfaces. Perhaps enabling it for wlan0 is breaking things.

Xyne

Administrator/PM

Registered: 2008-08-03

Posts: 6,963

Website

Re: netctl automation

You should provide more information to make it easier for others to help you.

You have enabled netctl-auto and netctl-ifplugd on wlan0, but the former is for wireless connections while the latter is for wired.  Presumably you only want to enable and start netctl-auto@wlan0.service.

What is the output of

ip link
netctl status home
systemctl status netctl-auto@wlan0.service

What is the content of your netctl "home" profile?

---

My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone

esquire70

Member

Registered: 2014-10-25

Posts: 13

Re: netctl automation

My apologies. I will be more thorough in the future. I disabled ifplugd with no luck. These are the outputs:

$: 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: enp9s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:1d:09:48:da:93 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
    link/ether 00:1f:3a:3b:cf:14 brd ff:ff:ff:ff:ff:ff

$: netctl status home
o netctl@home.service - Networking for netctl profile home
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: inactive (dead)
     Docs: man:netctl.profile(5)

systemctl status netctl-auto@wlan0.service
o netctl-auto@wlan0.service - Automatic wireless network connection using netctl profiles
   Loaded: loaded (/usr/lib/systemd/system/netctl-auto@.service; enabled)
   Active: active (running) since Wed 2014-12-17 19:08:03 EST; 5min ago
     Docs: man:netctl.special(7)
  Process: 233 ExecStart=/usr/bin/netctl-auto start %I (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/system-netctl\x2dauto.slice/netctl-auto@wlan0.service
           └─296 wpa_supplicant -B -P /run/wpa_supplicant_wlan0.pid -i wlan0 -D nl80211,wext -c/run/network/wpa_supplicant_wlan0.conf -W

Dec 17 19:08:01 pluto netctl-auto[233]: Included profile 'scwifi'
Dec 17 19:08:02 pluto netctl-auto[233]: Included profile 'home'
Dec 17 19:08:03 pluto wpa_actiond[298]: Starting wpa_actiond session for interface 'wlan0'

$: cat /etc/netctl/home (removing key)

Description='home'
Interface=wlan0
Connection=wireless
Security=wpa
IP=dhcp
ESSID='belkin.5892'
Key=*****

Last edited by esquire70 (2014-12-18 00:27:53)

LeonardK

Member

From: Berlin, Germany

Registered: 2014-07-31

Posts: 591

Re: netctl automation

try

netctl disable wlan0@home

so it wont interfere.

and

netctl-auto status

for showing which connections netctl-auto should handle etc.

---

It's 106 miles to Chicago we got a full tank of gas, half a pack of cigarettes, its dark and we're wearing sunglasses.