¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: telnet times out


 

¿ªÔÆÌåÓý

There are two timeout, the Node IDLETIME (normally 15 minutes) and the Chat Idle Timeout (2 Hours without user input).

Chat has an option (/keepalive) that will make it send a message to the user if there is no other traffic for 10 minutes, which keeps IDLETIME from expiring, but doesn't reset the Chat Idle timer.

All my terminal programs have an option (Chat Terminal Mode) that sends a single null character every 9 minutes or so which resets both the Node and Chat timers but is otherwise ignored so allows users to stay connected indefinitely.

73
John

On 24/02/2021 16:06, Tadd KA2DEW in NC via groups.io wrote:

One of my locals (kn4orb) is writing a Raspberry PI Python program which interfaces with CHAT. ?He's telnetting from a Python app on the Raspberry PI to pilinbpq on the same PI to address 127.0.1.1 and port 8011. ?He gets to the node and then connects to CHAT. ?After that the Python program does commands periodically in an attempt to keep the connection from timing out. ?The telnet session receives and sends from/to chat. ? The dialogs seem to work but it still seems to disconnect after 2 hours, reliably. ?There was an exchange moments before the disconnect this time. ?is there anything specific we need to do to keep telnet from timing out??

He gets this on the python side "raise EOFError, 'telnet connection closed' EOFError: telnet connection closed¡±

BTW, we have another Python app connecting through the TNC2 API to CHAT and with similar command exchanges it stays up for months at a time.?

Most recently we tried to send /s callsign ?messages to another local log-in to CHAT in order to keep CHAT from timing out. ? Maybe it isn¡¯t CHAT which is timing out? ?Is there a Telnet Port parameter which sets a timeout and has a 2 hour default?

?Thanks
? ? Tadd - KA2DEW


Tadd Torborg?





Join [email protected] to automatically receive all group messages.