Netctl-auto & netctl-ifplugd prefer wired?

Hi,
On my laptop running Arch Linux I've got both netctl-auto and netctl-ifplugd running. I have both ethernet and wireless set up in my house, and I'd like to have it set up so that it prefers wired over the wireless connection. So that if it's plugged in I can know for sure it is using the wired connection and not the wireless connection, and if I unplug it it should switch to wireless.
There's a 'priority' variable but that only applies to wireless connections and so it has no effect on the wired profile. I've gone through the manpages for netctl-auto and ifplugd and gone through the relevant sections for netcl in the wiki multiple times but there doesn't seem to be anything on getting this kind of setup.
So is there a way to have Arch prefer wired connections over wireless?

https://wiki.archlinux.org/index.php/ne … s_failover

Similar Messages

  • Netctl and bespoke ifplugd actions best practice

    Hi,
    Before the switch to netctl/systemd I used ifplugd to perform actions on ethernet up/down events.
    I'm now using netctl-ifplugd to automatically configure my ethernet interface and wonder how best to add my own actions. I apparently cannot run ifplugd separately because netctl-ifplugd is already running ifplugd on the same interface(?) Does this mean that I have to edit /etc/ifplugd/netctl.action? I'd rather not edit this in case of future updates.
    My goal is to automatically start my wireless connection when ethernet is disconnected and vice versa, so that the fastest connection is used. If there is a better way to achieve this I'd be happy to hear it.
    Thanks

    Personally, I just use netctl-auto and netctl-ifplugd, such that whichever can connect, will connect. In terms of having netctl select the fastest connection of the two, I'm sorry to say that I'm unaware of how to do that.
    All the best,
    -HG

  • Netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

    A few hours ago, I upgraded from wpa_supplicant-2.3-1 to wpa_supplicant-2.4-1. Subsequently [email protected] stopped working. After I started it, it would be reported as "active (running)" but fail to connect to any WIFI network (I wouldn't get assigned a DHCP IP address):
    Apr 25 12:44:47 sauron wpa_actiond[6952]: Interface 'wlp3s0' connected to network 'Edward'
    Apr 25 12:44:47 sauron dhcpcd[6974]: DUID xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
    Apr 25 12:44:47 sauron dhcpcd[6974]: wlp3s0: IAID xx:xx:xx:xx
    Apr 25 12:44:47 sauron dhcpcd[6974]: wlp3s0: rebinding lease of 192.168.1.20
    Apr 25 12:44:51 sauron dhcpcd[6974]: wlp3s0: leased 192.168.1.20 for 43200 seconds
    Apr 25 12:44:51 sauron dhcpcd[6974]: wlp3s0: adding route to 192.168.1.0/24
    Apr 25 12:44:51 sauron dhcpcd[6974]: wlp3s0: adding default route via 192.168.1.1
    12:55 ~$ journalctl -xe -u [email protected]
    Apr 25 12:36:28 sauron netctl-auto[5505]: Included profile 'wlp3s0-cz'
    Apr 25 12:36:28 sauron netctl-auto[5505]: Successfully initialized wpa_supplicant
    Apr 25 12:36:28 sauron netctl-auto[5505]: Could not read interface p2p-dev-wlp3s0 flags: No such device
    Apr 25 12:36:28 sauron systemd[1]: Started Automatic wireless network connection using netctl profiles.
    -- Subject: Unit [email protected] has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit [email protected] has finished starting up.
    Notice the "Could not read interface...". I downgraded back to 2.3-1 and the problem went away. Could this be a wpa_supplicant bug (new bug in 2.4-1) or netctl bug (incompatibility with the new wpa_supplicant)?
    There's nothing special about the profile files in /etc/netctl. In addition to the ones for wired network, I have a few files named like "wlp3s0-XXX" and they look like this (password crossed out):
    Connection=wireless
    Description='Edward'
    Interface=wlp3s0
    Security=wpa
    ESSID='Edward'
    Key='????'
    Hidden=yes
    IP=dhcp

    I'm having exactly the same problem.
    # wpa_supplicant -D wext -i wlp2s0 -c /tmp/wpap
    Successfully initialized wpa_supplicant
    ioctl[SIOCSIWENCODEEXT]: Invalid argument
    ioctl[SIOCSIWENCODEEXT]: Invalid argument
    ioctl[SIOCSIWSCAN]: Device or resource busy
    wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
    ioctl[SIOCSIWSCAN]: Device or resource busy
    wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
    ioctl[SIOCSIWSCAN]: Device or resource busy
    wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
    ioctl[SIOCSIWSCAN]: Device or resource busy
    wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
    wlp2s0: Trying to associate with 00:1e:e5:6d:83:6f (SSID='Driesen-Peeters' freq=2437 MHz)
    ioctl[SIOCSIWFREQ]: Device or resource busy
    wlp2s0: Association request to the driver failed
    wlp2s0: Authentication with 00:1e:e5:6d:83:6f timed out.
    ioctl[SIOCSIWMLME]: Transport endpoint is not connected
    ioctl[SIOCSIWAP]: Device or resource busy
    wlp2s0: CTRL-EVENT-DISCONNECTED bssid=00:1e:e5:6d:83:6f reason=3 locally_generated=1
    ioctl[SIOCSIWSCAN]: Device or resource busy
    wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
    ioctl[SIOCSIWSCAN]: Device or resource busy
    wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
    ^Cwlp2s0: CTRL-EVENT-TERMINATING
    # wpa_supplicant -D wext -i wlp2s0 -c /tmp/wpap
    Successfully initialized wpa_supplicant
    Could not read interface p2p-dev-wlp2s0 flags: No such device
    wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
    wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
    wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
    wlp2s0: SME: Trying to authenticate with 00:1e:e5:6d:83:6f (SSID='My-Network' freq=2437 MHz)
    wlp2s0: SME: Authentication request to the driver failed
    ^C
    nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
    p2p-dev-wlp2s0: CTRL-EVENT-TERMINATING
    nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0
    wlp2s0: CTRL-EVENT-TERMINATING
    This also break wifi-menu by the way, so the only option now is trying a manual wpa_supplicant connect. I should mention that this morning (after troubleshooting all night with no result) I managed to connect to my AP once (while begin connected via ethernet as well). After disconnecting the ethernet cable and trying again it failed again. I have not been able to reproduce this.
    Other possibly interesting information:
    # dmesg
    [ 734.004304] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
    [ 734.004343] iwlwifi 0000:02:00.0: No available PHY context
    [ 734.004378] iwlwifi 0000:02:00.0: No available PHY context
    [ 737.496406] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
    [ 737.496431] iwlwifi 0000:02:00.0: No available PHY context
    [ 741.388469] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
    [ 741.388493] iwlwifi 0000:02:00.0: No available PHY context
    [ 963.953904] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
    [ 963.956708] wlp2s0: send auth to 00:1e:e5:6d:83:6f (try 1/3)
    [ 963.958860] wlp2s0: authenticated
    [ 963.961363] wlp2s0: associate with 00:1e:e5:6d:83:6f (try 1/3)
    [ 963.964229] wlp2s0: RX AssocResp from 00:1e:e5:6d:83:6f (capab=0x411 status=0 aid=1)
    [ 963.965539] wlp2s0: associated
    [ 966.651095] wlp2s0: deauthenticating from 00:1e:e5:6d:83:6f by local choice (Reason: 3=DEAUTH_LEAVING)
    [ 966.655984] cfg80211: Calling CRDA to update world regulatory domain
    [ 966.659308] cfg80211: World regulatory domain updated:
    [ 966.659312] cfg80211: DFS Master region: unset
    [ 966.659313] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
    [ 966.659315] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
    [ 966.659317] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
    [ 966.659319] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
    [ 966.659321] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
    [ 966.659323] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
    [ 966.659324] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
    [ 966.659326] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
    [ 966.659327] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
    [ 1033.789418] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
    [ 1043.308740] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
    [ 1046.718632] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
    [ 1046.718644] iwlwifi 0000:02:00.0: No available PHY context
    [ 1046.718654] iwlwifi 0000:02:00.0: No available PHY context
    [ 1050.109123] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
    [ 1050.109147] iwlwifi 0000:02:00.0: No available PHY context
    [ 1072.258284] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
    [ 1075.694370] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
    [ 1075.697180] wlp2s0: send auth to 00:1e:e5:6d:83:6f (try 1/3)
    [ 1076.003982] iwlwifi 0000:02:00.0: No association and the time event is over already...
    [ 1076.004017] wlp2s0: Connection to AP 00:1e:e5:6d:83:6f lost
    [ 1080.255382] wlp2s0: authenticated
    # pacman -Q wpa_supplicant
    wpa_supplicant 2.4-1
    # uname -r
    3.19.3-3-ARCH
    # lspci -v | grep Wireless -A 15
    02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
    Subsystem: Intel Corporation Dual Band Wireless-AC 7265
    Flags: bus master, fast devsel, latency 0, IRQ 50
    Memory at f7000000 (64-bit, non-prefetchable) [size=8K]
    Capabilities: [c8] Power Management version 3
    Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
    Capabilities: [40] Express Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Device Serial Number 60-57-18-ff-ff-4a-6a-8c
    Capabilities: [14c] Latency Tolerance Reporting
    Capabilities: [154] L1 PM Substates
    Kernel driver in use: iwlwifi
    Kernel modules: iwlwifi
    I'm on a Zenbook UX305, what are you guys on and could you post the output of those last three commands I posted?
    Cheers!

  • Netctl-auto and dropbox

    Hi, I've been reading the wiki. The only difference is my interface name is wlp2s0 instead of wlan0. So I went to /etc/netctl/interfaces and I created a new file called wlp2s0 with the contents
    ExecUpPost="su -c 'DISPLAY=:0 /usr/bin/dropboxd &' root || true"
    ExecDownPre="killall dropbox"
    However, this doesn't seem to do anything. I've disabled the "Start Dropbox on system startup" option, but everytime I restart, there's no dropbox icon in the dock like there normally is. What am I doing wrong?
    Internet roaming still seems to work, even after putting the computer to sleep.
    Last edited by boogerlad (2013-11-16 22:01:34)

    Wonderwoofy,
    I'm having a similar problem with my [email protected] connecting at startup. It loads fine but stays on connecting....... . I can stop and restart it using
    # systemctl stop/start dropbox@dmy
    and it works as expected. I can use the same method that boogerland describes in the first post and it works fine but I wanted to get it to work with systemd if possible. Any thoughts? Here's my [email protected]
    [Unit]
    Description=Dropbox
    After=local-fs.target network.target netctl-auto@wlan0 netctl-ifplugd@enp3s0
    Wants=netctl-auto@wlan0 netctl-ifplugd@enp3s0
    [Service]
    Type=simple
    Environment=DISPLAY=:0
    ExecStart=/home/dmy/.dropbox-dist/dropboxd
    ExecReload=/bin/kill -HUP $MAINPID
    KillMode=process
    Restart=always
    User=%I
    [Install]
    WantedBy=multi-user.target

  • [SOLVED]netctl-auto no longer working

    Can some kind person point me in the right direction to fix this? Seems to have stopped working after latest upgrade.  Manually netctl start works OK.  Haven't been able to find the solution in man pages or googling.
    [email protected] - Automatic wireless network connection using netctl profiles
    Loaded: loaded (/usr/lib/systemd/system/[email protected]; enabled)
    Active: failed (Result: exit-code) since Wed 2014-07-09 08:00:20 UTC; 1h 14min ago
    Docs: man:netctl.special(7)
    Process: 231 ExecStart=/usr/bin/netctl-auto start %I (code=exited, status=1/FAILURE)
    Jul 09 08:00:20 arch systemd[1]: Failed to start Automatic wireless network connection using netctl profiles.
    Jul 09 08:00:50 arch netctl-auto[231]: Included profile 'wlp16s0-Matviak'
    Jul 09 08:00:51 arch netctl-auto[231]: Included profile 'wlp16s0-WIRELESS'
    Jul 09 08:00:51 arch netctl-auto[231]: Successfully initialized wpa_supplicant
    Jul 09 08:00:51 arch netctl-auto[231]: ctrl_iface exists and seems to be in use - cannot override it
    Jul 09 08:00:51 arch netctl-auto[231]: Delete '/run/wpa_supplicant/wlp16s0' manually if it is not used anymore
    Jul 09 08:00:51 arch netctl-auto[231]: Failed to initialize control interface '/run/wpa_supplicant'.
    Jul 09 08:00:51 arch netctl-auto[231]: You may have another wpa_supplicant process already running or the file was
    Jul 09 08:00:51 arch netctl-auto[231]: left by an unclean termination of wpa_supplicant in which case you will need
    Jul 09 08:00:51 arch netctl-auto[231]: to manually remove this file before starting wpa_supplicant again.
    Last edited by hilltownboy (2014-08-02 12:41:03)

    journalctl -b | grep wlp16s0:
    ul 29 11:27:17 arch systemd-udevd[148]: renamed network interface wlan0 to wlp16s0
    Jul 29 11:27:28 arch kernel: IPv6: ADDRCONF(NETDEV_UP): wlp16s0: link is not ready
    Jul 29 11:27:28 arch kernel: IPv6: ADDRCONF(NETDEV_UP): wlp16s0: link is not ready
    Jul 29 11:27:19 arch dhcpcd[225]: wlp16s0: adding address fe80::ea40:c74b:8e70:d43a
    Jul 29 11:27:23 arch wpa_actiond[317]: Starting wpa_actiond session for interface 'wlp16s0'
    Jul 29 11:27:24 arch dhcpcd[230]: wlp16s0: waiting for carrier
    Jul 29 11:27:24 arch dhcpcd[230]: wlp16s0: carrier acquired
    Jul 29 11:27:25 arch dhcpcd[230]: wlp16s0: IAID e0:20:c5:69
    Jul 29 11:27:28 arch dhcpcd[230]: wlp16s0: carrier lost
    Jul 29 11:27:25 arch systemd[1]: netctl@wlp16s0\x2dWIRELESS.service: main process exited, code=exited, status=1/FAILURE
    Jul 29 11:27:25 arch systemd[1]: Unit netctl@wlp16s0\x2dWIRELESS.service entered failed state.
    Jul 29 11:27:28 arch network[222]: Starting network profile 'wlp16s0-WIRELESS'...
    Jul 29 11:27:28 arch network[222]: Delete '/run/wpa_supplicant/wlp16s0' manually if it is not used anymore
    Jul 29 11:27:28 arch network[222]: The WPA supplicant did not start for interface 'wlp16s0'
    Jul 29 11:27:28 arch network[222]: Failed to bring the network up for profile 'wlp16s0-WIRELESS'
    Jul 29 11:27:28 arch netctl-auto[223]: Included profile 'wlp16s0-Matviak'
    Jul 29 11:27:28 arch netctl-auto[223]: Included profile 'wlp16s0-WIRELESS'
    Jul 29 11:27:28 arch dhcpcd[230]: wlp16s0: soliciting a DHCP lease
    Jul 29 11:27:28 arch dhcpcd[230]: wlp16s0: if_sendrawpacket: Network is down
    Jul 29 11:27:28 arch dhcpcd[230]: wlp16s0: dhcp if_readrawpacket: Network is down
    Jul 29 11:31:21 arch dbus[227]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.7" (uid=1000 pid=605 comm="systemctl restart netctl-auto@wlp16s0 ") interface="org.freedesktop.systemd1.Manager" member="RestartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
    Jul 29 11:31:22 arch dhcpcd[230]: wlp16s0: if_sendrawpacket: Network is down
    Jul 29 11:31:22 arch dhcpcd[230]: wlp16s0: dhcp if_readrawpacket: Network is down
    Jul 29 11:31:25 arch dhcpcd[230]: wlp16s0: if_sendrawpacket: Network is down
    Jul 29 11:31:25 arch dhcpcd[230]: wlp16s0: dhcp if_readrawpacket: Network is down
    Jul 29 11:31:29 arch dhcpcd[230]: wlp16s0: if_sendrawpacket: Network is down
    Jul 29 11:31:29 arch dhcpcd[230]: wlp16s0: dhcp if_readrawpacket: Network is down
    Jul 29 11:31:29 arch sudo[607]: norman : TTY=pts/1 ; PWD=/home/norman ; USER=root ; COMMAND=/usr/bin/systemctl restart netctl-auto@wlp16s0
    Jul 29 11:31:29 arch wpa_actiond[317]: Terminating wpa_actiond session for interface 'wlp16s0'
    Jul 29 11:31:33 arch dhcpcd[230]: wlp16s0: if_sendrawpacket: Network is down
    Jul 29 11:31:33 arch dhcpcd[230]: wlp16s0: dhcp if_readrawpacket: Network is down
    Jul 29 11:31:37 arch dhcpcd[230]: wlp16s0: if_sendrawpacket: Network is down
    Jul 29 11:31:37 arch dhcpcd[230]: wlp16s0: dhcp if_readrawpacket: Network is down
    Jul 29 11:31:41 arch netctl-auto[633]: Included profile 'wlp16s0-Matviak'
    Jul 29 11:31:41 arch netctl-auto[633]: Included profile 'wlp16s0-WIRELESS'
    Jul 29 11:31:41 arch dhcpcd[230]: wlp16s0: if_sendrawpacket: Network is down
    Jul 29 11:31:41 arch dhcpcd[230]: wlp16s0: dhcp if_readrawpacket: Network is down
    Jul 29 11:31:41 arch kernel: IPv6: ADDRCONF(NETDEV_UP): wlp16s0: link is not ready
    Jul 29 11:31:41 arch wpa_actiond[651]: Starting wpa_actiond session for interface 'wlp16s0'
    Jul 29 11:31:43 arch kernel: wlp16s0: authenticate with f8:1a:67:d3:6f:aa
    Jul 29 11:31:43 arch kernel: wlp16s0: send auth to f8:1a:67:d3:6f:aa (try 1/3)
    Jul 29 11:31:43 arch kernel: wlp16s0: authenticated
    Jul 29 11:31:43 arch kernel: wlp16s0: associate with f8:1a:67:d3:6f:aa (try 1/3)
    Jul 29 11:31:43 arch kernel: wlp16s0: RX AssocResp from f8:1a:67:d3:6f:aa (capab=0x421 status=0 aid=2)
    Jul 29 11:31:43 arch kernel: wlp16s0: associated
    Jul 29 11:31:43 arch kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp16s0: link becomes ready
    Jul 29 11:31:43 arch dhcpcd[230]: wlp16s0: carrier acquired
    Jul 29 11:31:43 arch wpa_actiond[651]: Interface 'wlp16s0' connected to network 'WIRELESS'
    Jul 29 11:31:43 arch dhcpcd[230]: wlp16s0: adding address fe80::ad30:b256:e3a3:dbd0
    Jul 29 11:31:43 arch dhcpcd[230]: wlp16s0: IAID e0:20:c5:69
    Jul 29 11:31:43 arch dhcpcd[230]: control command: dhcpcd -4 -q -t 30 -K -L wlp16s0
    Jul 29 11:31:43 arch dhcpcd[230]: wlp16s0: soliciting a DHCP lease
    Jul 29 11:31:43 arch dhcpcd[230]: wlp16s0: offered 192.168.0.100 from 192.168.0.1
    Jul 29 11:31:44 arch dhcpcd[230]: wlp16s0: soliciting an IPv6 router
    Jul 29 11:31:48 arch dhcpcd[230]: wlp16s0: leased 192.168.0.100 for 7200 seconds
    Jul 29 11:31:48 arch dhcpcd[230]: wlp16s0: adding route to 192.168.0.0/24
    Jul 29 11:31:48 arch dhcpcd[230]: wlp16s0: adding default route via 192.168.0.1
    Jul 29 11:31:56 arch dhcpcd[230]: wlp16s0: no IPv6 Routers available
    Blank line omits dozens of repeated "Network is down", etc.

  • Netctl profile works flawlessly unless called by netctl-auto

    I have four wireless profiles in /etc/netctl and all of them work just fine when used manually, i.e. netctl enable <profile> or netctl start <profile>, but when I set up netctl-auto one of them keeps failing.
    The three others are identical except for the SSID and the WPA key so I'm including just one of them here along with the one the keeps failing, but there's really nothing special here. The only difference is that the one that keeps failing has a hidden SSID.
    One of the three which work:
    Description='WiFi: AMPERSAND'
    Interface=wlan0
    Connection=wireless
    Security=wpa
    IP=dhcp
    ESSID='ampersand'
    # Prepend hexadecimal keys with \"
    # If your key starts with ", write it as '""<key>"'
    # See also: the section on special quoting rules in netctl.profile(5)
    Key='0f20f8g0fg2'
    # Uncomment this if your ssid is hidden
    #Hidden=yes
    The one that doesn't:
    Description='WiFi: HANLUKIO'
    Interface=wlan0
    Connection=wireless
    Security=wpa
    IP=dhcp
    ESSID='kjKJls83jpkskKkkUyasjqKAS'
    # Prepend hexadecimal keys with \"
    # If your key starts with ", write it as '""<key>"'
    # See also: the section on special quoting rules in netctl.profile(5)
    Key='CCyzJvIVljL9hsHSbhspPhs929c0hLssh38sPssofo382d8OS320dgSop3hfIGdi32GF'
    # Uncomment this if your ssid is hidden
    Hidden=yes
    The wiki doesn't seem to mention anything specific concerning a hidden SSID and netctl-auto, and since all four work flawlessly when used manually, I'm out of ideas. I'll try setting $NETCTL_DEBUG on the next try and hopefully that will output something meaningful but that wont be till next week and I was curious if anyone knew off the bat what the issue might me.

    As I understand man netctl.special, the netctl-auto does not honor the WPADriver parameters in the profiles, because it works on the interface level. Hence, the "Hidden=yes" is not parsed and the hidden ones are probably discarded.
    You should be able to add the parameter "scan_ssid=1" (or "Hidden=yes" - not sure) to a hook for the interface in /etc/netctl/interfaces/
    edit: wrong semantics striked; see below.
    Last edited by Strike0 (2013-12-16 22:16:36)

  • [SOLVED] netctl-auto not working, and I cannot remove netctl instance

    Hi, I installed Arch a few days ago, netctl-auto was working yesterday but today it's not.
    Note that
    netctl start
    works: I have a problem with netctl-auto only.
    $ ping -c 3 8.8.8.8
    connect: Network in unreachable
    I have created only one netctl profile so far, it's called wlp4s0-VM581389-2G (wlp4s0 is the name of my wireless interface)
    $ ls /etc/netctl
    examples hooks interfaces wlp4s0-VM581389-2G
    $ netctl list
    wlp4s0-VM581389-2G
    wpa_actiond is installed, and I have done
    systemctl enable [email protected]
    But for some reason I have some extra netctl@ instances that shouldn't be there. I am wondering if they could be the cause of netctl-auto not working properly:
    $ systemctl | grep netctl
    [email protected] loaded active running Automatic wireless network connection using netctl profiles
    ● netctl@my\x2dnetwork.service loaded failed failed Networking for netctl profile my-network
    ● netctl@wlp4s0\x2dVM581389\x2d2G.service loaded failed failed Networking for netctl profile wlp4s0-VM581389-2G
    system-netctl.slice loaded active active system-netctl.slice
    system-netctl\x2dauto.slice loaded active active system-netctl\x2dauto.slice
    - What are these bullet points at the beginning of these two lines?
    - Where do netctl@my\x2dnetwork.service and netctl@wlp4s0\x2dVM581389\x2d2G.service come from? They might be instances that I had enabled in the past.
    These instances are not enabled and they are inactive, but they are loaded!
    $ systemctl is-enabled netctl@my\x2dnetwork.service
    Failed to get unit file state for [email protected]: No such file or directory
    $ systemctl status netctl@my\x2dnetwork.service
    ● [email protected] - Networking for netctl profile myx2dnetwork
    Loaded: loaded (/usr/lib/systemd/system/[email protected]; static; vendor preset: disabled)
    Active: inactive (dead)
    Docs: man:netctl.profile(5)
    I have tried to get rid of them, but not managed:
    $ systemctl stop netctl@my\x2dnetwork.service
    $ systemctl disable netctl@my\x2dnetwork.service
    $ systemctl | grep netctl
    [email protected] loaded active running Automatic wireless network connection using netctl profiles
    netctl.service loaded active exited (Re)store the netctl profile state
    ● netctl@my\x2dnetwork.service loaded failed failed Networking for netctl profile my-network
    ● netctl@wlp4s0\x2dVM581389\x2d2G.service loaded failed failed Networking for netctl profile wlp4s0-VM581389-2G
    system-netctl.slice loaded active active system-netctl.slice
    system-netctl\x2dauto.slice loaded active active system-netctl\x2dauto.slice
    [user@mascip-toshiba ~]$ systemctl daemon-reload
    [user@mascip-toshiba ~]$ systemctl | grep netctl
    [email protected] loaded active running Automatic wireless network connection using netctl profiles
    netctl.service loaded active exited (Re)store the netctl profile state
    ● netctl@my\x2dnetwork.service loaded failed failed Networking for netctl profile my-network
    ● netctl@wlp4s0\x2dVM581389\x2d2G.service loaded failed failed Networking for netctl profile wlp4s0-VM581389-2G
    system-netctl.slice loaded active active system-netctl.slice
    system-netctl\x2dauto.slice loaded active active system-netctl\x2dauto.slice
    Also, I have tried to check with
    netctl-auto list
    , which gives an empty output. I am guessing that it's normal, because the netctl-auto instances are managed by systemd?
    Now, trying to understand what is happening to [email protected]: as seen before with systemctl | grep netctl, it is active and running.
    Then I do:
    $ journalctl -u [email protected]
    -- Reboot --
    Feb 10 17:34:23netctl-auto[270]: Included profile: 'wlp4s0-VM581389-2G'
    wpa_actiond[310]: Starting wpa_actiond session for interface 'wlp4s0'
    So, a wpa_actiond session was started, but I still cannot ping 8.8.8.8. Why?
    Investigating further:
    $ netctl status wlp4s0-VM581389-2G
    ● netctl@wlp4s0\x2dVM581389\x2d2G.service - Networking for netctl profile wlp4s0-VM581389-2G
    Loaded: loaded (/usr/lib/systemd/system/[email protected]; static; vendor preset: disabled)
    Active: failed (Result: exit-code) since Tue 2015-02-10 19:43:17 GMT; 3min 16s ago
    Docs: man:netctl.profile(5)
    Process: 274 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
    Main PID: 274 (code=exited, status=1/FAILURE)
    Feb 10 19:43:15 mascip-toshiba network[274]: Failed to initialize control interface '/run/wpa_supplicant'.
    Feb 10 19:43:15 mascip-toshiba network[274]: You may have another wpa_supplicant process already running or the file was
    Feb 10 19:43:15 mascip-toshiba network[274]: left by an unclean termination of wpa_supplicant in which case you will need
    Feb 10 19:43:15 mascip-toshiba network[274]: to manually remove this file before starting wpa_supplicant again.
    Feb 10 19:43:17 mascip-toshiba network[274]: The WPA supplicant did not start for interface 'wlp4s0'
    Feb 10 19:43:17 mascip-toshiba network[274]: Failed to bring the network up for profile 'wlp4s0-VM581389-2G'
    Feb 10 19:43:17 mascip-toshiba systemd[1]: netctl@wlp4s0\x2dVM581389\x2d2G.service: main process exited, code=exited, status=1/FAILURE
    Feb 10 19:43:17 mascip-toshiba systemd[1]: Failed to start Networking for netctl profile wlp4s0-VM581389-2G.
    Feb 10 19:43:17 mascip-toshiba systemd[1]: Unit netctl@wlp4s0\x2dVM581389\x2d2G.service entered failed state.
    Feb 10 19:43:17 mascip-toshiba systemd[1]: netctl@wlp4s0\x2dVM581389\x2d2G.service failed.
    "You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again."
    What does this mean? Which file might have been left by an unclean termination? I tried to find this info in the wpa_supplicant documentation, and by searching on Google, but couldn't find anything.
    Now I am lost:
    - how do I get rid of these two undesired netctl instances?
    - where can I investigate next, to get netctl-auto@wlp4s0 to work?
    Any help greatly appreciated :-)
    Last edited by mascip (2015-02-13 11:15:38)

    What is the output of:
    ls -l /etc/systemd/system/multi-user.target.wants
    netctl-auto cannot be used with explicitly enabled profiles (ie, those for which you have used `netctl enable <profile>`).

  • Netctl-auto cannot connect after unblocking wifi

    Hello,
    I'm using netctl as a connection manager. Systemd automatically starts "netctl-auto@wlp1s0" and if I boot system with wifi unblocked (rfkill) it is working fine. But when I boot my system with wifi blocked (from previous session) and after boot I manually unblock it (using rfkill unblock wifi), it doesn't pick up network. And when I try "sudo netctl-auto swtich-to <network_name> it prints out:
    WPA association/authentication failed for interface 'wlp1s0'
    It also happens when I'm working without connection with blocked wifi (for saving the battery) and then I turn wifi on - it also doesn't pick up a network.
    I have to first do:
    systemctl restart netctl-auto@wlp1s0
    which blocks wifi (when I try rfkill list, I can see that this restart blocked it) and only if I immediately switch wifi on (also using rfkill), it connect as usual.
    Does anyone experience same issue? Is it normal behaviour? Thanks

    I think you are seeing a manifestation of this bug.
    Note that I wrote that report.
    Last edited by ewaller (2014-03-27 15:01:50)

  • Netctl-auto Is Not Observing Priority

    I have been using netctl with a single profile for the past few months without issue. My universities network offers a (much faster) WPA network in addition to a (more available) guest network. I am trying to configure netctl-auto to connect to these profiles using the Priority parameter in the profiles. I have set Priority=100 for WPA and Priority=75 for the guest network. Whenever I reboot my machine the guest network is selected and activated by netctl-auto even though the priority is set to use WPA.
    Would anyone have any insight as to why the priority is being ignored?

    I am having a similar issue, and would like to have a fix. I have 3 competing profiles, two guest networks and one eduroam. The first two profiles are simple, set up pretty much exactly as examples/wireless-open, and have Priority=1 and =2, respectively. The eduroam account contains a WPAConfigSection, and has Priority=3. Netctl-auto will not ahdere to these priorities. In order to start eduroam,  I need to “netctl-auto disable” both guest profiles.

  • Netctl-auto stoped working [Solved]

    After update yesterday, netctl-auto stoped working. Netctl start MyProfile works OK.
    Something I have missed during update?
    Last edited by torors (2013-11-17 21:09:09)

    I think another version of netctl has been pushed to the repos.  Maybe you should try updating again and see if your issues are resolved by the updated package.
    pacman -Qi netctl
    Name : netctl
    Version : 1.4-2
    <snip>
    Build Date : Sun 17 Nov 2013 01:37:39 AM PST
    Install Date : Sun 17 Nov 2013 08:56:25 AM PST
    <snip>

  • Netctl-auto fails every second boot

    So, since about two oder three days ago, my netctl-auto fails every second boot and I can't even enable a profile manually.
    I already found this thread: https://bbs.archlinux.org/viewtopic.php?pid=1275755
    But I checked and don't have any failed units and dhcpcd is not running.
    I will do some further investigation and post it here. Any ideas for solutions are welcome
    Wolle

    I've been having the same problem as well, it boots up just fine then after a reboot netctl-auto fails which had been going on for me for the past 30 minutes without "fixing" itself.
    After I added the line:
    TimeoutDHCP=30
    to my profile then rebooted, it worked. It could be a fluke "fix" but worth a try. I *think* the reason it worked is that the default timeout is 10 seconds which might not be enough to establish a connection for some routers/network cards.
    EDIT: I did another boot to see if it was a fluke, and it was. I'm getting a little tired of netctl-auto... I'm going to just disable it and manually do a "netctl start <profile>" after I boot up.
    Last edited by DukeH (2013-07-16 19:07:58)

  • Netctl: Using netctl-ifplugd and netctl-auto simultaneously?

    Hi! I've recently been having difficulties with Wicd, and have decided to try replacing it netctl. I've already got working profiles, but one thing that I would like to have working is multiple-interface automatic connection. As it is now (having both services enabled) a race condition exists, where one interface may hijack the default route, have no default route if one of them disconnects, or have a gateway conflict where no IP or Route is assigned to the interface.
    I have two profiles for my home network, and I'd like to be able to use ethernet while at my desk and wireless while moving about the house. I'm currently dealing with this by leaving -ifplugd enabled, and only enabling -auto if I need to use a wireless connection, then disabling it before I reconnect to wired.
    Is there a better, and more automated way of dealing with this situation?
    Thanks in advance.

    djo: The issue with that in my situation is that I require a static IP, and my locked-down Comcast gateway's pseudo-static DHCP option is extremely buggy. As crappy as it is, it does the job well enough to not warrant a separate router, especially since most of the good ones that support OpenWRT are quite pricey. I haven't really found a solution to the original problem, and still employ my original workaround, since entering my password once isn't much of an inconvenience.
    Šaran: Well they're both in the subnet, and can automatically connect at the same time. Both are supposed to be used as my machine's default route, so things get kinda wonky when two interfaces are connected to the same network fighting over who gets to provide the default route. Since your situation has only one interface that needs to serve the machine's default gateway, you don't run into that problem when both of them are trying to connect/disconnect at the same time.
    WonderWoofy: I was actually messing around with this as a possible solution when I first posted the problem. If I remember correctly, I couldn't manage to get it to play nicely, but I'll give it another shot in the morning to see if I can figure it out. I'd only messed with the ExecUp/ExecDown options, but hooks actually look like a far better candidate to solve this issue (as well as re-implementing some of my wicd-scripts.)

  • Netctl-auto wireless hangs on boot if there is no wireless device

    Hello!
    I've configured netctl to autostart wireless profiles according to wiki and it works pretty well except for one issue. If there is no wireless device on boot time, systemd sticks on [email protected] for about a minute until it finally fails, and only after that system continues to boot.
    Is there any way to make systemd skip this unit if there aren't any wireless interfaces at boot time? Or, better, to make netctl aware of the hardware situation and just prevent it from waiting so long for something that isn't going to happen.
    Last edited by Axon (2014-02-03 10:10:52)

    Yes.

  • Unable to connect wifi via netctl - Unregistered Authentication Agent

    I have a previous post int the Newbie Corner that went unanswered, so I figured I'd try again here now that I have some new information. The post is here...
    https://bbs.archlinux.org/viewtopic.php?id=197031
    And here's a copy of that post so you don't have to open it in a new tab.
    ORIGINAL POST:
    I have continually been having issues with netctl failing to start an automatic profile for awhile now, but I have been able to manually bring up my connection once my system is up and running. Today I am running into the issue where netctl will outright fail to connect during a manual attempt. When viewing journalctl -xe the error I receive is:
    WPA association/authentication failed for interface 'wlan0'
    Failed to bring the network up for profile
    I noticed that there is a 'fix' for this issue on the Arch Wiki which simply states to bring wlan0 down with ip link, then to start the profile with netctl again. I went ahead and gave that fix a try and got a new error.
    Unregistered Authentication Agent for unix-process:1324:44567
    The error goes on to provide a path to .../PolicyKit1/AuthenticationAgent,.
    I have tried using NetworkManager as well, but I'd prefer not to use it as I seem to have more problems with it over netctl, and that is why I currently have it disabled. Any advice on how to proceed would be appreciated. Also, I was connected to my home wifi last night without a problem, and I have tested the wifi connection with my phone, which authenticates and connects without a problem.
    EDIT:
    I did a bit more digging and found some startup errors issues via dmesg with wlan0.
    IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    wlan0: authenticate with 00:24:b2:71:b8:27
    wlan0: direct probe to 00:24:b2:71:b8:27 (try 1/3)
    wlan0: direct probe to 00:24:b2:71:b8:27 (try 2/3)
    wlan0: direct probe to 00:24:b2:71:b8:27 (try 3/3)
    wlan0: authentication with 00:24:b2:71:b8:27 timed out
    The last 5 lines of this error repeats about 7 times before stopping. I use a broadcom card and my 43xx driver loads without a problem, I've been using it for awhile now on various distros.
    b43-phy0: Broadcom 4311 WLAN found (core revision 10)
    EDIT:
    Well after doing some research, I found this existing bug.
    https://bugs.archlinux.org/task/44821
    Involving wifi not working under kernel 4.0.1. I noticed a Broadcom card listed by one of the users who was having the same problem, so at this point I'm probably going to wait until I get home to test my laptop on my home wifi again, then if I run into problems I'll downgrade my kernel and see how things go.
    NEW POST:
    So after all of that I tried my laptop at home again, and netctl-auto connected flawlessly to my wifi at home, which has led me to believe that the problem has to do with the message...
    polkitd[1087]: Unregistered Authentication Agent for unix-process:2582:96758
    I had previously noted that I would downgrade my kernel, but at this point I'd hate to do that considering netctl-auto is working.
    I have also tried connecting via wifi-menu, and when I try that I get the message
    Interface 'wlan0' is controlled by netctl-auto
    After which authentication fails. I have stopped netctl-auto via systemctl using systemctl stop [email protected] and tried again. I end up receiving the message error message from systemctl that the job failed, and viewing journalctl -xe shows the recurring Unregistered Authentication Agent from polkitd.
    Any help would be appreciated.
    EDIT:
    The issue continues. I have enabled the netctl profile I am currently working in netctl-auto with netctl enable profile, and that has not allowed the profile to automatically start up as it would with my home wireless connection. Something I have been noticing is that upon boot, without attempting to connect with netctl, is that wlan0 is not up.
    IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    I have manually brought it up and immediately receive a failed message from systemd regarding my profile in netctl. If I do not manually bring it up with ip link set dev wlan0 up, then when I try to connect with netctl start profile, netctl will not bring wlan0 up and it will leave it in it's previous state.
    The odd thing is, even with wlan0 in a down state, systemd is giving me the error message...
    WPA association/authentication failed for interface 'wlan0'
    Which is odd because netctl shouldn't be able to pass authentication is wlan0 is still down.
    I've been at this for 2 days now and am no closer to fixing this than I was yesterday. I could really use some assistance. At this point I believe I may just downgrade my kernel and hope this fixes the issue, if not then I'm silently hoping my laptop won't connect to my home wifi when I get home so I can diagnose this problem via ethernet.
    EDIT:
    Well here's something new. When viewing why netctl-auto fails on startup via systemctl status [email protected] I am getting the reason of
    Could not create the configuration file for interface wlan0
    At least now I have a bit more to work with.
    Last edited by barefly (2015-05-06 22:30:39)

    Use this article: iOS: Wi-Fi settings grayed out or dim - Support - Apple
    Follow all of the troubleshooting steps.  You can even try restoring the device as new: iOS: How to back up your data and set up your device as a new device
    If the wi-fi remains greyed out, your device needs service.
    If within warranty, it should be free.
    If not, it will probably cost $199 USD + tax.

  • Netctl fails with "link is not ready"

    Hi all
    I was hoping that you can help me out! I'm new to archlinux so please accept my apologies if I've missed something obvious.
    I've just setup a new archlinux system on my HP N40L according to the archwiki beginner's guide and this btrfs guide.
    I want to automatically connect to the internet with a static ip via ethernet cable.
    netctl setup
    cp /etc/netctl/examples/ethernet-static /etc/netctl/ethernet
    nano /etc/netctl/ethernet
    netctl start ethernet
    netctl profile
    Description='A basic static ethernet connection'
    Interface=enp2s0
    Connection=ethernet
    IP=static
    Address=('192.168.1.212/24')
    #Routes=('192.168.0.0/24 via 192.168.1.2')
    Gateway='192.168.1.1'
    DNS=('62.24.128.17')
    ## For IPv6 autoconfiguration
    #IP6=stateless
    ## For IPv6 static address configuration
    #IP6=static
    #Address6=('1234:5678:9abc:def::1/64' '1234:3456::123/96')
    #Routes6=('abcd::1234')
    #Gateway6='1234:0:123::abcd'
    journalctl output
    Jul 21 21:52:50 arch network[340]: Starting network profile 'ethernet'...
    Jul 21 21:52:50 arch kernel: tg3 0000:02:00.0: irq 43 for MSI/MSI-X
    Jul 21 21:52:51 arch kernel: IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
    Jul 21 21:52:56 arch network[340]: No connection on interface 'enp2s0'
    Jul 21 21:52:57 arch network[340]: Failed to bring the network up for profile 'ethernet'
    Jul 21 21:52:57 arch systemd[1]: [email protected]: main process exited, code=exited, status=1/FAILURE
    Jul 21 21:52:57 arch systemd[1]: Failed to start A basic static ethernet connection.
    Jul 21 21:52:57 arch systemd[1]: Unit [email protected] entered failed state.
    dmesg output for ethernet card module
    [ 4.576037] tg3.c:v3.130 (February 14, 2013)
    [ 4.621520] tg3 0000:02:00.0 eth0: Tigon3 [partno(BCM95723) rev 5784100] (PCI Express) MAC address a0:b3:cc:df:1e:7f
    [ 4.621526] tg3 0000:02:00.0 eth0: attached PHY is 5784 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
    [ 4.621530] tg3 0000:02:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
    [ 4.621533] tg3 0000:02:00.0 eth0: dma_rwctrl[76180000] dma_mask[64-bit]
    [ 31.196779] tg3 0000:02:00.0: irq 43 for MSI/MSI-X
    I can connect if I use these commands so there's no physical problem with hardware.
    ip link set enp2s0 up
    ip addr add 192.168.1.200/24 dev enp2s0
    ip route add default via 192.168.1.1
    or
    systemctl start dhcpcd@enp2s0
    I also tried to bring the interface up first.
    ip link set enp2s0 up
    netctl start ethernet
    journalctl output
    Jul 21 22:00:47 arch network[438]: Starting network profile 'ethernet'...
    Jul 21 22:00:47 arch network[438]: The interface of network profile 'ethernet' is already up
    Jul 21 22:00:47 arch systemd[1]: [email protected]: main process exited, code=exited, status=1/FAILURE
    Jul 21 22:00:47 arch systemd[1]: Failed to start A basic static ethernet connection.
    systemctl output
    UNIT LOAD ACTIVE SUB DESCRIPTION
    proc-sys...t_misc.automount loaded active waiting Arbitrary Executable File Formats File System Automount Point
    sys-devi...und-card0.device loaded active plugged GF119 HDMI Audio Controller
    sys-devi...et-enp2s0.device loaded active plugged NC107i Integrated PCI Express Gigabit Server Adapter
    sys-devi...-sda-sda1.device loaded active plugged SAMSUNG_SSD_830_Series
    sys-devi...-sda-sda2.device loaded active plugged SAMSUNG_SSD_830_Series
    sys-devi...block-sda.device loaded active plugged SAMSUNG_SSD_830_Series
    sys-devi...tty-ttyS0.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS0
    sys-devi...tty-ttyS1.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS1
    sys-devi...tty-ttyS2.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS2
    sys-devi...tty-ttyS3.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS3
    sys-module-configfs.device loaded active plugged /sys/module/configfs
    sys-subs...es-enp2s0.device loaded active plugged NC107i Integrated PCI Express Gigabit Server Adapter
    -.mount loaded active mounted /
    dev-hugepages.mount loaded active mounted Huge Pages File System
    dev-mqueue.mount loaded active mounted POSIX Message Queue File System
    sys-kernel-config.mount loaded active mounted Configuration File System
    sys-kernel-debug.mount loaded active mounted Debug File System
    tmp.mount loaded active mounted Temporary Directory
    systemd-...ord-console.path loaded active waiting Dispatch Password Requests to Console Directory Watch
    systemd-...ssword-wall.path loaded active waiting Forward Password Requests to Wall Directory Watch
    dbus.service loaded active running D-Bus System Message Bus
    [email protected] loaded active running Getty on tty1
    [email protected] loaded failed failed A basic static ethernet connection
    sshd.service loaded active running OpenSSH Daemon
    systemd-journald.service loaded active running Journal Service
    systemd-logind.service loaded active running Login Service
    systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
    systemd-sysctl.service loaded active exited Apply Kernel Variables
    systemd-...es-setup.service loaded active exited Recreate Volatile Files and Directories
    systemd-...-trigger.service loaded active exited udev Coldplug all Devices
    systemd-udevd.service loaded active running udev Kernel Device Manager
    systemd-update-utmp.service loaded active exited Update UTMP about System Reboot/Shutdown
    systemd-...sessions.service loaded active exited Permit User Sessions
    systemd-...le-setup.service loaded active exited Setup Virtual Console
    dbus.socket loaded active running D-Bus System Message Bus Socket
    dmeventd.socket loaded active listening Device-mapper event daemon FIFOs
    lvmetad.socket loaded active listening LVM2 metadata daemon socket
    systemd-initctl.socket loaded active listening /dev/initctl Compatibility Named Pipe
    systemd-journald.socket loaded active running Journal Socket
    systemd-shutdownd.socket loaded active listening Delayed Shutdown Socket
    systemd-...d-control.socket loaded active listening udev Control Socket
    systemd-udevd-kernel.socket loaded active running udev Kernel Socket
    basic.target loaded active active Basic System
    cryptsetup.target loaded active active Encrypted Volumes
    getty.target loaded active active Login Prompts
    graphical.target loaded active active Graphical Interface
    local-fs-pre.target loaded active active Local File Systems (Pre)
    local-fs.target loaded active active Local File Systems
    multi-user.target loaded active active Multi-User System
    network.target loaded active active Network
    paths.target loaded active active Paths
    remote-fs.target loaded active active Remote File Systems
    sockets.target loaded active active Sockets
    sound.target loaded active active Sound Card
    swap.target loaded active active Swap
    sysinit.target loaded active active System Initialization
    timers.target loaded active active Timers
    systemd-...iles-clean.timer loaded active waiting Daily Cleanup of Temporary Directories
    LOAD = Reflects whether the unit definition was properly loaded.
    ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
    SUB = The low-level unit activation state, values depend on unit type.
    58 loaded units listed. Pass --all to see loaded but inactive units, too.
    To show all installed unit files use 'systemctl list-unit-files'.
    My modem router (192.168.1.1) handles DNS and DHCP (192.168.1.2 - 192.168.1.254).
    I tried change the address pool to 192.168.1.2 - 192.168.1.253 and setting my computer's ip to 192.168.1.254 to avoid possible conflicts but this made no difference.
    I have only installed packages from the base group and the packages openssh, amd-ucode and btrfs-progs.
    thanks for the help - hopefully it's something simple I've missed
    EDIT
    I've found out that the following works
    pacman -S ifplugd
    systemctl start [email protected]
    does anyone know why the beginner's guide wasn't working for me? is there a bug with netctl?
    Last edited by tadetter (2013-07-22 22:11:17)

    Thanks for the pointer Lone_Wolf.
    I've opted for the method you linked to as it means I can remove netctl and ifplugd.
    [Unit]
    Description=Wired Static IP Connectivity
    Wants=network.target
    Before=network.target
    BindsTo=sys-subsystem-net-devices-enp2s0.device
    After=sys-subsystem-net-devices-enp2s0.device
    [Service]
    Type=oneshot
    RemainAfterExit=yes
    ExecStart=/usr/bin/ip link set dev enp2s0 up
    ExecStart=/usr/bin/ip addr add 192.168.1.254/24 dev enp2s0
    ExecStart=/usr/bin/ip route add default via 192.168.1.1
    ExecStop=/usr/bin/ip addr flush dev enp2s0
    ExecStop=/usr/bin/ip link set dev enp2s0 down
    [Install]
    WantedBy=multi-user.target
    I guess this is a solution sorts, although the original issue remains unsolved.
    Is it worth cross posting to netctl on git?
    Last edited by tadetter (2013-07-22 22:11:38)

Maybe you are looking for