openmptcprouter
quinn
Our great sponsors
openmptcprouter | quinn | |
---|---|---|
129 | 23 | |
1,637 | 3,449 | |
- | 2.7% | |
9.1 | 9.0 | |
7 days ago | 1 day ago | |
C | Rust | |
GNU General Public License v3.0 only | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
openmptcprouter
- Multipath TCP for Linux
- OpenMPTCProuter v0.60: an open source solution to aggregate connections
-
802.11ah Wi-Fi HaLOW: The 1 Kilometer WiFi Standard
https://www.openmptcprouter.com/
I mentored the port of MPTCP to OpenWRT years ago, and OpenMPTCPRouter took some of this work in their port.
-
Ask HN: A network device that doesn't exist?
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.
-
Starlink as an emergency solution
You might want to take a look at https://www.openmptcprouter.com/.
-
Satellite handover latency
I do the same and for the same reason, but I use https://www.openmptcprouter.com/, which is open source. It's game changing!
-
ISO best failover option for SL and T-Mobile 5G
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/.
-
Seamless failover solution using channel bonding and Wireguard, is it possible?
I get a VPS, preferably with Debian or Ubuntu and set it up as described here
-
AMA with startyourownisp.com creators: 50+ years in the (W)ISP industry. Ask us anything!
https://www.openmptcprouter.com/ was the inspiration
-
Suggestions for Load Balancing
Then OP could use OpenMPTCProuter to bond the connection, thus actually getting bandwidth benefits out of the multiple carriers.
quinn
-
Why HTTP/3 is eating the world
Since it lives on top of UDP, I believe all you need is SOCK_DGRAM, right? The rest of QUIC can be in a userspace library ergonomically designed for your programming language e.g. https://github.com/quinn-rs/quinn - and can interoperate with others who have made different choices.
Alternately, if you need even higher performance, DPDK gives the abstractions you'd need; see e.g. https://dl.acm.org/doi/abs/10.1145/3565477.3569154 on performance characteristics.
-
Async rust – are we doing it all wrong?
> Making things thread safe for runtime-agnostic utilities like WebSocket is yet another price we pay for making everything multi-threaded by default. The standard way of doing what I'm doing in my code above would be to spawn one of the loops on a separate background task, which could land on a separate thread, meaning we must do all that synchronization to manage reading and writing to a socket from different threads for no good reason.
Why so? Libraries like quinn[1] define "no IO" crate to define runtime-agnostic protocol implementation. In this way we won't suffer by forcing ourselves using synchronization primitives.
Also, IMO it's relatively easy to use Send-bounded future in non-Send(i.o.w. single-threaded) runtime environment, but it's almost impossible to do opposite. Ecosystem users can freely use single threaded async runtime, but ecosystem providers should not. If you want every users to only use single threaded runtime, it's a major loss for the Rust ecosystem.
Typechecked Send/Sync bounds are one of the holy grails that Rust provides. Albeit it's overkill to use multithreaded async runtimes for most users, we should not abandon them because it opens an opportunity for high-end users who might seek Rust for their high-performance backends.
-
quicssh-rs Rust implementation SSH over Quic proxy tool
quicssh-rs is quicssh rust implementation. It is based on quinn and tokio
-
The birth of a package manager [written in Rust :)]
Regarding Quinn, I had a blast this week resurrecting an old PR. Looking forward to the next!
- Best performing quic implementation?
-
str0m a sans I/O WebRTC library
By studying u/djcu/hachyderm.io (and others!) excellent work in Quinn, doing a sans I/O implementation of QUIC https://github.com/quinn-rs/quinn we have a way forward.
-
durian - a high-level general purpose client/server networking library
QUIC isn't web/wasm-compatible because of https://github.com/quinn-rs/quinn/issues/1388, so durian wouldn't either since it's built on top of it.
-
FPS server with QUINN?
Quinn, as in the implementation of QUIC? https://github.com/quinn-rs/quinn
-
I built a Zoom clone 100% IN RUST
You are right, I am planning to switch the transport to UDP + quic using the awesome QUINN library, https://github.com/quinn-rs/quinn .
-
I write a secure UDP tunnel
Hi, I am new to the community, I just started learning rust and created a secure UDP tunnel based on the Quinn library, thanks to Quinn, I didn't need to go into the detail of the QUIC protocol and quickly created a UDP tunnel, and thanks to the BBR congestion control algorithm it uses, the tunnel performs quite well with lousy and long fat network, I didn't do any benchmark, but it performs a lot better (higher throughput with LFN) than most of other TCP tunnel implementations I used before.
What are some alternatives?
MLVPN - Multi-link VPN (ADSL/SDSL/xDSL/Network aggregation / bonding)
quiche - 🥧 Savoury implementation of the QUIC transport protocol and HTTP/3
shadowsocks-rust - A Rust port of shadowsocks
s2n-quic - An implementation of the IETF QUIC protocol
glorytun - Multipath UDP tunnel
h3
overthebox - OverTheBox - Aggregate and encrypt your multiple internet connections.
msquic - Cross-platform, C implementation of the IETF QUIC protocol, exposed to C, C++, C# and Rust.
SmoothWAN - An OpenWrt flavor for internet bonding and seamless failover using Speedify with few extras.
laminar - A simple semi-reliable UDP protocol for multiplayer games
sctp - A Go implementation of SCTP
neqo - Neqo, an implementation of QUIC in Rust