Here is another handy little trick for tcpdump that will help you identify some potential network issues. Often times when there is some trouble along the line you will see reset connections. This happens for many reasons and can be an indication of everything form a network program to a crashed application that suddenly stops responding.
When I was getting started using Quicksilver I was always hearing about all the great things it would do, but it was a struggle to get it set up the right way to get at that functionality. In order to prevent that struggle for others I am including my basic set up.
I keep telling everyone they need to try out Quicksilver, that it is the most amazing app. Then they ask me what it does, and I generally say, “it’s hard to explain.” Which it is. Then I fumble around to demonstrate a few things that never seems to do it justice. I need Ron Popeil to pop out and say, “but wait, there’s more.”
You see that light blinking like crazy on the switch, and want to see what it is that your systems is doing? If you are on a (u|li)n[i|u]x or bsd of some sort pick up a copy of tcpdump. If you are on OS X it is already included.
Now that you have created keys for logging into you servers, you might find that you are moving between systems, or you just don’t like leaving your keys behind when you go home. There is a quick fix for this.
In the last post I suggested you add a passphrase to keep your private key secure. The problem with this is that now you have traded entering a password for entering a passphrase which is most likely longer. Doesn’t seem like such a great trade off.
Are you sick of typing in passwords when sshing into systems or when transferring files of scp of sftp. Well the good news is that there is an easier and safer way to do this with ssh keys.