Behaviour on TCP disconnect
#1
Hi,

received my two 232+OLEDs today, thanks!
Attempting to use it for inbound telnet to the old "Simplex BBS" software, I'm getting pretty far, but when nc'ing (netcat - so not telnet) to the BBS and then ctrl-C-ing netcat - which closes the connection and presumably sends TCP RST and all that - I see the BBS receiving a "NO CARRIER" string from the modem, and then the software goes into a loop where it says carrier was dropped, and then attempts to reset the modem - which again brings it to the "carrier was dropped" message, ad infinitum.

If I allow the BBS software itself to do the disconnect (timeout or whatnot), it manages just fine.

The OLED reads "Ready" when this happens.

I've tried all variants of AT&Dx, but haven't played much with other settings.

I find it hard to debug what's going on here, so I'm humbly(?) asking for some ideas of what to look for, and how. It could be a hardware (serial ports?), driver (OS/2 1.3 + Digi ClassicBoard serial card driver), software (Simplex for OS/2) or config problem.. I just don't know where to look.

Thanks again,
/Eirik
http://floppy.museum/
Reply


Messages In This Thread
Behaviour on TCP disconnect - by ltning - 02-26-2023, 01:47 PM
RE: Behaviour on TCP disconnect - by admin - 02-27-2023, 11:17 AM
RE: Behaviour on TCP disconnect - by ltning - 03-03-2023, 05:38 AM
RE: Behaviour on TCP disconnect - by admin - 03-04-2023, 02:21 PM
RE: Behaviour on TCP disconnect - by ltning - 05-10-2023, 02:36 PM
RE: Behaviour on TCP disconnect - by admin - 05-10-2023, 10:57 PM
RE: Behaviour on TCP disconnect - by ltning - 05-10-2023, 04:52 PM
RE: Behaviour on TCP disconnect - by ltning - 05-12-2023, 04:52 AM
RE: Behaviour on TCP disconnect - by admin - 05-12-2023, 08:40 AM



Users browsing this thread: 2 Guest(s)