3 ms·
> TCP-over-TCP > It lowers the throughput due to more overhead and increases the latency. On connections with packet loss or high latencies (e.x. satellite) it
by apitman 2y ago
> TCP-over-TCP
> It lowers the throughput due to more overhead and increases the latency. On connections with packet loss or high latencies (e.x. satellite) it can cause a TCP meltdown.
This actually isn't a problem with SSH tunnels unless you're using TAP/TUN, because It unpacks and forwards the TCP streams. But you can still get reduced performance with multiple channels due to head of line blocking.
- Snawoot 2y ago> But you can still get reduced performance with multiple channels due to head of line blocking. Later problem can be solved with the use of pool of separate SSH connections: https://github.com/Snawoot/rsp?tab=readme-ov-file#performance https://github.com/Snawoot/rsp?tab=readme-ov-file#performanc...
- apitman 2y agoInteresting tech. I've considered implementing something similar but for WebSockets. I'd love to see some data on how effective it is at various levels of packet loss. To guarantee complete avoidance of HoL blocking you would need 1 TCP connection per channel/stream.