securesocketfunneling
commented
7 years ago Hi again,
It is possible that the current version is suffering of latency. The issue could be the stack of two cryptographic layers:
- one between the client and its the first server in the relay chain
- the second between the client and its final destination
If the relay chain is empty (direct connection), the second layer is still present. On the 1.*, the second layer did not exist and we did not observe latency on our tests. There is definitely something to do here. This is a network framework issue. We can stack different layer types (e.g. TLS > CIRCUIT > TLS > TCP) but there is currently no way to disable a layer on particular condition at runtime.
We will do some tests with executables which does not add this second layer to be sure that it's the origin of the problem.
Thanks for your feedback. It's really appreciated :-)
Hello SSF Devs, At first many thanks for your good work, it's so a great tool.
My issue is that if I use ssf (ssfc + ssfs in socks mode, or tcp forward to a local socks on server ) the latency is very high (normal latency= 40-50ms) but with ssf I have 200ms or 300 ms, also tried to set the process to realtime, no effect.
If I use another similar program called "stunnel" for the same use case I have normal pings like 40-50ms. tested with beta.speedtest.net.
Can anyone confirm that ssf have a high latency? or dit I something wrong? can't belive that.
EDIT: My server is a Windows Server 2016 and Clients are Win7 and Win10
Best Regards