Re: Wireguard interface on RPI evbarm
Ramiro Aceves <[email protected]> Thu, 30 Apr 2026 16:55:42 +0200
| Newsgroups | gmane.os.netbsd.ports.arm |
|---|---|
| Message-ID | <[email protected]> |
El 30/4/26 a las 15:19, Mayuresh escribió: > On Thu, Apr 30, 2026 at 02:50:19PM +0200, Ramiro Aceves wrote: >> https://ea4nz.ampr.org/hamradio/ampr/ampr.html >> >> Perhaps you can pick some ideas, just in case... > > Thanks. I was just struggling with keepalive > Hello, > The usage message does show it: > > # wg set > Usage: wg set <interface> [listen-port <port>] [fwmark <mark>] [private-key <file path>] [peer <base64 public key> [remove] [preshared-key <file path>] [endpoint <ip>:<port>] [persistent-keepalive <interval seconds>] [allowed-ips [+|-]<ip1>/<cidr1>[,[+|-]<ip2>/<cidr2>]...] ]... > > But trying to set it draws error, e.g. > > wg set wg0 peer <pubkey> persistent-keepalive 25 > Unable to modify interface: No such file or directory > > > ping is a workaround for now, but what sort of problems to expect if I > don't set persistent-keepalive at all? > I have not used that "wg" command (I do not remember to which pkgsrc package it does belong to cause it was some time ago when I was strugling with this). I have used only the "wgconfig" command present on the NetBSD base system. NetBSD implementation does not have the Keepalive setting, I think. That is why I used some periodical pings to keep it alive. Without that and after seveeral seconds my RPiZero was not reachable from outside. Regards.