Add Brutal congestion control for wstunnel

[evan0greenup]

Describe the feature

Just bring the Ideas from hysteria2 https://github.com/apernet/hysteria or tcp_brutal https://github.com/apernet/tcp-brutal . Use add option to use a brutal congestion control algorithm when the transmission rate of the network path between two end of wstunnel is constant and known.

Describe the reason for such feature

For a network path with known transmission rate, the default congestion control my not be optimal, because when there is packet loss or congestion, the speed will drop severally (usually half). For the scenario for wstunnel, The virtual tunnel is usually established between two fixed node (so the transmission rate between two nodes are also fixed),

Describe alternatives you've considered

Because websocket is based on TCP protocol, the tcp-brutal may be very helpful, or can be directly used in wstunnel.

[erebe]

Hello,

I will try to take a look, but would you mind describing in which scenario are you using wstunnel ?
This kind of congestion control is only relevant when you own the network, or when you don't want to be a good cityzen of the network

[evan0greenup]

wstunnel has two end, let us naming it with endA and endB. when there is many router or network switch between these two end, even if the overall bandwidth is high, but there is too many factors which can affect the successful delivery of datagrams. As a result, the websocket connection will keep halfing its transfer rate. Those datagrams loss is not due to the lack of capacity of network, instead, it is due to random event occurs on the network. If the connection just simply ignore those event and keep going in the same rate, the bandwidth can be ensured without sacrificing other users experience.

[bytejedi]

Concept NACK. We should keep simple as we can.