search for: foox1234

...9;'shorewall check'' command shows a segmentation fault occurring and aborts reporting that I don''t have IPP2P support. Delving further I found shorewall''s test for ipp2p support in /usr/share/shorewall/lib.base where is it running the following command: $IPTABLES -A fooX1234 -p tcp -m ipp2p --ipp2p -j ACCEPT Note that I''ve correctly defined the $IPTABLES variable in the main config file to point to /usr/local/sbin/iptables instead of /sbin/iptables If I run the command directly myself I also get the segmentation fault: root@gecko:~# iptables -A fooX1234 -m...

Jason Wohlford wrote: > > linux:/etc/shorewall# shorewall check > /sbin/shorewall: line 261: Added: command not found > Loading /usr/share/shorewall/functions... > Processing /etc/shorewall/params ... > Processing /etc/shorewall/shorewall.conf... > /usr/share/shorewall/firewall: line 261: Added: command not found BTW -- it looks like you have a missing "#" on a

Hi all, I''m currently using ipsec with Shorewall 3.0.7 on a patched 2.6.10 kernel. Having heard that ipsec support was in the standard kernel starting from 2.6.16, I tried to upgrade to the last kernel. My problem is that shorewall won''t start anymore. I get this output in /var/log/shorewall-init.log: Starting Shorewall... Initializing... Shorewall has detected the

.../iptables -t mangle -L -n + /sbin/iptables -t mangle -L -n + MANGLE_ENABLED=Yes + CONNTRACK_MATCH= + MULTIPORT= + XMULTIPORT= + POLICY_MATCH= + PHYSDEV_MATCH= + IPRANGE_MATCH= + RECENT_MATCH= + OWNER_MATCH= + IPSET_MATCH= + ROUTE_TARGET= + XMARK= + CONNMARK= + CONNMARK_MATCH= + qt /sbin/iptables -N fooX1234 + /sbin/iptables -N fooX1234 + qt /sbin/iptables -A fooX1234 -m conntrack --ctorigdst 192.168.1.1 -j ACCEPT + /sbin/iptables -A fooX1234 -m conntrack --ctorigdst 192.168.1.1 -j ACCEPT + CONNTRACK_MATCH=Yes + qt /sbin/iptables -A fooX1234 -p tcp -m multiport --dports 21,22 -j ACCEPT + /sbin/iptables...

...when the host was added to the zone. For example, if eth0:1.2.3.4 is added to dynamic zone Z then traffic out of any firewall interface to 1.2.3.4 will obey the fw->Z policies and rules. This has been corrected. 4. Shorewall uses the temporary chain ''fooX1234'' to probe iptables for detrmining which features are supported. Previously, if that chain happened to exist when Shorewall was run, capabilities were mis-detected. New Features: 1. The output of "shorewall status" now includes the results of "i...

I am getting the following message when Shorewall stops can anybody shed any light on this message and where I should be looking? Thanks root@bobshost:~# shorewall stop Loading /usr/share/shorewall/functions... Processing /etc/shorewall/params ... Processing /etc/shorewall/shorewall.conf... Loading Modules... Stopping Shorewall...Processing /etc/shorewall/stop ... IP Forwarding Enabled