3 ms·
Socat is terrible. When used to establish a persistent connection to a remote listening (TCP) port, it has NO WAY to detect that the remote end has dropped the
by axiolite 6y ago
Socat is terrible.
When used to establish a persistent connection to a remote listening (TCP) port, it has NO WAY to detect that the remote end has dropped the connect, and automatically reconnect. It just does not work.
Yes, I know all about all the keep-alive and retry options in the manual. Try it yourself.
It's one of those horrible tools that you can get up and running quickly, but can never make work reliably.
- bandie91 6y agoi doubt that socat did not handle TCP RST. is not it the network environtment which eats TCP RST in some cases (like AWS NLB).
- axiolite 6y agoThat's why I said try it yourself... It's no good for serious use. Here's the first search result: https://stackoverflow.com/questions/9341254/reconnect-socat-connection-after-network-failure https://stackoverflow.com/questions/9341254/reconnect-socat-...
- sundbry 6y agoI don't think you understand how TCP works. A TCP connection can stay alive through an unplugged Ethernet cable if it hasn't sent any packets.
- axiolite 6y agoI've worked as a senior network admin for some very large organizations. Safe to say I understand TCP.