search for: startup_error

Displaying 10 results from an estimated 10 matches for "startup_error".

2006 Oct 23
3
command not found error
I am running version 3.0.7 of Shorewall on a Debian Sarge system, but when I start Shorewall I get this: /usr/share/shorewall/firewall: line 204: 4: command not found I looked there and found this: # Run ip and if an error occurs, stop the firewall and quit # run_ip() { if ! ip $@ ; then if [ -z "$STOPPING" ]; then error_message "ERROR: Command \"ip
2005 May 25
5
Patch to fix dynamic add/delete to zone functinality
...,16 +7001,20 @@ while read z hosts; do if [ "$z" = "$zone" ]; then + found= for h in $hosts; do + [ -n "$found" ] && break for host in $hostlist; do if [ "$h" = "$host" ]; then - rm -f ${STATEDIR}/zones_$$ - startup_error "$host already in zone $zone" + found=Yes fi done done - - [ -z "$hosts" ] && hosts=$hostlist || hosts="$hosts $hostlist" + if [ -n "$found" ]; then + error_message "Warning: $host does appear to be in zone $zone a...
2003 Aug 12
1
Shorewall Keeps sending false IP Address Conflict
...['' 1 -gt 1 '']'' + trap ''my_mutex_off; exit 2'' 1 2 3 4 5 6 9 + command=start + ''['' 1 -ne 1 '']'' + do_initialize + export LC_ALL=C + LC_ALL=C + PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin + terminator=startup_error + version= + FW= + SUBSYSLOCK= + STATEDIR= + ALLOWRELATED=Yes + LOGRATE= + LOGBURST= + LOGPARMS= + ADD_IP_ALIASES= + ADD_SNAT_ALIASES= + TC_ENABLED= + LOGUNCLEAN= + BLACKLIST_DISPOSITION= + BLACKLIST_LOGLEVEL= + CLAMPMSS= + ROUTE_FILTER= + NAT_BEFORE_RULES= + DETECT_DNAT_IPADDRS= + MUTEX_TIMEOUT= +...
2004 Feb 10
22
Re: [Shorewall-newbies] specific log-prefix ... patch
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
2004 Sep 14
1
start error "invalid interface" on shorewall 2.08
...39;' xnet = xnet '']'' + return 0 + list_search eth0:1 eth0 + local e=eth0:1 + ''['' 2 -gt 1 '']'' + shift + ''['' xeth0:1 = xeth0 '']'' + ''['' 1 -gt 1 '']'' + return 1 + wildcard= + startup_error ''Invalid Interface Name: eth0:1'' + echo '' Error: Invalid Interface Name: eth0:1'' Error: Invalid Interface Name: eth0:1 + my_mutex_off + ''['' -n Yes '']'' + mutex_off + rm -f /var/lib/shorewall/lock + have_mutex= + ''[...
2004 Dec 05
13
Adding dynamically more than one host at once?
Hi, it seems not to be possible to add more than one host at once to a zone. So shorewall add br0:eth0:192.168.2.10,eth0:192.168.2.11 work fails, since "br0:eth0:192.168.2.10,eth0" is interpreted as one interface. --snip -- iptables v1.2.9: interface name `eth0:192.168.2.10,eth0'' must be shorter than IFNAMSIZ (15) Try `iptables -h'' or ''iptables
2005 Apr 10
28
dumb, dumb question
I''m very new to shorewall. My setup is IP Gateway (CentOS 4 + Shorewall) with 3 NIC cards. Shorewall works great on the firewall machine. Bind also works (local net machines get IPs fine). Under firestarter, all works great. With shorewall, the loc machines can not route past the firewall. They can connect to the firewall, but not past it. Exactly what information should I post to get
2003 Mar 23
12
Shorewall 1.4.1
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
2005 May 31
11
More Tests for 2.4.0-RC2 - strange behaviour
...rap ''my_mutex_off; exit 2'' 1 2 3 4 5 6 9 + COMMAND=restart + case "$COMMAND" in + ''['' 1 -ne 1 '']'' + do_initialize + export LC_ALL=C + LC_ALL=C + umask 177 + PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin + terminator=startup_error + version= + IPTABLES= + FW= + SUBSYSLOCK= + STATEDIR= + ALLOWRELATED=Yes + LOGRATE= + LOGBURST= + LOGPARMS= + LOGLIMIT= + ADD_IP_ALIASES= + ADD_SNAT_ALIASES= + TC_ENABLED= + BLACKLIST_DISPOSITION= + BLACKLIST_LOGLEVEL= + CLAMPMSS= + ROUTE_FILTER= + LOG_MARTIANS= + DETECT_DNAT_IPADDRS= + MUTEX_TIME...
2005 Feb 01
4
Shorewall problem
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