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.
I'm new to the whole SSH thing, and I can't get it to work. I've googled left and right, but haven't found any answers.
I am trying to get SSH to work just between two Ubuntu desktops on a local LAN. sshd is running, and I use firestarter and have port 22 open to SSH, and everything else (like pinging) between the two computers works. But when I try:
or any variation thereof, I get the message:
ssh: connect to host 192.168.1.101 port 22: Connection refused
and exactly the same when I try from the other computer to this one. Any help would be appreciated.
the main reason may be that the public keys generated by the server has changed for some reason in the client. this may happen when u have reinstalled the ssh server.this changes the ssh public keys and shows a mismatch in the client. for that remove the file ".known_hosts" in "~/.ssh/" where ~ is the home directory of the user by which u r trying to login. now retryin ssh to the server. this may show a message that a new key has been recieved. type yes . this brings the ssh session into existence. if this worked for u click on the thanks button. bye happy sshing ...
u have to make shore that sshd is running on the remote computer.
and the command u type is correct if u have the user with the same name as the user on your computer.
if we assume that I have a user called ipolit on the remote machine the command is
You can also login to 22.214.171.124 from 100.72.232.207 without entering a password or passphrase? Specifying two remote destinations needs ssh-key authentication (maybe with agent forwarding), as otherwise you would have to reveal your password or passphrase to one of the remote servers. It’s a safety measure.