3 ms·
Not directly related to the article, but I've been doing a lot of interesting stuff with WireGuard for the past few years. I've observed some odd behavior by s
by anonymousisme 5y ago
Not directly related to the article, but I've been doing a lot of interesting stuff with WireGuard for the past few years. I've observed some odd behavior by some mobile service providers. Right now I have two permanently deployed WireGuard VPNs using terrestrial wireless carriers. One VPN uses AT&T Wireless while the other uses T-Mobile. That AT&T VPN worked fine out the box. The T-Mobile VPN required some odd tweaks to MTU/MRU in order to get it working. I found that the MTU on the mobile end needed to be 1220 or less, and the MTU on the remote end needed to be 1380 or less. This took a while to debug.
- mcspiff 5y agoI wonder if you’re bumping into issues with t-mobile’s 646XLAT (https://sites.google.com/site/tmoipv6/464xlat https://sites.google.com/site/tmoipv6/464xlat )?
- binarybanana 5y agoThat would suck for anything IPv6 (minimum MTU is 1280, as opposed to 576 or something around that).