Use another subnet for WireGuard tunnel as is conflicts with the openstack internal subnet
This commit is contained in:
parent
4538bfb375
commit
e3b6c9a2bc
5 changed files with 16 additions and 19 deletions
|
@ -20,23 +20,23 @@
|
|||
interfaces.wg0 = {
|
||||
listenPort = 51820;
|
||||
ips = [
|
||||
"172.16.50.1/24"
|
||||
"172.18.50.1/24"
|
||||
];
|
||||
peers = [
|
||||
{
|
||||
name = "mail-2";
|
||||
publicKey = "OIBOJlFzzM3P/u1ftVW2HWt8kA6NveB4PaBOIXhCYhM=";
|
||||
presharedKeyFile = "/secrets/wireguard-lifeline-mail-2-lifeline-psk.secret";
|
||||
allowedIPs = [ "172.16.50.2/32" ];
|
||||
allowedIPs = [ "172.18.50.2/32" ];
|
||||
}
|
||||
];
|
||||
postSetup = ''
|
||||
${pkgs.iptables}/bin/iptables -A FORWARD -i wg0 -j ACCEPT
|
||||
${pkgs.iptables}/bin/iptables -t nat -A POSTROUTING -s 172.16.50.0/24 -o ens6 -j MASQUERADE
|
||||
${pkgs.iptables}/bin/iptables -t nat -A POSTROUTING -s 172.18.50.0/24 -o ens6 -j MASQUERADE
|
||||
'';
|
||||
postShutdown = ''
|
||||
${pkgs.iptables}/bin/iptables -D FORWARD -i wg0 -j ACCEPT
|
||||
${pkgs.iptables}/bin/iptables -t nat -D POSTROUTING -s 172.16.50.0/24 -o ens6 -j MASQUERADE
|
||||
${pkgs.iptables}/bin/iptables -t nat -D POSTROUTING -s 172.18.50.0/24 -o ens6 -j MASQUERADE
|
||||
'';
|
||||
privateKeyFile = "/secrets/wireguard-lifeline-wg0-privatekey.secret";
|
||||
};
|
||||
|
@ -46,7 +46,7 @@
|
|||
internalInterfaces = [ "wg0" ];
|
||||
externalInterface = "ens6";
|
||||
forwardPorts = [{
|
||||
destination = "172.16.50.2:25";
|
||||
destination = "172.18.50.2:25";
|
||||
proto = "tcp";
|
||||
sourcePort = 25;
|
||||
}];
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue