Post B6w06bDZKzXou4s9gW by wolf480pl@mstdn.io
 (DIR) More posts by wolf480pl@mstdn.io
 (DIR) Post #B6w06b0o6RKuGUtxnE by algernon@come-from.mad-scientist.club
       0 likes, 0 repeats
       
       Hnghgh. Friendship with WireGuard is ending. When it works - and it usually does - it's great. But debugging wtf is wrong when it does not, is proving to be a pain in the ass.
       
 (DIR) Post #B6w06bDZKzXou4s9gW by wolf480pl@mstdn.io
       0 likes, 0 repeats
       
       @algernon sooo what is it gonna be instead? OpenVPN?
       
 (DIR) Post #B6w08YTMW14cy6BybI by wolf480pl@mstdn.io
       0 likes, 0 repeats
       
       @algernon (I know a lot of alternatives that I'm not suggesting because they're harder to debug)
       
 (DIR) Post #B6w0HLJGp7pYkcf72G by algernon@come-from.mad-scientist.club
       0 likes, 0 repeats
       
       The current situation is that I upgraded a server to NixOS 26.05. My desktop connects fine to it. Other people have... problems. Like, handshake failing.On my end, the only log is No valid endpoint has been configured or discovered for peer 3.The other observed problem is that my server's end of WG appears to be not pingable (I can ping it, though).So, uhh... quick question: is oscar.onlyjunk.fans pingable for anyone?
       
 (DIR) Post #B6w0HLmL535CCmGKLQ by wolf480pl@mstdn.io
       0 likes, 0 repeats
       
       @algernon pingable over IPv4not pingable over IPv6, trace ending somewhere in your-cloud.host
       
 (DIR) Post #B6w0xq5ul1omOFg9Y0 by algernon@come-from.mad-scientist.club
       0 likes, 0 repeats
       
       @wolf480pl Thanks!
       
 (DIR) Post #B6w0xqjyM5rQOUQ8zA by wolf480pl@mstdn.io
       0 likes, 0 repeats
       
       @algernon also, in case you don't know yet: there's `wg show` command which can show you the in-kernel state of the wireguard interfaces
       
 (DIR) Post #B6w3TxoDoHLtUXqhtI by algernon@come-from.mad-scientist.club
       0 likes, 0 repeats
       
       Friendship with WireGuard restored to some extent, because it turns out it was an IPv6 problem. Would've been nice if the client side error was something like: "I CAN'T TALK TO THE FUCKING ENDPOINT! WHAT DO YOU WANT ME TO DO?!?!?" instead of "handshake error" or something.But fine, now I know, checking IPv6 is now part of the debugging playbook!
       
 (DIR) Post #B6w3Ty2kwEyiDceJXs by algernon@come-from.mad-scientist.club
       0 likes, 0 repeats
       
       It would also be nice if I had IPv6 at home. But alas, the routers in the house allegedly do not support IPv6.I was told - with a straight face! - that's the reason. Not kidding.
       
 (DIR) Post #B6w3TyEoDQcSp0HwKe by wolf480pl@mstdn.io
       0 likes, 0 repeats
       
       @algernon is one of those routers an ISP-issued one that you cannot replace with your own?