shorewall doesn't start

Bug #103065 reported by rodrigochinaski
2
Affects Status Importance Assigned to Milestone
shorewall (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: shorewall

root@starkey:~# shorewall start
Compiling...
Initializing...
Determining Zones...
   IPv4 Zones: net loc
   Firewall Zone: fw
Validating interfaces file...
Validating hosts file...
   Bridge ports are: eth0 eth2
Validating Policy file...
Determining Hosts in Zones...
   net Zone: ppp0:0.0.0.0/0
   loc Zone: br0:eth0 br0:eth2 br0:192.168.0.5 ppp1:0.0.0.0/0 eth1:0.0.0.0/0
Pre-processing Actions...
   Pre-processing /usr/share/shorewall/action.Drop...
   Pre-processing /usr/share/shorewall/action.Reject...
   Pre-processing /usr/share/shorewall/action.Limit...
Deleting user chains...
Compiling /etc/shorewall/routestopped ...
Creating Interface Chains...
Compiling Proxy ARP
Compiling NAT...
Compiling NETMAP...
Compiling Common Rules
Compiling Blacklisting...
Adding Anti-smurf Rules
Enabling RFC1918 Filtering
Compiling TCP Flags checking...
Compiling Kernel Route Filtering...
Compiling IP Forwarding...
Compiling /etc/shorewall/rules...
Compiling Actions...
Compiling /usr/share/shorewall/action.Drop for Chain Drop...
Compiling /usr/share/shorewall/action.Reject for Chain Reject...
Compiling /etc/shorewall/policy...
Compiling Masquerading/SNAT
Compiling Traffic Control Rules...
Validating /etc/shorewall/tcdevices...
Validating /etc/shorewall/tcclasses...
Compiling Rule Activation...
Compiling Refresh of Black List...
Validating /etc/shorewall/tcdevices...
Validating /etc/shorewall/tcclasses...
Shorewall configuration compiled to /var/lib/shorewall/.start
Starting Shorewall....
Initializing...
Clearing Traffic Control/QOS
Deleting user chains...
Enabling Loopback and DNS Lookups
Creating Interface Chains...
Setting up Proxy ARP...
Setting up one-to-one NAT...
Setting up SMURF control...
Setting up Black List...
Adding Anti-smurf Jumps...
Setting up RFC1918 Filtering...
Setting up TCP Flags checking...
Setting up ARP filtering...
Setting up Route Filtering...
Setting up Accept Source Routing...
IP Forwarding Enabled
Setting up SYN Flood Protection...
Setting up IPSEC management...
Setting up Rules...
Setting up Actions...
Creating action chain Drop
Creating action chain Reject
Creating action chain dropBcast
Creating action chain dropInvalid
Creating action chain dropNotSyn
Applying Policies...
Setting up Masquerading/SNAT...
Setting up TC Rules...
Activating Rules...
iptables: Invalid argument
   ERROR: Command "/sbin/iptables -A OUTPUT -o br0 -m physdev --physdev-out eth0 -m policy --pol none --dir out -j fw2loc" Failed
IP Forwarding Enabled
Terminated

ProblemType: Bug
Architecture: i386
Date: Wed Apr 4 17:58:54 2007
DistroRelease: Ubuntu 7.04
Uname: Linux starkey 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

Revision history for this message
rodrigochinaski (rodrigo-chinaski) wrote :

running the above command gives me:

root@starkey:~# /sbin/iptables -A OUTPUT -o br0 -m physdev --physdev-out eth0 -m policy --pol none --dir out -j fw2loc
iptables v1.3.6: Couldn't load target `fw2loc':/lib/iptables/libipt_fw2loc.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.