Friday, September 26, 2025

Re: wireguard multiple peers problem: information ignored

On 2025-09-26, Stuart Henderson <stu.lists@spacehopper.org> wrote:
>> [Peer]
>> PublicKey = LJNRAWz8cUS7sO/8PUlc3erIhJw8dkHr9VaDMu2DDzM=
>> AllowedIPs = 192.168.23.0/24
>>
>> [Peer]
>> PublicKey = Bevi0lbafrShca6QruEBw0H2DnlWw7XGHWdgJM1mkn8=
>> AllowedIPs = 192.168.23.0/24
...
>
> Smells like a bug in wireguard-tools perhaps when setting the
> allowed ips.

oh, as Ze Loff pointed out, it's the same address/prefix on both,
yes that won't work.

perhaps WG_PEER_REPLACE_AIPS should possibly reject attempting to
use a wgaip that's already used on another peer, however, then you'd
also need a way to remove an existing wgaip from a peer; currently
it only seems possible to that by assigning it to another peer.

wg is convenient for some things but there are still various
issues hiding ...

--
Please keep replies on the mailing list.

No comments:

Post a Comment