Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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 have configured iptables to log all incoming packets in a separate file at /var/log location.
which is working fine, but the problem is :
--The logs are displayed to all terminal , dmesg along with the actual file (i.e /var/log/firewall.log)
My syslog contains :
##DUMP FIREWALL LOG : Added by Firewall Script
I come to know about dmesg LEVEL , using which , firewall messages can be avoided on dmesg, but have no idea about how to use it.
So it will be great help if any one can help me in fixing this issue (with dmesg /or any other way), also if possible , provide me some link , so that I can get full information about these Dmesg LEVELS. (what are the different level and how to use it ??).
After googling around, i tried to fix this by changing the /proc/sys/kernel/printk value.
FYI, my system current printk value is "3 4 1 7 "
I have no idea , what these value stands for , but it's not able to save my dmesg problem.
I come to know about dmesg LEVEL , using which , firewall messages can be avoided on dmesg, but have no idea about how to use it. (..) get full information about these Dmesg LEVELS.
Check 'man dmesg' (usage) which leads to 'man 8 syslogd' (syslog daemon nfo) which leads to 'man 3 syslog' (facility/priority) and 'man 2 syslog' (loglevel aka facility listing). You'll find using 'dmesg' is like 'dmesg -n n' where n is a facility between 0 and 7.
Thanks for your suggestion but still i am not able to fix it and need help !
Problem is when ever I try to enable log option (with level warn and redirect it to file in syslog.conf [as keren.warn filename]), it start logging to file as well as on screen/terminal, due to which my system accessibility get suffered.
Is there any way to fix it , so that log msg go only to mentioned file not to screen or dmesg.
Below are the steps I followed to log iprules;
-- Enable iptables log by
: iptables -I INPUT 1 -p tcp -s x.x.x.x -i eth0 -j LOG --log-prefix CH-IN: ALL tcp packets --log-level warn
--Setup syslog to log this to file at /var/log/firewall.log
: vi /etc/syslog.conf ;
But still the log message are at console along with dmesg and firewall.log