Re: [Shorewall-users] Logging Rejects via Syslog/Console

[Gilson S. <gil...@gi...>]

At 11:02 AM 5/8/2002 -0700, Tom Eastep wrote:
>On Wed, 8 May 2002, Tom Eastep wrote:
>
> > On Wed, 8 May 2002, Gilson Soares wrote:
> >
> > > I configured Shorewall to log only REJECTed packets.
> > > It's doing fine, sending to /var/log/messages, BUT it's also sending 
> to the
> > > console.
> > >
> > > I checked a lot of things but the SYSLOG is totally default, out of box.
> > > It's a RedHat 7.2 plain (minimal) installation, totally updated via RHN
> > > (up2date), with the default syslog.conf.
> > >
> > > I used the script below to test and only "emerg" priority were send 
> to the
> > > console.
> > >
>
>Unfortunately, logger and kernel printk use different mechanisms.
>
> > > I'm using REJECT:info. And only Shorewall messages are going to the 
> console.
> > >
> > > Any idea ?
> > >
> >
> > FAQ #16 -- http://www.shorewall.net/FAQ.htm#faq16
> >
>
>In RH7.2, there's a file called /etc/sysconfig/init that sets a variable
>called LOGLEVEL. That is passed to dmesg in the rc.sysinit script. In my
>RH setup, it is set to 3.
>
>You can see how the console is configured WRT kernel printk messages by:
>
>[root@gateway sysconfig]# cat /proc/sys/kernel/printk
>3       4       1       7
>[root@gateway sysconfig]#

My RH is:
7      4       1       7

So, as directed in the in FAQ (man dmesg), I issued:
dmesg -l 3

WORKED! But don't ask me HOW or WHEN or WHO changed this value.
Maybe another app (bind, squid, httpd). Anyway......

I just wanna know why only syslog messages about Shorewall (iptables) were 
going to console ?

Thanks
-Gilson