- changed status to new
wireguard generates subnet masks incorrectly
Issue #315
closed
The generated config and the QR code containst Interface IP adress 10.10.0.2/24 and allowed IPs 10.10.0.1/24
Comments (3)
-
repo owner -
repo owner - changed status to closed
Already fixed in latest release.
-
In my case, the route to the peer network (allowed IPs) is not created with the defined subnet mask.
I specified /24 but it’s 255.255.255.255
VPN type is “internal - full mesh”
I have a workaround with the post-up script by removing the wrong route and add the correct one.
- Log in to comment