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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am trying to connect to my ssh server over a very high latency connection. I am guessing the connection is timing out when I try to connect. When I connect from a low latency connection I have no problems. Any ideas on what settings I can change on the ssh server to work with high latency connections?
well you'd need a pretty astonishing latency to see somethign that dramatic... are you actually connecting at all? run "tcpdump port 22 -n" to see the ssh activity on the system, see if packets actually are coming back, and what's happening around the time of a timeout...
ok, well the full output would be more useful, but the server has reset you... that's an explicit refusal from the server, *OR* something inbetween spoofing a server packet, like a firewall, IDS or something.
I can't post the full output. I am pretty sure out firewall doesn't block ssh traffic and I have our firewall guys double checking that for me. I know the server is not set up to block any one from connecting to ssh on it.