On Mon, 26 Jan 2026 12:30:08 +0100
Ramiro Aceves <[email protected]> wrote:
> Sorry, after adding that route pinging from outside does not work either.
I'm not sure what you mean by outside. I currently use wireguard on a
LAN. The way I have it set up - I have a server and a client. I can
initiate a connection from client to server any time, but not the other
way round if wgconfig on the server shows latest-handshake as never
for this peer:
wgconfig wg0
interface: wg0
private-key: (hidden)
listen-port: 51820
peer: test
public-key: XXX
endpoint: (none)
preshared-key: (hidden)
allowed-ips: 10.1.5.50/32
latest-handshake: (never)
Once I establish a connection from the client and keepalive is running,
I can then ping this client from the server:
# ping 10.1.5.50
PING 10.1.5.50 (10.1.5.50): 56 data bytes
64 bytes from 10.1.5.50: icmp_seq=0 ttl=255 time=0.640570 ms
64 bytes from 10.1.5.50: icmp_seq=1 ttl=255 time=0.647329 ms
64 bytes from 10.1.5.50: icmp_seq=2 ttl=255 time=0.626626 ms
I think you can configure wireguard server so it acts as a server and
client at the same time by specifying option "--endpoint=" in the "add
peer" command, but I've not tried it yet.
