@anav
I will try to provide you as much information as possible.
a. which is server and which is client for the initial connection establishing the tunnels ?
R1 should be the server, as it’s the main router in our network and R2 and R3 are clients as I see it.
b. is traffic for each connection going to be two way or one way ( in other words do users, on both devices travel out over the tunnel)
Yes, traffic is going to be two way
c. if traffic is to subnets, or to internet
I presume to subnets, as i only need to access device on remote network and the router itself.
Finally last step is access router for config purposes
So only R1 should be able to admin R2 and R3
If I forgot something just say.
@Sob
Okey, I added /24 subnet because that is in the tutorial, so if i understand you right, for tunnels i shouldn’t use /24 subnet, as right way is to change subnet to /32, so R1 should be 10.255.255.1/32, R2 should be 10.255.255.2/32 and R3 should be 10.255.255.3/32 so WG interface on R1 can only comunicate with WG interface on R2 and R3 like they are directly connected by cable and have static IP ?
I don’t need R2 to communicate with R3 as all the data is comming back to R1 and any configuration is sent via R1 to R2 or R3
And about “this is the one that don’t want to connect if there is nothing connected to it”, WG is by default silent, it only connects when there are some data to be sent. If you want it to be more active, setting keepalive for peer should do the trick.
I didn’t know that, maybe that is the problem all the time, because, if I setup ping on 192.168.1.1 and start pinging 192.168.25.1 it says timeout, until i connect laptop for example, then it took about 3 seconds or less to start seeing response to pings.