forked from extern/shorewall_code
b66929a65e
1) Elimination of the "shorewall monitor" command. 2) The /etc/shorewall/ipsec and /etc/shorewall/zones file are combined into a single /etc/shorewall/zones file. This is done in an upwardly-compatible way so that current users can continue to use their existing files. 3) Support has been added for the arp_ignore interface option. 4) DROPINVALID has been removed from shorewall.conf. Behavior is as if DROPINVALID=No was specified. 5) The 'nobogons' option and BOGON_LOG_LEVEL are removed. 6) Error and warning messages have been made easier to spot by using capitalization (e.g., ERROR: and WARNING:). 7) The /etc/shorewall/policy file now contains a new connection policy and a policy for ESTABLISHED packets. Useful for users of snort-inline who want to pass all packets to the QUEUE target. 8) A new 'critical' option has been added to /etc/shorewall/routestopped. Shorewall insures communication between the firewall and 'critical' hosts throughout start, restart, stop and clear. Useful for diskless firewall's with NFS-mounted file systems, LDAP servers, Crossbow, etc. 9) Macros. Macros are very similar to actions but are easier to use, allow parameter substitution and are more efficient. Almost all of the standard actions have been converted to macros in the EXPERIMENTAL branch. 10) The default value of ADD_IP_ALIASES in shorewall.conf is changed to No. 11) If you have 'make' installed on your firewall, then when you use the '-f' option to 'shorewall start' (as happens when you reboot), if your /etc/shorewall/ directory contains files that were modified after Shorewall was last restarted then Shorewall is started using the config files rather than using the saved configuration. git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@2409 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
33 lines
1.2 KiB
Plaintext
33 lines
1.2 KiB
Plaintext
#
|
|
# Shorewall 2.6 /etc/shorewall/actions
|
|
#
|
|
# This file allows you to define new ACTIONS for use in rules
|
|
# (/etc/shorewall/rules). You define the iptables rules to
|
|
# be performed in an ACTION in
|
|
# /etc/shorewall/action.<action-name>.
|
|
#
|
|
# ACTION names should begin with an upper-case letter to
|
|
# distinguish them from Shorewall-generated chain names and
|
|
# they must meet the requirements of a Netfilter chain. If
|
|
# you intend to log from the action then the name must be
|
|
# no longer than 11 character in length. Names must also
|
|
# meet the requirements for a Bourne Shell identifier (must
|
|
# begin with a letter and be composed of letters, digits and
|
|
# underscore characters).
|
|
#
|
|
# If you follow the action name with ":DROP", ":REJECT" or
|
|
# :ACCEPT then the action will be taken before a DROP, REJECT or
|
|
# ACCEPT policy respectively is enforced. If you specify ":DROP",
|
|
# ":REJECT" or ":ACCEPT" on more than one action then only the
|
|
# last such action will be taken.
|
|
#
|
|
# If you specify ":DROP", ":REJECT" or ":ACCEPT" on a line by
|
|
# itself, the associated policy will have no common action.
|
|
#
|
|
# Please see http://shorewall.net/Actions.html for additional
|
|
# information.
|
|
#
|
|
#ACTION
|
|
|
|
#LAST LINE - ADD YOUR ENTRIES ABOVE THIS ONE - DO NOT REMOVE
|