openssl VS openmptcprouter

> Client-side QUIC support

Is that enough to get rid of the QuicTLS fork? https://github.com/quictls/openssl.

I've been looking at this project for a while which may be interesting to you: https://github.com/Ysurac/openmptcprouter.

I recently bought a property where I cannot get a full fibre connection, but I can get 150-400 Mbps using 5G. I've been thinking about using dual 5G connections and tunneling my traffic via mptcp to a VPS to aggregate the connections.

https://www.openmptcprouter.com/

I mentored the port of MPTCP to OpenWRT years ago, and OpenMPTCPRouter took some of this work in their port.

Something which goes further than this, but works very well for my use case and would probably suit others in the WFH crowd: OpenMPTCProuter [1]

This handles failover between connections and also aggregates them using MultiPath TCP to maximize bandwidth & overall reliability at the expense of increased data usage and the cost of running a machine somewhere with a decent connection, even a cheap VPS.

I'm using it to aggregate ADSL, Starlink and 4G, resulting in a stable 250mbps/50mbps connection.

* [1] https://www.openmptcprouter.com/

You might want to take a look at https://www.openmptcprouter.com/.

I do the same and for the same reason, but I use https://www.openmptcprouter.com/, which is open source. It's game changing!

If you're looking for a bonded type solution similar to Speedify, I've had good success with a raspberry pi, an inexpensive 10 port gig switch, a DigitalOcean droplet and https://www.openmptcprouter.com/.

I get a VPS, preferably with Debian or Ubuntu and set it up as described here

https://www.openmptcprouter.com/ was the inspiration

Then OP could use OpenMPTCProuter to bond the connection, thus actually getting bandwidth benefits out of the multiple carriers.