Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

shorewall-ipsets(5) [debian man page]

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)

Check Out this Related Man Page

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

NAME

       modules - Shorewall file

SYNOPSIS

       /usr/share/shorewall/modules

       /usr/share/shorewall/helpers

DESCRIPTION

       These files specify which kernel modules Shorewall will load before trying to determine your iptables/kernel's capabilities.

       The modules file is used when LOAD_HELPERS_ONLY=No in shorewall.conf[1](8); the helpers file is used when LOAD_HELPERS_ONLY=Yes

       Each record in the files has the following format:

       loadmodule modulename [moduleoption...]

       The modulename names a kernel module (without suffix). Shorewall will search for modules based on your MODULESDIR and MODULE_SUFFIX
       settings in shorewall.conf[1](8). The moduleoptions are passed to modprobe (if installed) or to insmod.

       The /usr/share/shorewall/modules file contains a large number of modules. Users are encouraged to copy the file to /etc/shorewall/modules
       and modify the copy to load only the modules required or to use LOAD_HELPERS_ONLY=Yes..if n .sp
	   Note
	   If you build monolithic kernels and have not installed module-init-tools, then create an empty /etc/shorewall/modules file; that will
	   prevent Shorewall from trying to load modules at all.

EXAMPLE

       loadmodule ip_conntrack_ftp ports=21,221

FILES

       /usr/share/shorewall/modules

       /usr/share/shorewall/helpers

       /etc/shorewall/modules

       /etc/shorewall/helpers

SEE ALSO

       shorewall(8), shorewall-accounting(5), shorewall-actions(5), shorewall-blacklist(5), shorewall-hosts(5), shorewall_interfaces(5),
       shorewall-ipsets(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.conf
	   http://www.shorewall.net/manpages/shorewall.conf.html

[FIXME: source] 						    06/28/2012						      SHOREWALL-MODULES(5)
Man Page