DebianThis forum is for the discussion of Debian Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
in "/var/log/messages" and at all of the virtual consoles. what package monitors network traffic like this? i removed snort because i thought that it was the culprit, but i still get the messages. i installed a counter strike server, so i get a lot of pings requesting the status of the server. i just want to ignore (get rid of) these messages for now.
You can stop these messages from showing up in console with "dmesg -n1", which you can put to some init script. If you find out how to prevent them from cluttering log messages, please let us know.
I wouldn't really say that it's Firestarter that is the reason for the messeges - don't shoot the messenger... I had a similar "problem" with Guarddog as the firewall, check out this thread for details.
You can stop these messages from showing up in console with "dmesg -n1", which you can put to some init script.
I found a better way than "dmesg -n1". I installed the "ulogd" package and added the line
Code:
FIREHOL_LOG_MODE="ULOG"
to /etc/default/firehol. Then I rebooted and now all firewall log messages go to /var/log/ulog/syslogemu.log (instead of cluttering console or system log messages).
That works with my FireHOL firewall. You need to consult ulogd documentation if you want to find out how to make it work with other firewalls, such as Firestarter or Guarddog.
I don't know if anyone was looking for a way to get these messages to stop for firestarter or shorewall (besides using "dmesg -n1" in a startup script), but I was. I found this to be useful.
For Debian it says edit /etc/init.d/klogd and set KLOGD="" to KLOGD="-c 5". Works like a charm!
Originally posted by six6 I don't know if anyone was looking for a way to get these messages to stop for firestarter or shorewall (besides using "dmesg -n1" in a startup script), but I was. I found this to be useful.
For Debian it says edit /etc/init.d/klogd and set KLOGD="" to KLOGD="-c 5". Works like a charm!
Though it is against my principles to adjust something at systemlevel, that effects every potential application, just to solve a specific application problem...
I tried the Shorewall tip, but no joy, Then i tried the Firehol's one and it worked perfectly, don't know the answer, the thing is, i followed Dead Parrot's instructions, went out on an errand for half an hour, and when i came back, there were no messages whatsover.
Dead Parrot: i don't care what your loved ones say about you, you are a prince. I haven't been able to solve this problem in the 2 years i've been using Linux, good show!
Do us all a favor, and copy/paste this tip to the sticky.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.