GitLab

Let the netctl profile service yield at the last moment before any
communication on the interface takes place. That way, we catch as many
problems as possible without suffering unpredictable delays.
This means network.target is reached earlier for wireless connections.

Hooks and interface scripts are now sourced more systematically.
Settings of wireless profiles that depend on hooks are now picked up
correctly by netctl-auto.

Suggested by: Vitor Sakaguti <vis@tutao.de>

The name of the subcommand mirrors the same subcommand of systemd-analyze.

Verification before restarting would be useful. However, verification
requires the profile file to be readable by the current user. The current
user may be a regular user with permission to control systemd, so
restarting does not require the profile file to be readable. Therefore, we
do not attempt verification before restarting.

Written mostly by GitHub user tetrakist.

When netctl-ifplugd starts a profile that uses dhcpcd and the interface
disappears (for example because of a re-enumeration after a resume from
suspend), dhcpcd immediately exits, but ifplugd notices that the interface
reappears within a timeout and does not bother reconfiguring it.

This commit disables the ifplugd timeout. If it turns out to be needed for
buggy interfaces, we should implement the desired functionality in the
ifplugd.action script.

Семён Марьясин authored May 31, 2020 and Jouke Witteveen committed Jun 26, 2020

When you call `netctl list`, it calls `systemctl status` for each of the
profiles. By default, `systemctl status` fetches the last log entries from the
journal, which is often a time-consuming operation. Additionally, the status
output is not meant for machine processing.

With dhcpcd 9, the rundir has moved. We follow this change and no longer
support older versions of dhcpcd.
While here, also support information only use on IPv6, which has been
possible with dhcpcd for quite a while already.

Reported by: Antonio Rojas <arojas@archlinux.org>

Also, make sure that netctl does not wait for the interface of a wireguard
connection, since that interface will be created by netctl itself.

Contributed by Thibaut Sautereau <thibaut@sautereau.fr>

Connection types bond, bridge, dummy, vlan, and macvlan create their own
interface. Previously, only macvlan offered control over the MAC address of
the created interface. Now, this functionality is available to all these
connection types.

Thanks to:
Javier <j.e.vasquez.v@gmail.com>
and
David Hummel <hummeltech@dhummel.net>

The same functionality is provided by wpa_supplicant, so we do not need
an extra and Arch Linux specific dependency.

When accept_ra is set to 1, router advertisements are still ignored if
the interface is in forwarding mode. For such configurations, the
interface should have a static configuration and netctl already sets
accept_ra to 0. Setting it to 2 otherwise forces the kernel to accept
router advertisements regardless of the forwarding setting.

Eli Schwartz authored Jan 26, 2019 and Jouke Witteveen committed Feb 07, 2019

The Makefile commands in use include bash-specific features like brace
expansion, and thus cannot run under the default /bin/sh shell as that
may or may not be GNU bash (bash supports brace expansion even in posix
mode).

Consequently, the Makefile failed to execute correctly when the system
/bin/sh was a different sh implementation, such as dash or busybox ash.

Fix this by declaring the SHELL which will be used when running all
commands.

Christoph Hoopmann authored Oct 17, 2018 and Jouke Witteveen committed Nov 15, 2018

Signed-off-by: Christoph Hoopmann <christophhoopmann@gmail.com>

Depend on the interface, not on the implementation.
Nevertheless, for netctl, openresolv is the preferred implementation.

Inside double quotes, backslash is an escape character. Hence, it is
cleaner to use single quotes where backslashes may occur. This includes
pattern strings for print, grep, and sed.

This also allows hooks to alter the profile to be loaded.

The .include directive in systemd unit files has effectively been
deprecated since systemd v210. Its functionality is subsumed by
drop-in directories.

Strictly speaking, we should check with the SSIDEncoding value sent out
by the station, as specified in the 2012 version of 802.11 (page 566),
but wpa_supplicant does not (yet) expose this information and stations
may not set the field to UTF-8 and still encode their SSID accordingly.

We therefore assume SSIDs to be UTF-8 encoded (the only real alternative
is treating SSIDs as raw byte string) in wifi-menu. Note that wifi-menu
is only provided as a convenience and many/most use cases involve
writing profile files manually.

When the current character map is not set to UTF-8, wifi-menu will only
use ASCII characters in its screen output.
This can be forced using for example `LC_CTYPE=C wifi-menu`.

Thanks to Declspeck <declspeck@declblog.com> for their activity on the
Flyspray task.