Open w3rkzeug opened 3 years ago
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 notifications@github.com 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 https://github.com/samhocevar/rinetd/issues/22#issuecomment-788068584, 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. I'm using GPS tracker for my car and it's sending packets via rinetd to my Traccar server. I don't know. It looks like rinetd doesn't close connections. Every few weeks I need to restart it or it runs out of filedescriptors.
Do you plan implementing this feature as well ?