Subj : Automatically blocking co
To   : DIGITAL MAN
From : Dumas Walker
Date : Thu Jun 06 2024 09:23 am

>  > > I have not observed this problem (Telnet server not responding while SSH
>  > > does)
>  > > nor heard any reports of it, besides yours. I would expect the use of
>  > > tools like netstat to help identify the real cause of that issue.

>  > If I can restart synchronet and it goes away, I think that tells me
>  > something.

> It tells me that the TCP port was rebound. If the socket is configured for
> address/port reuse (in ctrl/sockopts.ini), then one could artifically create
> this exact scenario by starting and stopping a second process (after sbbs) tha
> bound to TCP port 23. It could even be a second instance of sbbs. No "crashing
> of the Synchronet telnet server would be required.

Hmmmm... which setting would I want to set if I wanted to tell synchronet
not to allow the port to be reused by another process?

Currently, the only two options I have set in sockopts.ini are:

KEEPALIVE = TRUE
TCP_NODELAY = TRUE

I also see that IPV6_V6ONLY = 1 .  What does that one do?

I suspect that these are all defaults as I don't remember changing anything
in this ini file, and the modify date is 8/20/2015.

Thanks!


 * SLMR 2.1a * If you stomp gripes, do you get whine?
---
 þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

.