Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
In which case you'd want to install telnetd (telnet daemon).
Redhat doesn't install it by default, so you'll have to go to your cd's and install
telnet-server-0.17-20.i386.rpm
although your version numbers might differ. Once installed you'll need to edit your /etc/xinetd.d/telnet file and change 'disabled = yes' to 'no'.
That said, acid has a very valid point which is that you're *much* better off using ssh, as
a) It's much more secure (doesn't transmit passwords in the clear )
b) It allows you to do things like tunnel traffic across your ssh connection (X windows is an example)
c) Allows for compression of traffic, saving yourself bandwith.
If you installed everything from your distro's CD roms all you have to do is do a "chkconfig --list | grep telnet" and then use
"chkconfig --level 345 telnetname" to turn it on. Where telnetname is the name of the telnet daemon that you got from the chkconfig --list command, it's probably telnetd but i'm not positive.
except that telnet is an inetd service and relies on xinetd to start and stop it.
So urm.. no.
the result of your 'chkconfig --list | grep telnet' would look like this :
telnet: on
for a machine with a functioning telnet server, and would return nothing at all for a machine without it installed.
chkconfig --level 345 <something> would ordinarily turn <something> on, yes... but not in this case. Like I said.. it's wrapped into inetd.
It's also an exceptionally bad idea to be implying that 'installing everything from your distro's CD roms' is an okay thing to do. It's not. On so many levels...
I can only finish with the rather obvious observation that the poor originator of this message has not installed verything from his cd's.
hi guys, i got another two question related to this subject. what is the level 345 means?
and second question is related to the 'telnet' file which is located in /etc/xinetd.d/telnet . what should i do to pop up or to display a welcome or instruction message whenever someone get connected on login to my telnet server?
what should i changed or add in the 'telnet' server?
The level 345 refers to your runlevels. If you boot to a GUI login prompt then you are using runlevel 5. If you boot to a text logon prompt you are using runlevel 3. Its rare that anyone boots to runlevel 4 so you can usually just leave that out of your --levels switch.
The file that deals with the message that pops up when someone logs in is the /etc/motd . MOTD stands for Message Of The Day. Whatever you put in that file, be it a text message or an ASCII drawing, will pop up every time someone logs in.
Hey Crashed_Again!!!... you just did it again. you are fabulous man... you are amazing. how could you reply so fast. it seem like you are always in front of your PC 24-7.
and... that make me confuse. if you are unemployed and broke, how could affort to have a such internet connection so long. it's free? how do you pay the ISP company?
Bah.. Crashed get's all the credit for dipping into a conversation right at the very end?
*mutter*
Crashed also lives in the US. So he gets free local phone calls (or has a cable modem) and is able to sit online 24/7 without having to pay by the minute, unlike those in Europe.
Sorry Slick I take all the credit that was given to me and I give it to you okay? Does that make you happy? Where do you live in Europe anyway? I'm sorry that I have a cable modem connection and that I don't have a job right now so I am online all the time. Sorry boss...
urm, i always dreaming to have PC always connected to internet. but never know when the day will come. then i will able to download all the 5 CDs of redhat 8.0.
you are lucky crashed. and as far as i know a man that have such knowledge in IT(information technology) or something like that, will have a good income in my place. but it may be differ in your place.
I'm a newbie to Linux, with the same desire to turn on Telnet. Sure, it may not be the most secure thing around, but I'm in a test environment just learning this OS, so it's good to learn some of this basic stuff & worry about security later.
I didn't see the exact answer to turning on Telnet in the posts here to help me, but I was able to figure it out with the information that was provided.
"chkconfig" was the key.
I ran this statement to get the name of the telnet daemon:
chkconfig --list | grep telnet
This was the output:
telnet: off
krb5-telnet: off
Then I ran this statement to turn Telnet on:
chkconfig telnet on
I then verified that it was indeed turned on by running the previous statement again. I then tested it & I was able to telnet to this server.
Note: The level option was not applicable for this particular daemon. If you run "chkconfig --list" you'll see that other daemons do have the various "levels," but not telnet.
well.. that is good. at first i also of the opinion that it is ok to learn the telnet first before going further. but now i realize that telnet is not a good option. it is not secure, it is not safe especially when you are in a network or connected to unsecured network (internet). however, i do run telnet but in a standalone PC.
well.. that is good. at first i also of the opinion that it is ok to learn the telnet first before going further. but now i realize that telnet is not a good option. it is not secure, it is not safe especially when you are in a network or connected to unsecured network (internet). however, i do run telnet but in a standalone PC. i think it is verry good idea to switch to SSH and i am looking toward it now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.