From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Shorewall config problem [SOLVED]
Date: Sun, 10 May 2015 10:17:24 +0100 [thread overview]
Message-ID: <2442871.vZ6LR7RNj4@wstn> (raw)
In-Reply-To: <6390922.lAtsHpQybt@wstn>
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]
On Wednesday 06 May 2015 16:20:19 I wrote:
> I've recently installed a new ADSL modem, and now I'm trying to get it to
> log to my LAN server. The modem seems to be sending log messages but
> Shorewall is dropping them at the server.
--->8
It seems I had missed something in the kernel configuration. I can't say what
exactly because I added several options (life's too short to go through all
the network options one at a time).
So now, Shorewall is not dropping syslog packets, and syslog-ng is logging
correctly. This is my /etc/syslog-ng/syslog-ng.conf:
----------------
@version: 3.6
@include "scl.conf"
options {
threaded(yes);
chain_hostnames(no);
stats_freq(43200);
mark_freq(0);
};
source src { system(); internal(); };
source s_remote { udp (ip(192.168.1.2) port(514) ); };
filter f_cron { facility (cron); };
filter f_ncron { not facility (cron); };
destination d_remote { file("/var/log/remote"); };
destination d_cron { file("/var/log/cron"); };
destination messages { file("/var/log/messages"); };
destination console_all { file("/dev/tty12"); };
log { source(src); filter(f_cron); destination(d_cron); };
log { source(src); filter(f_ncron); destination(messages); };
log { source(src); filter(f_ncron); destination(console_all); };
log { source(s_remote); destination(d_remote); };
----------------
I hope that will be useful to someone.
--
Rgds
Peter
[-- Attachment #2: Type: text/html, Size: 8158 bytes --]
prev parent reply other threads:[~2015-05-10 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 15:20 [gentoo-user] Shorewall config problem Peter Humphrey
2015-05-10 9:17 ` Peter Humphrey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2442871.vZ6LR7RNj4@wstn \
--to=peter@prh.myzen.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox