search for: strip_file

...6,10 @@ echo "$config does not exist!" >&2 exit 2 fi + # + # Determine the capabilities of the installed iptables/netfilter + # + determine_capabilities [ -z "${STATEDIR}" ] && STATEDIR=/var/state/shorewall @@ -4728,10 +4732,6 @@ strip_file interfaces strip_file hosts # - # Determine the capabilities of the installed iptables/netfilter - # - determine_capabilities - # # Check out the user''s shell # [ -n "$SHOREWALL_SHELL" ] || SHOREWALL_SHELL=/bin/sh

Been trying to track down an issue where when I issue a restart on shorewall it stalls for maybe 5 minutes. I have tracked it down to the removing of the rules portion but have not been able to get any closer yet. Some place after "strip_file rules" and echo "Deleting user chains..." It seems to fix itself after a reboot of the system for an unknown time then it resurfaces again. Probably related to the kernel or something on the box it self but I figured I would run it by you and see if you have heard of anything like t...

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

...39;']'' ++ case $val in ++ echo '''' + SAVE_IPSETS= ++ added_param_value_no CROSSBEAM No ++ local val=No ++ ''['' -z No '']'' ++ case $val in ++ echo '''' + CROSSBEAM= + ''['' -z eth0 '']'' + strip_file interfaces + local fname + ''['' 1 = 1 '']'' ++ find_file interfaces ++ local saveifs= directory ++ case $1 in ++ ''['' -n '''' -a -f /interfaces '']'' ++ saveifs='' '' ++ IFS=: ++ for directory in ...

Let''s move this to the Shorewall Development list.... On Tuesday 10 February 2004 03:14 pm, xavier wrote: > here is a patch to allow this : > |ACCEPT<10/sec:20>:debug fw lan:$ntp_servers udp 123 - - - - ntp > > a problem with the patch is that now the logprefix is mandatory. > i''m trying to debug it, but i can''t find the flaw. Also, with

This is a minor release of Shorewall. WARNING: This release introduces incompatibilities with prior releases. See http://www.shorewall.net/upgrade_issues.htm. Changes are: a) There is now a new NONE policy specifiable in /etc/shorewall/policy. This policy will cause Shorewall to assume that there will never be any traffic between the source and destination zones. b) Shorewall no longer

Hi, I installed the shorewall 1.3.8-2 debian package to my debian testing machine which serves as the gateway to the internet. Since I have two other machine connect to internet thru this gateway machine, I also downloaded the configuration guide for "basic two-interface firewall" and followed the instructions. When I try to start the shorewall I get the following message and can not