Though the maintainers thought the two shorewall-perl updates( to -3)
would fix the incompatibility with latest iptables, and the bugs marked
closed, nevertheless the exact problem remains uncorrected and
shorewall-perl crashes. Downgrading to iptables 1-3 works. The error
was on this .iptables-restore-input line:
-A zlcl12fw -p 6 --dport 3128 -m conntrack --ctorigdst ! 192.168.0.1 -j
ACCEPT ...
The log:
09:39:32 Running /sbin/iptables-restore...
iptables-restore v1.4.1.1: host/network `!' not found
...
09:39:31 Generating Rule Matrix...
09:39:31 Creating iptables-restore input...
09:39:31 Compiling iptables-restore input for chain blacklst...
09:39:31 Shorewall configuration compiled to /var/lib/shorewall/.start
09:39:31 Processing /etc/shorewall/params ...
09:39:31 Starting Shorewall....
09:39:31 Initializing...
09:39:31 Loading Modules...
09:39:31 Processing /etc/shorewall/init ...
09:39:32 Setting up ARP filtering...
09:39:32 Setting up Route Filtering...
09:39:32 Setting up Martian Logging...
09:39:32 Setting up Accept Source Routing...
09:39:32 Setting up Proxy ARP...
09:39:32 Setting up Traffic Control...
09:39:32 Adding IP Addresses...
09:39:32 IP Address 64.4.171.82 added to interface eth1 with label eth1:1
09:39:32 Preparing iptables-restore input...
09:39:32 Running /sbin/iptables-restore...
iptables-restore v1.4.1.1: host/network `!' not found
Error occurred at line: 265
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
ERROR: iptables-restore Failed. Input is in
/var/lib/shorewall/.iptables-restore-input
09:39:32 Processing /etc/shorewall/stop ...
09:39:32 IP Forwarding Enabled
09:39:32 Processing /etc/shorewall/stopped ...
Terminated
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
