connection issues / quits without reason with ip232+VICE #25
Description
I have seen various strange issues in my tests... i will add more logs when i stumble about them again.
i always start tcpser like this:
./tcpser -r -p 6400 -S 300 -v 25232 -l 4 -tmM -i"s5=20 s0=1 s39=1"
Then i start VICE like this:
x64sc -default -rsdev3ip232 -rsdev3baud "300" -rsuserbaud "300" -rsuserdev "2" -userportdevice "2"
now tcpser produces a log like this
2023-06-25 21:19:34:139691083523904:INFO:Server socket bound to port
2023-06-25 21:19:34:139691083523904:INFO:Server socket listening for connections
2023-06-25 21:19:34:139691083523904:INFO:Creating modem #0
2023-06-25 21:19:34:139691083519680:INFO:Opening ip232 device
2023-06-25 21:19:34:139691083519680:INFO:Server socket bound to port
2023-06-25 21:19:34:139691083519680:INFO:Server socket listening for connections
2023-06-25 21:19:34:139691083519680:INFO:ip232 device configured
2023-06-25 21:19:34:139691083519680:INFO:Control Lines: DSR:1 DCD:0 CTS:1 RI:0
2023-06-25 21:19:38:139691075126976:INFO:Connection accepted from 127.0.0.1
2023-06-25 21:19:38:139690992727744:INFO:Link has come up
2023-06-25 21:19:38:139691083519680:TRACE:RS<-|0000|ff |. |
2023-06-25 21:19:38:139691083519680:TRACE:RS<-|0000|01 |. |
2023-06-25 21:19:38:139691083519680:TRACE:RS<-|0000|ff |. |
2023-06-25 21:19:38:139691083519680:TRACE:RS<-|0000|00 |. |
2023-06-25 21:19:38:139691083519680:INFO:No ip232 socket data read, assume closed peer
2023-06-25 21:19:38:139691075126976:INFO:Connection accepted from 127.0.0.1
the funky part is, when i connect to tcpser using
telnet 127.0.0.1 6400
it will show
2023-06-25 21:20:52:139691083519680:INFO:Control Lines: DSR:1 DCD:0 CTS:1 RI:1
2023-06-25 21:20:52:139691083519680:TRACE:RS->|0000|0d 0a |.. |
and then tcpser terminates, with no error message whatsoever .... how can this happen? As i understand it, there is no way tcpser can - or even should - do this. But it does :)