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.
There is less than 2 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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.
Is it possible to grep something from the tcpdump summary? Like: tcpdump -nn -c100 | grep "packets dropped by kernel"
But that somehow doesn't work, it only pipes the packets itself, but the summary seems to be written to another stdout or something. I want to grep/awk one of these lines:
0 packets captured
0 packets received by filter
0 packets dropped by kernel
Thank you for your reply and your explaination, very helpful. I'm now trying to do the same with the script from the first answer of this topic and it doesn't work with both of your solutions. Any suggestion on this one? Thank you in advance, much appreciated.
The principle is identical, except that business_kid threw an unnecessary tempfile/pipe to the mix. My post demonstrates how it can all be done with a single command. Also, I took the time to add a link so that you can study it in more detail.
And it doesn't help much to just say that something "didn't work". What exactly did you try, and what exactly happened when you tried it? We can't see your screen, so we can't figure out what went wrong unless you give us enough detail to work with.