Re: [Shorewall-users] Change log path problem

2006-10-02 Thread Wong Chee Chun
what you can do here is to employ ulogd and shorewall together, instead of using syslog. Ulogd is available at http://www.netfilter.org/projects/ulogd/index.html. cheers! On 10/3/06, Wilson Kwok <[EMAIL PROTECTED]> wrote: Hello, I changed the log path in shorewall.conf, LOGFILE=/var/log/

Re: [Shorewall-users] Change log path problem

2006-10-02 Thread Tom Eastep
Wilson Kwok wrote: > I changed the log path in shorewall.conf, > LOGFILE=/var/log/messages to LOGFILE=/var/log/shorewall, and then I > touched the shorewall file in /var/log, permission root:root 600, after > shorewall restart, no logging messages appear in /var/log/shorewall. so > how can I

[Shorewall-users] Change log path problem

2006-10-02 Thread Wilson Kwok
Hello,     I changed the log path in shorewall.conf, LOGFILE=/var/log/messages to LOGFILE=/var/log/shorewall, and then I touched the shorewall file in /var/log, permission root:root 600, after shorewall restart, no logging messages appear in /var/log/shorewall. so how can I fix this problem ?

Re: [Shorewall-users] Error after update

2006-10-02 Thread Tom Eastep
Elio Tondo wrote: > From: "Tom Eastep" <[EMAIL PROTECTED]> > >>> It used to work with no problems with Shorewall 3.0 and also with earlier >>> 3.2 releases >> I need to know which earlier 3.2 release(s). > > I am not sure to be able to track this down, because the two firewalls are > managed by o

Re: [Shorewall-users] Error after update

2006-10-02 Thread Elio Tondo
From: "Tom Eastep" <[EMAIL PROTECTED]> > > It used to work with no problems with Shorewall 3.0 and also with earlier > > 3.2 releases > > I need to know which earlier 3.2 release(s). I am not sure to be able to track this down, because the two firewalls are managed by other people (I only did th

Re: [Shorewall-users] Error after update

2006-10-02 Thread Tom Eastep
Tom Eastep wrote: > Tom Eastep wrote: >> Elio Tondo wrote: >> >>> and in the masq file: >>> >>> #INTERFACE SUBNET ADDRESS PROTO PORT(S) >>> IPSEC >>> eth0 eth1!192.158.10.5,192.158.10.60 >>> >>> (masquerading for all machines in loc except for the

Re: [Shorewall-users] Error after update

2006-10-02 Thread Tom Eastep
Tom Eastep wrote: > Elio Tondo wrote: > >> and in the masq file: >> >> #INTERFACE SUBNET ADDRESS PROTO PORT(S) IPSEC >> eth0 eth1!192.158.10.5,192.158.10.60 >> >> (masquerading for all machines in loc except for the two with static NAT). >> >> It u

Re: [Shorewall-users] Error after update

2006-10-02 Thread Tom Eastep
Elio Tondo wrote: > > I have two machines in the loc zone with a static NAT: > > #EXTERNAL INTERFACE INTERNALALL LOCAL > # INTERFACES > xxx.xxx.xxx.254 eth0192.168.10.5 No No > xxx.

Re: [Shorewall-users] Error after update

2006-10-02 Thread Tom Eastep
Elio Tondo wrote: > > and in the masq file: > > #INTERFACE SUBNET ADDRESS PROTO PORT(S) IPSEC > eth0 eth1!192.158.10.5,192.158.10.60 > > (masquerading for all machines in loc except for the two with static NAT). > > It used to work with no prob

[Shorewall-users] Error after update

2006-10-02 Thread Elio Tondo
On two firewalls I have errors after a Shorewall update; no changes have been done on the configuration files. Current situation on one of the two installations (the other one is similar): - Fedora Core 4 - shorewall-3.2.4-1.fc4 - iptables-1.3.0-2 I have two machines in the loc zone with a stati