Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
not a great output, use "iptables -L -n -v" instead for clearer output but with a little added guesswork...
1) Send everything on an unshown interface to a "LOCALINPUT" target, presumably lo
2) Accept everything on an unshown interface (lo again? clashes with above...??)
3) Accept incoming UDP DNS requests from that IP
4) Accept incoming TCP DNS requests from that IP
5) Accept incoming UDP DNS responses from that IP
6) Accept incoming TCP DNS responses from that IP
7) Accept UDP DNS replications from that IP
8) Send all borked TCP packets to the INVALID table
9) Accept everything that is already known and passed.
Was that all the output? There should at the least be a chain called LOCALINPUT that's missing.
the 194.* address appears to be a DNS server due to the ports the rule is matching. check /etc/resolv.conf to see if the IP is listed there.
RELATED, ESTABLISHED rules are generally safe and very efficient (should be at the top of the chains so they action quicker), so no, you shouldn't worry about it. It means the traffic has already been matched and ACCEPTed somewhere else.