It may help if you explain a bit more about “testing purposes”; in my
experience most people only want it for port tests, long ago made better
and faster and more-reliable with netcat or nmap, so I"ll cover netcat.
xinetd is not what you want if you want a client; that’s a server.
Telnet is installed by default as part of the “Enhanced Base” pattern.
It is a normal client application, not a service. It is run by typing “telnet” at a shell prompt or in a script. Other options are explained in “man telnet”. I do not understand what you were trying to achieve with the bizarre systemctl commands.
If you have deleted or somehow failed to install telnet then:
It’s coming from a suse forum about a similarly question ( from my point of view). I think now it was relative to telnet server ( and not telnet client ).
After deleting telnet and reinstall it I can use it.
The rest is the same, since that is just stuff you are typing as part of
the application layer (layer seven (7)) which is SMTP in this case and all
happening within the TCP (layer four (4)) connection. You may use ‘nc’
instead of ‘netcat’ depending on the version you have installed.
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
The telnet client is still very useful at times(you can probe any network service behind any port), but the server was deprecated many, many years ago due to its lack of built in security (everyone should use ssh instead if you want to run a server).
There probably is no acceptable reason to risk a system by running a telnet server, even for “testing.”