-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timeout Flag for TCP Connections #22
Comments
Well, I didn’t plan to, but that’s only because no one ever asked! Could you explain why this would be necessary? I was under the impression that the client and the server were already capable of handling timeouts and connexion keepalives. |
The idea is that rinetd redirects the tcp packets to certain socks5 proxy
servers , which may be down, thus i need to know from the connecting
machine that.
…On Mon, Mar 1, 2021, 18:07 Sam Hocevar ***@***.***> wrote:
Well, I didn’t plan to, but that’s only because no one ever asked!
Could you explain why this would be necessary? I was under the impression
that the client and the server were already capable of handling timeouts
and connexion keepalives.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#22 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJUM7N2F5L7ZNLMF322OIUTTBO3VLANCNFSM4YMHLNFQ>
.
|
I've got impression that there is some fundamental issue with how rinetd is handling TCP connections. |
Do you plan implementing this feature as well ?
The text was updated successfully, but these errors were encountered: