Timeline for socat - multiple connection attempts fail to pass through serial
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 29, 2020 at 10:27 | comment | added | matlo | Since the next GIMX version will change the baudrate dynamically, I am planning to add a "proxy" mode to make this use-case easier. | |
| Jan 17, 2020 at 14:31 | comment | added | DragRedSim | I feel I may have found a switch that I was looking for - "end-close", when applied to the TCP connection, will only close the handle in the fork when the connection terminates, while leaving it open for further traffic. I can't confirm this, however, see my edit on the original question. | |
| Jan 14, 2020 at 13:32 | comment | added | matlo | This is definitely a connection issue since second connection fails. The way the first connection is closed on client/com2tcp side probably leaves the socket on server/socat side in a stale state, and the first connection is probably still pending/closing. This is a bare guess, you can easily diagnose the problem using wireshark. | |
| Jan 13, 2020 at 16:06 | comment | added | DragRedSim | Yes, UDP would be a better design option due to its non-handshaking nature. The issue here is not with the connection - it works. Once. Then when I close it from the remote PC, I can’t fire it up again. As you may have guessed, I’m working on the COM port tunnelling as a way around getting FFB translation over the network. Having looked at the source, I see there’s no easy way to add it in, and it would be a much greater load over WAN transmissions, hence why I didn’t request it being added. (For those who don’t know, matlo is the creator of the GIMX software mentioned in the OP.) | |
| Jan 13, 2020 at 12:50 | review | First posts | |||
| Jan 13, 2020 at 12:55 | |||||
| Jan 13, 2020 at 12:47 | history | answered | matlo | CC BY-SA 4.0 |