[SOLVED] dmesg shows odd output, not sure how else to explain it (deb 7.2)

saman007uk · 01-19-2014, 09:52 AM

Quote:

Originally Posted by slacker_

Is there a way to just have them dump the logs into a file instead of messing up my dmesg?

Yes. Look at here.

slacker_ · 01-21-2014, 11:24 AM

Quote:

Originally Posted by saman007uk

Yes. Look at here.

That blog post you linked to mentioned something that I'm not sure how to do:

Quote:

So, for each logging rule in your firewall script, add --log-prefix "iptables: ".

And it goes on to give an example with a firewall builder called firehol. I'm not using any firewall builder, so how do I add that "--log-prefix "iptables: " to my firewall script?

saman007uk · 01-22-2014, 08:22 AM

You need to improvise on that blog post. Your iptables rules already have the prefix "Inbound", so you don't need to add another prefix.

Run the following as root, and you are good:

Code:

apt-get update
apt-get install rsyslog
echo ":msg, startswith, \"Inbound: \" -/var/log/iptables.log" > /etc/rsyslog.d/iptables.conf
echo "& ~" > /etc/rsyslog.d/iptables.conf
service rsyslog restart

This will put all those log entries in /var/log/iptables.log. You might want to make a log rotation, as described at the end of that article.

slacker_ · 01-22-2014, 03:02 PM

Quote:

Originally Posted by saman007uk

You need to improvise on that blog post. Your iptables rules already have the prefix "Inbound", so you don't need to add another prefix.

Run the following as root, and you are good:

Code:

apt-get update
apt-get install rsyslog
echo ":msg, startswith, \"Inbound: \" -/var/log/iptables.log" > /etc/rsyslog.d/iptables.conf
echo "& ~" > /etc/rsyslog.d/iptables.conf
service rsyslog restart

This will put all those log entries in /var/log/iptables.log. You might want to make a log rotation, as described at the end of that article.

Oh. Brilliant. apparently I already had rsyslog installed. So after doing that, I'm still getting the "Inbound" thing coming up in dmesg. Now what...?

slacker_ · 06-07-2014, 07:04 PM

Just in case anyone was subscribed to this thread, I figured I'd update everyone on the status of the issue:

Source was iptables, but resolution was never found. I worked on it for quite a while before I gave up. One of the things I tried that I thought would work for sure was resetting everything related to iptables back to defaults, but even that didn't restore normal output of demsg.

I have since reinstalled debian wheezy (now 7.5) so the issue has, in a way, been taken care of, but not solved..