As explaine below and as explained by Tom in his previous mail you have to
redirect output to Ulogd. Replace the info entry in the Rules and Config file
by ULOG. Check:
http://leaf.sourceforge.net/devel/jnilo/bishorwall.html
Jacques
---
This S
On Thu, 3 Jul 2003 21:20:48 -0400, lbilyeu <[EMAIL PROTECTED]> wrote:
Does anyone know how to resolve the conflict?
I can't.
Very often, people who start by assuming that they can do something are
able to do it. Those who start by assuming that they can't do something
have failed before they h
Your Shorewall configuration is using syslogd -- The Bering 1.2
Shorewall
package has been modified to use ulog. Looks like the upgrade
instructions
that you followed are incomplete with respect to Bering 1.2.
I'm not surprised the instructions are incomplete.
I cobbled the HOWTO together from
On Thu, 3 Jul 2003 20:19:55 -0400, lbilyeu <[EMAIL PROTECTED]> wrote:
>b) what does "shorewall status | grep LOG" show you?
shorewall status | grep LOG > messages.txt
###the output of messages.txt is a follows
0 0 LOGall -- * * 0.0.0.0/0
0.0.0.0/0
---
>a) Are you using syslogd or ulogd for logging?
which syslogd
returns /sbin/syslogd
which ulogd
returns /usr/sbin/ulogd
###forgive me master, my meager skills are unable to determine.
###I am using whatever the s
On Thu, 3 Jul 2003 19:25:55 -0400, lbilyeu <[EMAIL PROTECTED]> wrote:
The file itself located at /var/log/shorewall.log is 0 bytes.
a) Are you using syslogd or ulogd for logging?
b) what does "shorewall status | grep LOG" show you?
-Tom
--
Tom Eastep\ Shorewall - iptables made easy
Shoreline
>> after the upgrade, the firewall performs correctly but the
>> shorewall.log is now broken.
>What does that mean exactly?
Shorewall functions as it did before the upgrade...
allows traffic that is allowed by the rulesets to get through
and denies those that should be denied.
shorewall status
shor
I have a successfully working bering1.2 installation.
I download the latest shorewall package v1.45 from TomEastep at
www.shorewall.net
I followed the upgrade procedure --see below
...
after the upgrade, the firewall performs correctly but the
shorewall.log is now broken. Can anyone determine w
