Open bullr opened 7 months ago
This is the same behavior I have on EQA server. I just don't have a ready need for Telnet so haven't dumped the time into looking into this yet. Ideally we could figure out a way to move to a more secure protocol anyway. I am also on Debian 12.
Thanks for the reply. A general API for python would be nice rather than a service like telnet for outside scripting and automation.
I cannot get the telnet server to start up and listen on TCP 9000 when enabling it in the eqemu_config.json file. Here is my current telnet configuration:
"telnet": { "enabled": "true", "ip": "127.0.0.1", "port": "9000" }
I would expect when the server is launched that this would start the telnet server listening on TCP port 9000 over the local loopback interface so I can interact with it using scripts running locally on the server.
My current build was compiled using sources from 3/14/2024. Netstat only yields port 9000 UDP when queried.
netstat -an | grep 9000
udp 0 0 0.0.0.0:9000 0.0.0.0:*
Either the config change is not doing anything, or there is something wrong in the telnet server startup in the source. Port 9000 TCP is not being used by any other service on this system. The system is exclusive to the TAKP server software and database only.
OS is a clean minimal install of Debian 12 Linux.