Cloak
Cloak copied to clipboard
cbeuw
did cloak support tcp fast open?
error msg="trying to close a closed session"
its a ss msg or cloak?
in plug mode, how to know which msg belongs to?
I recommend to use bbr plus instead using tfo(tcp fast open) if you're using cloak plugin. I remembered cloak+tfo would have big cpu usage?
I recommend to use bbr plus instead using tfo(tcp fast open) if you're using cloak plugin. I remembered cloak+tfo would have big cpu usage?
i think there is no conflict between tfo and bbr
i have tried ss(tfo open)+cloak 3hours more with the server, cpu usage is normal
there is only one thing to worry, is about safety
many years ago, tfo traffic was very small, interfering with tfo traffic will not have a big impact
but now, more and more normal server is begin to use tfo, so, many traffic is tfo traffic, maybe tfo is safe now
between cloak and ss, tfo is absolutely secure, because traffic is only inside the server
btw, you can try bbr2
how to know which msg belongs to?
You need to learn using github first xD you mean search? i tried, but no answer here...
@malikshi
I recommend to use bbr plus instead using tfo(tcp fast open) if you're using cloak plugin. I remembered cloak+tfo would have big cpu usage?
@qwerttvv is right: there is no conflict between TFo and BBR. TFO reduce the time to make a connection between two endpoints which had a connection before by using a cookie. BBR improves the tcp transmission effeiciency by adjusting the size of tcp window accordingly. This process is after the TFO process.
Should fast open be turned off in client or server Shadowsocks if Cloak doesn't support it?
@klaaktu It shouldn't really affect anything because the communication between Shadowsocks and Cloak is entirely on loopback (assuming you have them on the same machine). It won't affect detection chance and the bandwidth should be close to memory speed whether or not you have TFO turned on
