core-agent-linux/vm-systemd/NetworkManager.service.d/30_qubes.conf

[Unit]
ConditionPathExists=/var/run/qubes-service/network-manager
# For /rw
After=qubes-mount-dirs.service
# For /var/run/qubes-service
After=qubes-sysinit.service
# For configuration of qubes-provided interfaces
After=qubes-network-uplink.service

[Service]
ExecStartPre=/usr/lib/qubes/network-manager-prepare-conf-dir
vm/init: introduce SystemD startup scripts 2012-01-10 12:10:16 +01:00			`[Unit]`
			`ConditionPathExists=/var/run/qubes-service/network-manager`
vm/network: symlink NetworkManager system-connection to /rw (#425) In FC15, NetworkManager by default uses global connections ("Available to all users"). Save them in /rw instead of /etc, to preserve them across reboots. 2012-01-30 14:20:02 +01:00			`# For /rw`
systemd: improve ordering of systemd units - qubes-misc-post.service is no longer responsible for mounting /rw - both qubes-sysinit.service and qubes-mount-dirs.service are part of basic.target, so no need to mention them explicitly (as long as DefaultDependencies=yes) QubesOS/qubes-issues#2198 2016-07-27 05:13:21 +02:00			`After=qubes-mount-dirs.service`
			`# For /var/run/qubes-service`
			`After=qubes-sysinit.service`
Order NetworkManager after qubes-network-uplink.service Make sure NM config for uplink interface (eth0) is created before starting NetworkManager itself. Otherwise NM helpfully will try to use automatic DHCP configuration, which will fail and cause delays on network start. 2020-12-05 18:13:27 +01:00			`# For configuration of qubes-provided interfaces`
			`After=qubes-network-uplink.service`
vm/network: symlink NetworkManager system-connection to /rw (#425) In FC15, NetworkManager by default uses global connections ("Available to all users"). Save them in /rw instead of /etc, to preserve them across reboots. 2012-01-30 14:20:02 +01:00
			`[Service]`
			`ExecStartPre=/usr/lib/qubes/network-manager-prepare-conf-dir`