Fix tinyproxy starting before VPN bridge is configured
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,14 @@ in
|
|||||||
Port = cfg.proxyPort;
|
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" ];
|
||||||
|
serviceConfig.ExecStartPre = [
|
||||||
|
"+${pkgs.systemd}/lib/systemd/systemd-networkd-wait-online --interface=${cfg.bridgeName}:no-carrier --timeout=60"
|
||||||
|
];
|
||||||
|
};
|
||||||
|
|
||||||
# WireGuard interface creation (host-side oneshot)
|
# WireGuard interface creation (host-side oneshot)
|
||||||
# Creates the interface in the host namespace so encrypted UDP stays in host netns.
|
# Creates the interface in the host namespace so encrypted UDP stays in host netns.
|
||||||
|
|||||||
Reference in New Issue
Block a user