search for: rejnotsyn

...ples. 2) Shorewall previously used root''s default umask which could cause files in /var/lib/shorewall to be world-readable. Shorewall now uses umask 0177. 3) In log messages produced by logging a built-in action, the packet disposition was displayed incorrectly. Example: rejNotSyn:ULOG all all tcp produces the log message: Feb 12 23:57:08 server Shorewall:rejNotSyn:ULOG: ... rather than Feb 12 23:57:08 server Shorewall:rejNotSyn:REJECT: ... 4) The comments regarding built-in actions in /usr/share/shorewall/actions.std h...

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

...- ADD YOUR ENTRIES ABOVE THIS LINE -- DO NOT REMOVE'' + read first rest + cut -d# -f1 + grep -v ''^[[:space:]]*$'' + echo ''Pre-processing Actions...'' Pre-processing Actions... + process_actions1 + ACTIONS=''dropBcast allowBcast dropNonSyn dropNotSyn rejNotSyn dropInvalid allowInvalid allowinUPnP allowoutUPnP forwardUPnP'' + USEDACTIONS= + strip_file actions + local fname + ''['' 1 = 1 '']'' ++ find_file actions ++ local saveifs= directory ++ case $1 in ++ ''['' -n '''' -a -f /action...

This minor release includes some bugfix back-ports from 2.2. 1) Invoking the ''rejNotSyn'' action results in an error at startup. 2) The UDP and TCP port numbers in /usr/share/shorewall/action.AllowPCA were reversed. 3) If a zone is defined in /etc/shorewall/hosts using <interface>:!<network> in the HOSTS column then startup errors occur on "shorewa...