provide "virtual socket" concept (essentially a name table) for wstunnel client to reduce loopback overhead

[evan0greenup]

Describe the feature

When there are two client computer (without public IP address) and a server (with a public IP address), one client computer connect to the server via wstunnel with forward tunnel and the other client computer connect to the server via wstunnel with reverse tunnel. The overall effect is there is tunnel from one client computer to the other client computer. It would be nice to make wstunnel smart enough, if both tunnel contain the same name of "virtual socket" in the table, wstunnel will directly move data in memory level from one tunnel to another tunnel to reduce overhead of network stack of operating system.

Describe the reason for such feature

For be above scenario, due to TCP congestion control If two tunnels are not directly bonded, the overall transfer rate is very low. and the latency will be high.

[erebe]

Hello,

Thank you for explaining the feature, sadly I don't see introducing such complexity in wstunnel for optimizing this use case.
Even if tcp on loopback introduce overhead, loopback interface is faster than on a regular network