Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
You will need two pieces of software: the telnet sever (telnetd) and the telnet client. Telnet clients ate two-a-penny, even Internet Explorer has telnet ability! Be warned though, telnet is a very dangerous way of doing things! The telnet protocol has no security on it what-so-ever, if you type a password in on a telnet session, then anyone 'listening in' on that session will then know your password. I would advise that you forget that telnet ever existed and go for SSH. SSH works in the same (almost) manner as telnet, in that is requires a ssh server (sshd) and ssh clients, however, ssh is a very unix-like thing and you have to hunt around for Windows based ssh clients. Having said that, it is much more secure than plain telnet, so you should be ok. Oh, and the server and Linux client software will be on your distro's install CD.
Just a small question on win ssh client. I find it giving me new window ( with shell and I loged in ) when I press on a icon. This means that win client is storing the paswd some where. If we are so much careful about passwds and do use ssh, is it safe to use win clients?