WireGuard Is Two Things
mlhpdx
17 points
3 comments
March 12, 2026
Related Discussions
Found 5 related stories in 436.6ms across 14,015 title embeddings via pgvector HNSW
- WireGuard for Windows Reaches v1.0 zx2c4 · 16 pts · April 21, 2026 · 74% similar
- WireGuard makes new Windows release following Microsoft signing resolution zx2c4 · 439 pts · April 10, 2026 · 65% similar
- WolfGuard: WireGuard with FIPS 140-3 cryptography 789c789c789c · 84 pts · March 24, 2026 · 61% similar
- Version 1.0 Released: WireGuard for Windows and WireGuardNT zx2c4 · 19 pts · April 18, 2026 · 59% similar
- Deep dive into iroh: Replacement for WireGuard or P2P layer for your application cold_pizz4 · 16 pts · June 24, 2026 · 55% similar
Discussion Highlights (2 comments)
tptacek
This is almost true, but not quite. WireGuard is a protocol, but it's also the Linux kernel implementation of that protocol; there are design decisions in the protocol that specifically support software security goals of the kernel implementation. For instance, it's designed to be possible to implement WireGuard without demand dynamic allocation.
viceconsole
The post mentions the deficiencies of TCP for mobile devices over unreliable links, but I've had nothing but trouble with Wireguard when connecting from phones via mobile data. I suspect it's due to my mobile operator doing traffic shaping / QoS that deprioritizes UDP VPN. In contrast, connecting to OpenVPN over TCP was a huge improvement. Not at all what I expected.