Is T-Mobile Fiber (in the US) friendly to Wireguard, or am I going to have blocking issues?

T-Mobile is installing fiber throughout our neighborhood. While I’m not a huge fan of T-Mobile, I actively loath Comcast, and that (or DSL) are currently our only options. At less cost for guaranteed Gb up/down, it’s a no-brainer switch.

Except that we’re always on VPN. I’ve got a perma-connection through Mullvad on the router, and a bypass for VPN the company my wife works for uses; there’s no unencrypted anything going through the network provider. Comcast has never been an issue, but before I go through switching to T-Mobile it’d be nice to confirm that they aren’t going to try to block VPN traffic.

As in the title, it’s Wireguard; does anyone use anything else anymore? Don’t answer that; it’s rhetorical.

Can anyone in the US confirm they’re successfully using Wireguard on T-Mobile Fiber?

  • 𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍@midwest.socialOP
    1·
    3 days ago

    You can put headers on any TCP packets, and they’re supposed to be preserved by intermediate routers. It affects all TCP packets, not just HTTP; the only way to bypass it is by using UDP, which is used by some protocols, but not most.

    A TCP implementation MUST be able to receive a TCP Option in any segment (MUST-5).

    RFC9293