Conversation

Notices

1. Embed this notice
   feld (feld@friedcheese.us)'s status on Saturday, 14-Jun-2025 05:46:42 JST feld
   Apparently people have known that the Wireguard PersistentKeepalive is broken shit for years and there isn't a good solution for it other than rolling your own watchdog solution
   
   Just ran into this myself. Watched tcpdump for minutes, it never even tries to send a single packet.
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Saturday, 14-Jun-2025 05:47:49 JST feld

     in reply to
     > latest handshake: 27 minutes, 18 seconds ago
     
     so stupid, this software is overrated
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Saturday, 14-Jun-2025 06:04:02 JST feld

     in reply to

     • dsp
     @dsp my clients are behind NAT, but the server they're connecting to is not. So really there should be no problem at all...
   • Embed this notice
     dsp (dsp@social.sdf.org)'s status on Saturday, 14-Jun-2025 06:04:03 JST dsp

     in reply to

     @feld lol, i too have this problem. somewhere down i believe that if i read the manual page in some different light, some understanding might dawn on me (NATed peer should matter?) but i have yet to make sense of it.

     wgpka interval
     Set the interval of persistent keepalive packets in seconds. The default, zero, disables these. They can be used to maintain connectivity to a peer otherwise blocked to unsolicited traffic by an intermediate firewall or NAT device.