2024-11-27 06:30 UTC
EDIT: Apparently, systemd-networkd was being a fuck
PLEASE BOOST THIS
What is wrong with this config on wireguard (wireguard-tools version v1.0.20210914)? The intent is to allow the clients to connect and access internyal nodes, while also being able to access the internet, with all of their traffic proxied through the VPN. This used to work on prior versions of WireGuard. I don't understand why it doesn't work now.
Server config:[Interface]
Address = 10.0.0.1/24
ListenPort =
PrivateKey =
PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE
[Peer]
PublicKey =
AllowedIPs = 10.0.0.2/32
Client config:[Interface]
PrivateKey =
Address = 10.0.0.2/24
DNS = 8.8.8.8
[Peer]
PublicKey =
AllowedIPs = 0.0.0.0/0, ::/0
Endpoint =
PersistentKeepalive = 30
Replies (0)
No replies.