Fix tinyproxy starting before VPN bridge is configured
Some checks failed
Check Flake / check-flake (push) Has been cancelled
Some checks failed
Check Flake / check-flake (push) Has been cancelled
tinyproxy binds to the bridge IP but had no ordering dependency on systemd-networkd, so it could start before the bridge existed.
This commit is contained in:
@@ -230,7 +230,11 @@ in
|
||||
Port = cfg.proxyPort;
|
||||
};
|
||||
};
|
||||
systemd.services.tinyproxy.before = [ "container@pia-vpn.service" ];
|
||||
systemd.services.tinyproxy = {
|
||||
before = [ "container@pia-vpn.service" ];
|
||||
after = [ "systemd-networkd.service" ];
|
||||
requires = [ "systemd-networkd.service" ];
|
||||
};
|
||||
|
||||
# WireGuard interface creation (host-side oneshot)
|
||||
# Creates the interface in the host namespace so encrypted UDP stays in host netns.
|
||||
|
||||
Reference in New Issue
Block a user