Hi,
I just had the same problem. It seems to me that if you don't want the
messages to be stored at all you should stop them from being logged.
I installed kmyfirewall to manage my iptables. It generates the iptables
script automatically. The following lines enable logging:
for i /proc/sys/net/i
Bob Proulx wrote:
> Jeff Elkins wrote:
>> I'm trying to rid myself of annoying iptables messages that are clogging
>> up the console and dmesg.
>
Easy. Try:
# aptitude ulogd
This puts firewall logs into a custom log file - see /etc/ulogd.conf
You need to have a kernel that contains the ipt_U
Jeff Elkins wrote:
> I'm trying to rid myself of annoying iptables messages that are clogging up
> the console and dmesg.
The Linux kernel default console logging is 8 so that all messages are
logged to the console. At least one other distro sets this to 3 in
/etc/syscontrol/init and so users th
On Thu, Jun 23, 2005 at 06:37:03PM -0500, [EMAIL PROTECTED] wrote:
> Quoting Alban Browaeys <[EMAIL PROTECTED]>:
>
> > Le Wed, 15 Jun 2005 15:39:07 -0400, Jeff Elkins a écrit
> > :
> >
> > > I'm trying to rid myself of annoying iptables messages
> > that are clogging up
> > > the console and dme
Quoting Alban Browaeys <[EMAIL PROTECTED]>:
> Le Wed, 15 Jun 2005 15:39:07 -0400, Jeff Elkins a écrit
> :
>
> > I'm trying to rid myself of annoying iptables messages
> that are clogging up
> > the console and dmesg. To my firewall script I've
> added:
> >
> > echo 0 >
> /proc/sys/net/ipv4/netf
Le Wed, 15 Jun 2005 15:39:07 -0400, Jeff Elkins a écrit :
> I'm trying to rid myself of annoying iptables messages that are clogging up
> the console and dmesg. To my firewall script I've added:
>
> echo 0 > /proc/sys/net/ipv4/netfilter/ip_conntrack_log_invalid
>
> And to sysklogd:
>
> KLOGD="
> Have you tried using ulog? You need to patch your kernel. It allows all
> firewall logs to go into a nominated log file, and does not put them in
> the dmesg.
Correction - no kernel patch is required. It works correctly "out of the
box".
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> The console messages seem to be gone, but dmesg is still clogged with
> iptables
> junk.
Have you tried using ulog? You need to patch your kernel. It allows all
firewall logs to go into a nominated log file, and does not put them in the
dmesg.
I use it in my gentoo server (I'm too scared t
On Thursday 16 June 2005 06:16 am, Shaun Lipscombe wrote:
> * Jeff Elkins wrote:
> > New not syn:IN=eth1 OUT= MAC=00:30:1b:3d:ed:0e:00:02:3b:01:dd:e1:08:00
> > SRC=64.14.56.90 DST=64.45.235.41 LEN=41 TOS=0x00 PREC=0x00 TTL=240
> > ID=21627 PROTO=TCP SPT=80 DPT=36366 WINDOW=64687 RES=0x00 ACK PSH UR
On Wednesday 15 June 2005 04:13 pm, Jan C. Nordholz wrote:
> Hi!
>
> > I'm trying to rid myself of annoying iptables messages that are clogging
> > up the console and dmesg. To my firewall script I've added:
>
> Well, dmesg just reads the kernel's debugging ringbuffer, where _every_
> printk() the
Hi!
> I'm trying to rid myself of annoying iptables messages that are clogging up
> the console and dmesg. To my firewall script I've added:
Well, dmesg just reads the kernel's debugging ringbuffer, where _every_
printk() the kernel issues is recorded. You can't keep messages from
appearing ther
11 matches
Mail list logo
