@simonebortolin @Cal Ho appena provato e confermo che su Linux NON si perde accesso alla LAN del client, la ragione credo sia la seguente.
https://www.wireguard.com/netns/#routing-all-your-traffic
We first set the fwmark on the interface and set a default route on an alternative routing table. Then we indicate that packets that do not have the fwmark should go to this alternative routing table. And finally we add a convenience feature for still accessing the local network, whereby we allow packets without the fwmark to use the main routing table, not the WireGuard interface's routing table, if it matches any routes in it with a prefix length greater than zero, such as non-default local routes. This is the technique used by the wg-quick(8) tool.
Configurazione del server:
[Interface]
Address = 10.20.30.1/24
PrivateKey = pf5gkErSjaKQgobVrVyyl6c9IfDPx2xVZMB2yXu5abXh
[Peer]
PublicKey = SmAG1PvkM3uQjUwM0uKN1cIxatLoTJTGVHDIjYl8XiUz
PresharedKey = Acasf1nkvC5sxPRfcoYpdQzhNKpMD828jUyNsS64dwdL
AllowedIPs = 10.20.30.2/32
Configurazione del client:
[Interface]
Address = 10.20.30.2/24
PrivateKey = uqZVScTq4ehC5UpM49UvJNnUa8WuUha29yvsqbb3q7IS
DNS = 192.168.12.6
[Peer]
PublicKey = sMrGGTTfFxt2ScP0fiRJaJXDrgTDUIRGfS2Bw2k52LRP
PresharedKey = Acasf1nkvC5sxPRfcoYpdQzhNKpMD828jUyNsS64dwdL
Endpoint = vpn.example.com:51820
AllowedIPs = 0.0.0.0/0, ::/0
