WireGuard server AllowedIPs: duplicate ranges cut peers off, host bits only widen trust
A common server-side mistake is giving every peer the same AllowedIPs range, such as 10.8.0.0/24, which makes WireGuard keep one owner per range and leave the earlier peer with no traffic while its handshake still succeeds. The author tested this on Linux 6.8 with wireguard-tools, confirming that the last-loaded peer takes the shared range. Writing a client address with a subnet prefix, such as 10.8.0.2/24, is less immediately harmful because the peer keeps its own /32 routing, but it makes every unassigned address in the subnet route to that peer and lets it send with any source address in the subnet. The author's config checker previously reported both cases identically, so it now separates a current error from a trust warning. The article gives /32 per client as the fix.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in