shorewall6-ipsets(5) [debian man page]

SHOREWALL-IPSETS(5)						  [FIXME: manual]					       SHOREWALL-IPSETS(5)

NAME

       ipsets - Specifying the name if an ipset in Shorewall6 configuration files

SYNOPSIS

       +ipsetname

       +ipsetname[flag,...]

       +[ipsetname,...]

DESCRIPTION

       Note: In the above syntax descriptions, the square brackets ("[]") are to be taken literally rather than as meta-characters.

       In most places where a network address may be entered, an ipset may be substituted. Set names must be prefixed by the character "+", must
       start with a letter and may be composed of alphanumeric characters, "-" and "_".

       Whether the set is matched against the packet source or destination is determined by which column the set name appears (SOURCE or DEST).
       For those set types that specify a tupple, two alternative syntaxes are available:
	   [number] - Indicates that 'src' or
		 'dst' should repleated number times. Example: myset[2].
	   [flag,...] where
		 flag is src or
		 dst. Example: myset[src,dst].

       In a SOURCE column, the following pairs are equivalent:

       o   +myset[2] and +myset[src,src]

       In a DEST column, the following paris are equivalent:

       o   +myset[2] and +myset[dst,dst]

       Beginning with Shorewall 4.4.14, multiple source or destination matches may be specified by enclosing the set names within +[...]. The set
       names need not be prefixed with '+'. When such a list of sets is specified, matching packets must match all of the listed sets.

       For information about set lists and exclusion, see shorewall-exclusion[1] (5).

EXAMPLES

       +myset

       +myset[src]

       +myset[2]

       +[myset1,myset2[dst]]

FILES

       /etc/shorewall6/accounting

       /etc/shorewall6/blacklist

       /etc/shorewall6/hosts -- Note: Multiple matches enclosed in +[...] may not be used in this file.

       /etc/shorewall6/maclist -- Note: Multiple matches enclosed in +[...] may not be used in this file.

       /etc/shorewall6/rules

       /etc/shorewall6/secmarks

       /etc/shorewall6/tcrules

SEE ALSO

       shorewall6(8), shorewall6-actions(5), shorewall6-blacklist(5), shorewall6-hosts(5), shorewall6-interfaces(5), shorewall6-maclist(5),
       shoewall6-netmap(5),shorewall6-params(5), shorewall6-policy(5), shorewall6-providers(5), shorewall6-rtrules(5), shorewall6-routestopped(5),
       shorewall6-rules(5), shorewall6.conf(5), shorewall6-secmarks(5), shorewall6-tcclasses(5), shorewall6-tcdevices(5), shorewall6-tcrules(5),
       shorewall6-tos(5), shorewall6-tunnels(5), shorewall6-zones(5)

NOTES

	1. shorewall-exclusion
	   http://www.shorewall.net/manpages6/shorewall-exclusion.html

[FIXME: source] 						    06/28/2012						       SHOREWALL-IPSETS(5)

SHOREWALL-IPSETS(5)						  [FIXME: manual]					       SHOREWALL-IPSETS(5)

NAME

       ipsets - Specifying the name if an ipset in Shorewall configuration files

SYNOPSIS

       +ipsetname

       +ipsetname[flag,...]

       +[ipsetname,...]

DESCRIPTION

       Note: In the above syntax descriptions, the square brackets ("[]") are to be taken literally rather than as meta-characters.

       In most places where a network address may be entered, an ipset may be substituted. Set names must be prefixed by the character "+", must
       start with a letter and may be composed of alphanumeric characters, "-" and "_".

       Whether the set is matched against the packet source or destination is determined by which column the set name appears (SOURCE or DEST).
       For those set types that specify a tupple, two alternative syntaxes are available:
	   [number] - Indicates that 'src' or
		 'dst' should repleated number times. Example: myset[2].
	   [flag,...] where
		 flag is src or
		 dst. Example: myset[src,dst].

       In a SOURCE column, the following pairs are equivalent:

       o   +myset[2] and +myset[src,src]

       In a DEST column, the following paris are equivalent:

       o   +myset[2] and +myset[dst,dst]

       Beginning with Shorewall 4.4.14, multiple source or destination matches may be specified by enclosing the set names within +[...]. The set
       names need not be prefixed with '+'. When such a list of sets is specified, matching packets must match all of the listed sets.

       For information about set lists and exclusion, see shorewall-exclusion[1] (5).

EXAMPLES

       +myset

       +myset[src]

       +myset[2]

       +[myset1,myset2[dst]]

FILES

       /etc/shorewall/accounting

       /etc/shorewall/blacklist

       /etc/shorewall/hosts -- Note: Multiple matches enclosed in +[...] may not be used in this file.

       /etc/shorewall/maclist -- Note: Multiple matches enclosed in +[...] may not be used in this file.

       /etc/shorewall/masq

       /etc/shorewall/rules

       /etc/shorewall/secmarks

       /etc/shorewall/tcrules

SEE ALSO

       shorewall(8), shorewall-accounting(5), shorewall-actions(5), shorewall-blacklist(5), shorewall-hosts(5), shorewall_interfaces(5),
       shorewall-maclist(5), shorewall-masq(5), shorewall-nat(5), shorewall-netmap(5), shorewall-params(5), shorewall-policy(5),
       shorewall-providers(5), shorewall-proxyarp(5), shorewall-rtrules(5), shorewall-routestopped(5), shorewall-rules(5), shorewall.conf(5),
       shorewall-secmarks(5), shorewall-tcclasses(5), shorewall-tcdevices(5), shorewall-tcrules(5), shorewall-tos(5), shorewall-tunnels(5),
       shorewall-zones(5)

NOTES

	1. shorewall-exclusion
	   http://www.shorewall.net/manpages/shorewall-exclusion.html

[FIXME: source] 						    06/28/2012						       SHOREWALL-IPSETS(5)