I have 2 locations with site-to-site connection between and public ip on both places.
I can ping devices on site B from site A and and backwards when I’m on the locations locally. (Have made routes to wireguard gateway adress)
My question is…
How can I make it possible to ping devices on site B from wireguard client connected to site A? I have made test by making a route from wireguard client address to wireguard site-2-site interface and when I look into firewall connection data I can see on site B that the ping come in, but in the computer with the client that is connected to site A I get Timeout request…
I asked you a question and you didnt answer it, also you ignored my warning about having two peers on the router with 0.0.0.0/0 for allowed Ips.
Plus you fail to have keep alive at either end.,
warning about two peers you didn’t mention ?
But my config I send was in test mode, just to have it working. from the start I didn’t have 0.0.0.0/0, it was just for testing to have all traffic going there. but that is fixed now, and I have set keep alive on the site B, but that won’t fix the problem
How can I route my traffic from Client WG(separated wg interface) on SITE A to SITE B, so when I connect my computer(client wg) to Site A I will have open line to the LAN on site B…
Is it better to have the client connecting to same wg interface as the site-to-site?
True dat, got mixed up with another thread…
Yes, there is no need for different interfaces. All the peers connecting to the same server can and normally all are on the same subnet
at the server device
peer1 10.10.10.2/32
peer2 10.10.10.3/32
etc…
At the peer devicesm their settings typically
peer server: 10.10.10.0/24
If the wireguard is setup properly, including allowed IPs to or from remote IP subnets, then the showstopper typically are
a. routes to remote subnets via wireguard interface
b. firewall routes allowing traffic from to wireguard with src and dst addresses