ifupdown1 have a service to launch "udevadm settle",
to be sure that networking devices are correctly setup
before networking service is started.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920623
Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
we don't want state_dir persistent across reboot.
I have add some ifreload hanging after a crash, with non existing old interfaces
Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
ifupdown2.0 now setup address in pre-up, but ovs script also
create in pre-up, but after address module.
This patch execute addons scripts before ifupdown modules
Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
commit 214bc505ac removed this by
mistake. While I fix it before detecting that (thank Wolfgang!) lets
restore it more like the state it was.
Add missing ordering:
After=network-pre.target
See systemd.special(7)'s description of this target
After=systemd-sysctl.service
ifupdown does the same - we want net.*.conf.default.*
sysctl keys to apply to newly created interfaces
After=systemd-modules-load.service
ifupdown does the same, though this should be mostly
optional as modules should be autoloaded anyway
Before=network.target
This is required to prevent services which require
network to be started too early and listen on wrong
addresses (iow. only on loopback or ipv4-only).
Before=network-online.target
See systemd.special(7)'s description. We are the
provider of this target.
Before=shutdown.target
ifupdown does it this way, it also makes more sense
given the Conflict entry, compared to the previous
WantedBy entry in [Install]
Changed install section:
WantedBy=multi-user.target
I wasn't sure about this. ifupdown does this.
basic.target didn't seem useful since we actually want:
WantedBy=network-online.target
We provide this, so we should be installed into it.
removed WantedBy=network.target
We strictly want to be ordered before this and instead
are required by multi-user.target already.
removed WantedBy=shutdown.target
I didn't see the point.
Originally-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
It was wrong set to 1, and break openvswitch
Ifupdown2 was 1 by default last year,
and the first version ofpatch was setting to 0.
But ifupdown2 was reverted to 0 in 2019, and I wrongly change the patch to 1.
So now, it's default to 0 , no need to patch it.
Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
to avoid error like
info: vmbr5001: applying bridge port configuration: ['tap111i0']
info: vmbr5001: applying bridge configuration specific to ports
error: 'NoneType' object has no attribute '__getitem__'
Note that ifupdown2 changed its versioning scheme: Instead
of 2.0 this release is 1.2.0.
This version has a release tag, so it _should_ stick now ;-)
Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
