Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • See if this article helps: ............ learn.beako.net/books/wireguard/page/persistentkeepalive
    – anon
    Commented Feb 5 at 20:26
  • 1
    note: If both have public IP addresses, then PersistentKeepalive has no useful role and shouldn't even be needed anywhere. There's probably an other problem.
    – A.B
    Commented Feb 5 at 22:40
  • @A.B tried adding and removing PersistentKeepalive the thing is if I remove it , it stops working after few minutes, but when added lasts for hours, what else can cause this ? Commented Feb 6 at 4:57
  • NAT or firewall despite what you wrote. Perhaps not directly on your systems. Or Docker running on one of the systems. etc.
    – A.B
    Commented Feb 6 at 7:01
  • 1
    For each system can you provide their network configuration while VPN works? Something like ip link; ip -br addr; ip route; ip rule + nft list ruleset (as root) + the output of wg (as root). You can replace public IP addresses with 1 or 2 blocks from RFC 5737: rfc-editor.org/rfc/rfc5737.html#section-3 . Then when it fails some minutes or hours later again the very same commands.
    – A.B
    Commented Feb 6 at 7:03