Anyone else having the issue of how to distinguish traffic from specific peers, and how did you solve it?
Other than having an interface per peer of course.
Other than having an interface per peer of course.
Eg: my SQL server has one WG and I've got N clients. They are each connecting with their key and assigned IP. So firewall rules will do it.
If routing was possible with just the public key, after wg has verified the packets, I would assume it'd be easier to maintain (and more flexible).
For example, I could run a "public" wg peer where peers could just join me without me messing with cidrs and whatnot. I wouldn't care what their vpn ip is, as I may not be their only peer and they could be using any number of internal addressess.
Obviously inside the tunnel that's what the source IP is for.