Mullvad VPN Introducing WireGuard over TCP and IPv6 (opens in new tab)

We understand why it exists. Although it would be nice if the issue was up front so people can be aware of the problem.

If they have an innovation that solved the TCP meltdown issue that would be interesting.

Exactly that. They are including an encapsulation option on their client package and running something on the server side to listen/decode the TCP and shove it back into udp. I have run a wireguard server behind udptunnel for the same reasons in the past and it looks like they are simply setting their own internal standard.

For the most part, if I am providing wifi in a place like that the only thing I want you to do is browse the web. I am not interested in your desire to run a torrent client, stream netflix, or do something else that consumes a significant amount of bandwidth. Most UDP applications are also rather poor when it comes to congestion control and in general do not play nice with the other children. These companies have better things to do than to provide IT support for people trying to use the wifi, so you block all UDP and force re-direct port 53 UDP (DNS lookups) to go to a resolver that you are going to provide in the DHCP lease. This also means that wireguard is not an option for most people if they are on these networks.

For those that aren't loading such domains these days: brief (even incomplete) list of points appreciated.