search for: my_mutex_off

...ng Shorewall, on a router with 4 NIC, seems running ok. Next day, when connecting from clients, (MS) we keep getting ip conflict for non-conflicting ip addresses. Any help is appreciated. Detals of Startup: + shift + nolock= + ''['' 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...

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

...inated ========================================================== When I follow the tracing instruction, I get the following # tail /tmp/trace ++ ''['' -f /etc/shorewall/stopped '']'' ++ logger ''Shorewall Stopped'' ++ rm -rf /tmp/shorewall-31374 ++ my_mutex_off ++ ''['' -n Yes '']'' ++ mutex_off ++ rm -f /var/lib/shorewall/lock ++ have_mutex= ++ kill 31374 ++ exit 2 - I have all the mensioned modules loaded. Ay help will be appreciated. Thanks.

...;' 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= + ''['' -n /tmp/shorewall.pS4135 '']'' + rm -rf /tmp/shorewall.pS4135 + ''['' -n /var/lib/shorewall/shorewall.mX4232 '']'' +...

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

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

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

...y hints on how to avoid this behaviour, I''ll be very gratefull. ________________________ Eduardo Ferreira Icatu Holding S.A. Supervisor de TI (5521) 3804-8606 -------------- next part -------------- + shift + nolock= + ''['' 1 -gt 1 '']'' + trap ''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= +...