From 3d6746412c9dbd8b6d08d132b273754543a640cd Mon Sep 17 00:00:00 2001 From: mhnoyes Date: Sun, 28 Dec 2003 15:58:02 +0000 Subject: [PATCH] fixed quotes, add CVS Id git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@991 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb --- Shorewall-docs/User_defined_Actions.xml | 45 ++++++++++++------------- 1 file changed, 21 insertions(+), 24 deletions(-) diff --git a/Shorewall-docs/User_defined_Actions.xml b/Shorewall-docs/User_defined_Actions.xml index 25bd955c2..8130b7736 100755 --- a/Shorewall-docs/User_defined_Actions.xml +++ b/Shorewall-docs/User_defined_Actions.xml @@ -2,7 +2,7 @@
- + User-defined Actions @@ -56,8 +56,8 @@ Once you have defined your new action name (ActionName), then copy /etc/shorewall/action.template to /etc/shorewall/action.ActionName (for - example, if your new action name is "Foo" then copy - /etc/shorewall/action.template to /etc/shorewall/action.foo). + example, if your new action name is Foo then copy + /etc/shorewall/action.template to /etc/shorewall/action.foo). @@ -71,24 +71,24 @@ TARGET - Must be ACCEPT, DROP, REJECT, LOG, QUEUE or <action> where <action> is a previously-defined action. - The TARGET may optionally be followed by a colon (":") and a - syslog log level (e.g, REJECT:info or ACCEPT:debugging). This causes the - packet to be logged at the specified level. You may also specify ULOG - (must be in upper case) as a log level.This will log to the ULOG target - for routing to a separate log through use of ulogd + The TARGET may optionally be followed by a colon (:) and + a syslog log level (e.g, REJECT:info or ACCEPT:debugging). This causes + the packet to be logged at the specified level. You may also specify + ULOG (must be in upper case) as a log level.This will log to the ULOG + target for routing to a separate log through use of ulogd (http://www.gnumonks.org/projects/ulogd). SOURCE - Source hosts to which the rule applies. A comma-separated list of subnets and/or hosts. Hosts may be specified by IP or MAC - address; mac addresses must begin with "~" and must use - "-" as a separator. + address; mac addresses must begin with ~ and must use + - as a separator. Alternatively, clients may be specified by interface name. For example, eth1 specifies a client that communicates with the firewall - system through eth1. This may be optionally followed by another colon - (":") and an IP/MAC/subnet address as described above (e.g., + system through eth1. This may be optionally followed by another colon (:) + and an IP/MAC/subnet address as described above (e.g., eth1:192.168.1.5). @@ -97,19 +97,18 @@ MAC addresses are not allowed. Unlike in the SOURCE column, you may specify a range of up to 256 - IP addresses using the syntax <first ip>-<last ip>. - + IP addresses using the syntax <first ip>-<last ip>. - PROTO - Protocol - Must be "tcp", "udp", - "icmp", a number, or "all". + PROTO - Protocol - Must be tcp, udp, + icmp, a number, or all. DEST PORT(S) - Destination Ports. A comma-separated list of Port names (from /etc/services), port numbers or port ranges; if the protocol - is "icmp", this column is interpreted as the destination + is icmp, this column is interpreted as the destination icmp-type(s). A port range is expressed as <low port>:<high @@ -117,7 +116,7 @@ This column is ignored if PROTOCOL = all but must be entered if any of the following ields are supplied. In that case, it is suggested - that this field contain "-". + that this field contain -. If your kernel contains multi-port match support, then only a single Netfilter rule will be generated if in this list and the CLIENT @@ -141,10 +140,10 @@ this column: <rate>/<interval>[:<burst>]where - <rate> is the number of connections per <interval> - ("sec" or "min") and <burst> is the largest - burst permitted. If no <burst> is given, a value of 5 is - assumed. There may be no whitespace embedded in the specification. + <rate> is the number of connections per <interval> (sec + or min) and <burst> is the largest burst + permitted. If no <burst> is given, a value of 5 is assumed. + There may be no whitespace embedded in the specification. Example: 10/sec:20 @@ -157,6 +156,4 @@ LogAndAccept/etc/shorewall/action.LogAndAccept LOG:info ACCEPT - -
\ No newline at end of file