El 20/1/26 a las 18:38, Martin Husemann escribió:
On Tue, Jan 20, 2026 at 06:25:42PM +0100, Ramiro Aceves wrote:
And then it works again from the local network. This may be related to the
absence of the PersistentKeepalive = 20 parameter that comes in the
configuration file sent by email from the tunnel provider and that does not
exist in NetBSD implementation of WireGuard.
It has a default keep alive of 10s, you can adjust it with
sysctl net.wg.keepalive_timeout
If you want to find out what goes wrong you should enable
sysctl net.wg.debug and see if it logs something interesting.
Martin
Thanks Martin,
Oh yes, that is the default, 10 seconds, but this way the connection
drops, I do not know why if they recommend a keepalive of 20 seconds, it
shoud be enough. It seems to always resurrect with ping to 44.x.y.z from
the raspberry pi.
netbsd-raspaZeroW# sysctl net.wg.keepalive_timeout
net.wg.keepalive_timeout = 10
The "big" problem now is that I cannot ping the 44 IP from the outside.
Regards.
Ramiro.
