Browse Source

build: add to service files

systemd specifies a special passive target unit ''
which may be pulled in by services that want to run before any network
interface is brought up or configured. Correspondingly, network
management services such as iwd and ead should specify to ensure a proper ordering with respect to
this special target. For more information on, see

Two examples to explain the rationale of this change:

1. On one of our embedded systems running iwd, a oneshot service is
   run on startup to configure - among other things - the MAC address of
   the wireless network interface based on some data in an EEPROM.
   Following the systemd documentation, the oneshot service specifies:

   ... to ensure that it is run before any network management software
   starts. In practice, before this change, iwd was starting up and
   connecting to an AP before the service had finished. iwd would then
   get kicked off by the AP when the MAC address got changed. By
   specifying, systemd will take care to avoid
   this situation.

2. An administrator may wish to use to ensure
   firewall rules are applied before any network management software is
   started. This use-case is described in the systemd documentation[1].
   Since iwd can be used for IP configuration, it should also respect
   the convention.

Note that is a passive unit that is only pulled in if
another unit specifies e.g. If no such unit
exists, this change will have no effect on the order in which systemd
starts iwd or ead.

Alvin Šipraga 2 years ago
committed by Denis Kenzior
  1. 1
  2. 1


@ -1,5 +1,6 @@
Description=Wireless service


@ -1,5 +1,6 @@
Description=Ethernet service