Fw: iptables -j LOG no going to syslogd but to dmesg....

["Pablo" <paa-listas@argentina.com>]

Sorry, was to the list... my error :·(

I use the standard syslogd, and that line is in syslogd.conf.

Thanks.
Pablo.

----- Original Message -----
From: "Phil Dyer" <phil@dyermaker.org>
To: "Pablo" <paa-listas@argentina.com>
Sent: Friday, January 06, 2006 5:30 PM
Subject: Re: iptables -j LOG no going to syslogd but to dmesg....


You only replied to me, not sure if you wanted to take it off the
debian-isp list or not...

anyway, make sure there is a line in your /etc/syslogd.conf that tells
it where to put kern.* messages... mine looks like this:

kern.*                          -/var/log/kern.log


If you are using syslog-ng, then look at the syslog-ng.conf file.


You should not need the ULOG stuff or anything like that. iptables uses
syslog by default.


-phil

Pablo said:
> Yes. The file is empty (0 bytes)
>
> Ls -l
> ...
> -rw-r-----   1 root        adm            0 2005-11-06 06:47 kern.log
> -rw-r-----   1 root        adm          591 2005-11-01 06:30 kern.log.0
> ...
>
> No logs in messages or daemon.log or similar
> # cd /var/log;
> # grep " Direct accest" *;
> #
>
> Thanks.
>
>
> -----Mensaje original-----
> De: Phil Dyer [mailto:phil@dyermaker.org]
> Enviado el: Viernes, 06 de Enero de 2006 01:45 p.m.
> Para: debian-isp@lists.debian.org
> Asunto: Re: iptables -j LOG no going to syslogd but to dmesg....
>
> Pablo said:
>> Helo,
>>
>>
>>
>> I have a rule to log some packets to syslogd, but they never go to that
>> place.
>>
>
>
> you should be looking in /var/log/kern.log for those messages. Is that
> where you're looking?
>


--

phil