Hi,
on Fedora 24, I've installed the "telnet-server" with
# dnf install telnet-server
But, still, I cannot login. I'm getting "Connection refused". Seems that it is not enabled.
What else do I need to do?
regards, chris
On Wed, Sep 6, 2017 at 3:18 PM, Christian Groessler chris@groessler.org wrote:
Hi,
on Fedora 24, I've installed the "telnet-server" with
# dnf install telnet-server
But, still, I cannot login. I'm getting "Connection refused". Seems that it is not enabled.
I would ask why you would choose a telnet server over ssh but assuming you had a good reason...
What else do I need to do?
Have you changed the firewall setting to allow incoming connections?
Assuming you have a full desktop (not a CLI only install) you want firewall-config if you don't have it already installed.
Thanks, Richard
Hi,
On 09/06/17 22:30, Richard Shaw wrote:
On Wed, Sep 6, 2017 at 3:18 PM, Christian Groessler <chris@groessler.org mailto:chris@groessler.org> wrote:
on Fedora 24, I've installed the "telnet-server" with # dnf install telnet-server But, still, I cannot login. I'm getting "Connection refused". Seems that it is not enabled.I would ask why you would choose a telnet server over ssh but assuming you had a good reason...
Yes, I have a good reason :-) It's on a local network and I want to test a telnet client running on an 8-bit machine. ssh would be a bit too heavy for a 6502....
What else do I need to do?Have you changed the firewall setting to allow incoming connections?
No. I think I had the firewall disabled on this machine (long before)...
Assuming you have a full desktop (not a CLI only install) you want firewall-config if you don't have it already installed.
... firewall-config loops endlessly with "Trying to connect to firewalld, waiting..."
Also, "netstat -tuna | grep :23" doesn't show an open port at 23. So I think no one is listening on the telnet (23) port.
regards, chris
On Wed, 6 Sep 2017, Christian Groessler wrote:
Also, "netstat -tuna | grep :23" doesn't show an open port at 23. So I think no one is listening on the telnet (23) port.
The telnet daemon in.telnetd is traditionally started when required by xinetd, but it seems systemd has taken that role over in recent Fedora versions, so you probably need to check the systemd is doing sensible things. Incidentally, Fedora 24 is now End Of Life, so you should think about upgrading.
Michael Young
Is theTæ port Open in the firewall??
Den 6. sep. 2017 22.19 skrev "Christian Groessler" chris@groessler.org:
Hi,
on Fedora 24, I've installed the "telnet-server" with
# dnf install telnet-server
But, still, I cannot login. I'm getting "Connection refused". Seems that it is not enabled.
What else do I need to do?
regards, chris _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On 09/07/2017 04:18 AM, Christian Groessler wrote:
on Fedora 24, I've installed the "telnet-server" with
# dnf install telnet-server
But, still, I cannot login. I'm getting "Connection refused". Seems that it is not enabled.
What else do I need to do?
I don't have an F24 system at the moment. Only F26.
But, first, to respond to other items brought up in replies. (Yes, I know you have disabled your firewall).
[egreshko@meimei ~]$ telnet 192.168.1.137 Trying 192.168.1.137... telnet: connect to address 192.168.1.137: No route to host
The above means the firewall is blocking port 23
[egreshko@meimei ~]$ telnet 192.168.1.137 Trying 192.168.1.137... telnet: connect to address 192.168.1.137: Connection refused
The above means the port is enabled but there is no service running.
OK, now to the answer for F26 and probably the same on F24....
[root@f26-rc15k xinetd.d]# systemctl enable telnet.socket Created symlink /etc/systemd/system/sockets.target.wants/telnet.socket → /usr/lib/systemd/system/telnet.socket
[root@f26-rc15k xinetd.d]# systemctl start telnet.socket [root@f26-rc15k xinetd.d]#
And as we can see from another host....
[egreshko@meimei ~]$ telnet 192.168.1.137 Trying 192.168.1.137... Connected to 192.168.1.137. Escape character is '^]'.
Kernel 4.12.9-300.fc26.x86_64 on an x86_64 (3) f26-rc15k login: egreshko Password: Last login: Thu Sep 7 05:49:49 from 192.168.1.18
On 09/07/17 00:56, Ed Greshko wrote:
On 09/07/2017 04:18 AM, Christian Groessler wrote:
But, still, I cannot login. I'm getting "Connection refused". Seems that it is not enabled.
What else do I need to do?
[snip]
OK, now to the answer for F26 and probably the same on F24....
# systemctl enable telnet.socket # systemctl start telnet.socket
Thank you very much! This did it!
I'm still not very comfortable with systemd....
regards, chris
On 09/07/2017 07:17 AM, Christian Groessler wrote:
Thank you very much! This did it!
Welcome...
I'm still not very comfortable with systemd....
FWIW, this one is a bit "odd" even my systemd standards.
Most daemons would have a service file. And you would expect a /lib/systemd/system/telentd.service file. With the d in telnetd standing for daemon.
But that isn't the case. You have a telnet@.service and telnet.socket files. And the .service file can't be enabled as one would normally expect. There also appears to be no actual documentation, or documentation that could be found easily, so you "just have to know" it would seem.
Maybe that is "Red Hat's" way of discouraging the use of telnet.
-
Christian Groessler -
Ed Greshko -
Michael Young -
René Harder Olsen -
Richard Shaw