You have to do the same. Use for the WG-interfaces a "transportation
subnet" and add your local IP as Gateway for the subnet of the other lan
side.

left: ip route add 192.168.90.0/24 via 192.168.1.3
right: ip route add 192.168.1.0/24 via 192.168.90.20


#left
[Interface]
Address = 172.16.0.1/32
ListenPort = 12345
PrivateKey = priv1

#right
[Peer]
PublicKey = pub2
AllowedIPs = 172.16.0.2/32, 192.168.90.0/24
Endpoint = 80.40.20.10:12345

-------

#right
[Interface]
Address = 172.16.0.2/32
ListenPort = 12345
PrivateKey = priv2

#left
[Peer]
PublicKey = pub1
AllowedIPs = 172.16.0.1/32, 192.168.1.0/24
Endpoint = 200.100.50.25:12345

Am Mo., 6. Mai 2019 um 22:43 Uhr schrieb Paulo Lopes <plopes1960@hotmail.com
>:

> Hi all!!!
>
> First, let me thank for the amazing vpn protocol that Wireguard is!!!!
>
> I need your advise. As you can see on the picture attach, I have 2
> raspberry pi. One as a vpn server and the other as a vpn client to connect
> 2 remote Lan.
>
> Can you point me what I need to do, if I want to replace the openvpn for
> the wireguard?
>
> I can connect 2 rpi with wireguard, but, the others ip machinies on the
> server and client side can´t see each other.
>
> With openvpn I needed to inser iroute and add a static route on both
> routers. What I need to with the wireguard?
>
> Once again many tahnks for all the help you can give me😉
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>