Notices by 4censord (4censord@mstdn.social)

@dwarf yes, we can hear you loud and clear.

@dwarf @momo @flandrescarlet oh, so a devops specialists?

@dwarf No, I wasn't clear with what i meant.

On the server, the client is configured like this:

# Client 1
[Peer]
PublicKey = [...]
AllowedIPs = 10.0.99.3/32

So the client only gets a single address (/32).

On the client side, it is set up like this:

[Interface]
Address = 10.0.99.3/24
PrivateKey = [...]

So the client has a single address (10.0.99.3), but knows its part of a /24 network.

@dwarf How is your clients `Address` set up?
Is it a /32 with only the clients ip, or eg a /24?

For me, the route with the wireguard interface looks like this:

10.0.1.0/24 dev wg1 proto kernel scope link src 10.0.1.4 metric 50

@dwarf I forgot: i have it set up with a /24

@dwarf Can you remove
* the peer config for client1 from client2
* the peer config for client2 from client1

It sounds for me like your clients are trying to connect to each other directly, instead of going via the server.

This fails, because they don't have `Endpoints` configured for each other

@dwarf for me it works without problems. If you want, I can take a look at it later, but you would need describe your setup more.

Does client{1,2} -> server on its own work?

How are you calling ping, "destination address required" sounds more like e.g. it can't resolve the other host vie DNS.

@dwarf Hello

@rqsd @dwarf @astrid isn't essentially a database server with a very predictable load?
So depending on how many things you monitor, this might be completely expected.