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'm looking for a Linux utility (command line or GUI) that is capable of telling you the complete domain name of any connections that are made to and from your machine. An added bonus would be a utility that knows what application is making the connections.
Netstat is a problem because it truncates domain names. I'm totally making this up, but if the name is too long it kind of looks like:
It never ceases to amaze me how scalable Linux is!
Although that is true as well, this is more of a case of flexibility =). lsof is a great tool and it's often under appreciated. lsof can help you figure out what program is locking down a certain file or the reverse, what files a program is using; hence the name (LiSt Open Files). Another thing about lsof is that most root kits don't trojan it, so if you think your computer might be compromised and netstat doesn't show anything funny, try lsof -i, it might just pop up that otherwise hidden connection.