Addressing the ordering issue in this bug report. On Sun, May 24, 2026 at 10:29:37PM +0200, Petr Gajdůšek wrote: > Two causes: > > 1. Ordering cycle: the unit sets "After=network.target" together with > "Before=network-pre.target". With NetworkManager (network-pre -> NM -> > network.target) this is cyclic; systemd breaks it non-deterministically > and probably may skip ferm entirely. > > ferm.service: Found ordering cycle: NetworkManager.service after > network-pre.target after ferm.service after network.target ...
iptables-persistent does it this way: [Unit] DefaultDependencies=no Wants=network-pre.target systemd-modules-load.service local-fs.target Before=network-pre.target shutdown.target After=systemd-modules-load.service local-fs.target Conflicts=shutdown.target [Install] WantedBy=multi-user.target Is that any better? I cannot try coexistence with network-manager since I don't have network-manager on any of my systems that I regularly boot. Greetings Marc
