Persistent Keep Alive

[verbal666]

Hi again 😉
I saw WStunnel client sends an "alive ping" every 60 seconds.
Is there a way to setup a major timing? My proxy logs too many entries to wst server 🥲
Do you think it's possible, client side, to add a PersistentKeepAlive feature?

I setup, server side, a --websocket-ping-frequency-sec 300 , but client keeps on ping every 60 seconds 🤷‍♀️

Thanks again 🙏🙏🙏

[erebe]

Hello,

Yes ping/pong is independant, at the initiative of either the client or the server. But this is not proper to wstunnel, it is in the websocket spec. So each of the client or the server is free to send ping at will and the other peer have to respond.

Regarding your proposition, i am not really sure to understand what would be this PersistantKeepAlive ?

[verbal666]

But this is not proper to wstunnel, it is in the websocket spec.

Here we go. So it's not wstunnel managing the ping/pong feature 🥲it's a specific of protocol... i'll try to find if i can raise the timings, kernel side 👍

Regarding your proposition, i am not really sure to understand what would be this PersistantKeepAlive ?

Was relating to the ping/pong feature (i thought, but as you explained it's not a software feature). My intention was (as in an OpenVPN tunnel) to keep a single persistent tunnel connection (i don't bother about throughput) and log less possible inside the HTTP PROXY. Opening an OpenVPN tunnel through PROXY let the proxy log ONLY 1 CONNECT to remote host, using TCP KEEPALIVE with long time. I thought it was possible also with wstunnel/websocket 🤷‍♀️🤷‍♀️🤷‍♀️

Many thanks erebe 👍👍👍
wstunnel is a great tool, many congratulations, and thanks for sharing 💪💪💪👏👏👏🤩

[verbal666]

Anyway, solved the problem in a easy way,

• open a wstunnel client session with local socks5 listening
• now, i do not interrogate wstunnel socks5 directly, but chain another socks5 proxy in front, so the tunnel remains the original one

ws server <-1-> http proxy <--1--> ws client <-1-> socks5 <-1.1-> socks5 proxy chained

Now if i call directly socks5 #1 ws send a new ws request and proxy logs the new channel request.
If i call socks5 #1.1 ws uses the original #1 tunnel channel and the only log i can see is the original #1 👍