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.
Actually this was really easy...all i needed to so was load the sshd daemon...now i can connect.
One thing though...how do i get X11 Forwarding to work? That means i can get a remote desktop right? I edited the sshd_config file, but i cant get X to start remotely. Well, it starts, but the screen doesnt show remotely.
What is a good SSH utility that i can run from a command prompt?
X11 forwarding means that if you run a X server on your Win box, you can start X11 apps on your linux box and the window will pop up on your screen. You need to actually run such a thing on Windows, and then specify that you want to enable X11 forwarding. The latter is sometimes on, sometimes off, depending on the client you use, and sometimes it it sensitive to the existence of the $DISPLAY env. variable.
My favorite is the cygwin package (www.cygwin.com), you get a shell with nice unix commands, ssh among them (you need to say in the installation gui that you want that).
The # makes it a comment. But (I'm running RH, it may be different with SW) the commented-out options represent the default that sshd has. Make it
in the file (then restart sshd).
I don't use putty, so I don't know offhand how to control forwarding. cygwin's ssh lets you give all usual options, such as -v to actually see what's going on. Note that the forwarding is controlled on *both* sides, the server can allow or deny it, and the client can ask for it or not. You can make your desired behavior (with cygwin) the default with a file ~/.ssh/config, mine reads
I'm sure putty has the same capabilities, just that I don't use it.