crypto routing with subnets?
Jason A. Donenfeld
Jason at zx2c4.com
Fri Oct 20 20:02:43 CEST 2017
Fortunately the inquires of this email are things that you could
figure out simply by trying, so if you want to learn-by-doing, you can
stop reading here and finish reading afterward.
Here are the solutions:
1. A peer is its public key, which means you can't have two different
peers with the same key, since they'd be the same peer. In essence
you're asking for a==a&&a!=a, which is always false.
2. Traffic will always go to the most specific route, which means the
/32 will take precedence over the /16.
More information about the WireGuard