All traffic is secured with wireguard to my home router, and then goes through my ISP. The wireguard tunnel is wrapped in an error correcting tunnel; it makes a huge difference on the usability a lot of public APs.
[1]: https://du.nkel.dev/blog/2021-11-19_pfsense_opnsense_ipsec_c...
What is your error correcting tunnel? Given that Wireguard is UDP and that any tunneled TCP that gets dropped should just be handled by TCP, why encapsulate Wireguard in something else? I certainly find Wireguard itself improves many Public Wifi networks, I've never thought to encapsulate it further.
That's the thing, TCP doesn't really handle lossy connections well. A moderate lossy link might do udp traffic like video fine, but be practically unusable for TCP traffic.
Pretty sure I used the suggested config and it's been working flawlessly in the background.
Or something like that. With wireguard, it's just a matter of pointing the config at the local socket for the fec tunnel (or any other type of tunnel, there was a dicussion about making it look like TCP http traffic the other day), so it's pretty much plug and play.