shorewall-netmap man page on Mageia

Man page or keyword search:  
man Server   17783 pages
apropos Keyword Search (all sections)
Output format
Mageia logo
[printable version]

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

NAME
       netmap - Shorewall NETMAP definition file

SYNOPSIS
       /etc/shorewall/netmap

DESCRIPTION
       This file is used to map addresses in one network to corresponding
       addresses in a second network.

	   Warning
	   To use this file, your kernel and iptables must have NETMAP support
	   included.

       The columns in the file are as follows (where the column name is
       followed by a different name in parentheses, the different name is used
       in the alternate specification syntax).

       TYPE - {DNAT|SNAT}[:{P|O|T}]
	   Must be DNAT or SNAT; beginning with Shorewall 4.4.23, may be
	   optionally followed by :P, :O or :T to perform stateless NAT.
	   Stateless NAT requires Rawpost Table support in your kernel and
	   iptables (see the output of shorewall show capabilities).

	   If DNAT or DNAT:P, traffic entering INTERFACE and addressed to NET1
	   has its destination address rewritten to the corresponding address
	   in NET2.

	   If SNAT or SNAT:T, traffic leaving INTERFACE with a source address
	   in NET1 has it's source address rewritten to the corresponding
	   address in NET2.

	   If DNAT:O, traffic originating on the firewall and leaving via
	   INTERFACE and addressed to NET1 has its destination address
	   rewritten to the corresponding address in NET2.

	   If DNAT:P, traffic entering via INTERFACE and addressed to NET1 has
	   its destination address rewritten to the corresponding address in
	   NET2.

	   If SNAT:P, traffic entering via INTERFACE with a destination
	   address in NET1 has it's source address rewritten to the
	   corresponding address in NET2.

	   If SNAT:O, traffic originating on the firewall and leaving via
	   INTERFACE with a source address in NET1 has it's source address
	   rewritten to the corresponding address in NET2.

       NET1 - network-address
	   Network in CIDR format (e.g., 192.168.1.0/24). Beginning with
	   Shorewall 4.4.24, exclusion[1] is supported.

       INTERFACE - interface
	   The name of a network interface. The interface must be defined in
	   shorewall-interfaces[2](5). Shorewall allows loose matches to
	   wildcard entries in shorewall-interfaces[2](5). For example, ppp0
	   in this file will match a shorewall-interfaces[2](8) entry that
	   defines ppp+.

       NET2 - network-address
	   Network in CIDR format

       NET3 (Optional) - network-address
	   Added in Shorewall 4.4.11. If specified, qualifies INTERFACE. It
	   specifies a SOURCE network for DNAT rules and a DESTINATION network
	   for SNAT rules.

       PROTO - protocol-number-or-name
	   Optional -- added in Shorewall 4.4.23.2. Only packets specifying
	   this protocol will have their IP header modified.

       DEST PORT(S) (dport) - port-number-or-name-list
	   Optional - added in Shorewall 4.4.23.2. Destination Ports. A
	   comma-separated list of Port names (from services(5)), port numbers
	   or port ranges; if the protocol is icmp, this column is interpreted
	   as the destination icmp-type(s). ICMP types may be specified as a
	   numeric type, a numeric type and code separated by a slash (e.g.,
	   3/4), or a typename. See
	   http://www.shorewall.net/configuration_file_basics.htm#ICMP.

	   If the protocol is ipp2p, this column is interpreted as an ipp2p
	   option without the leading "--" (example bit for bit-torrent). If
	   no PORT is given, ipp2p is assumed.

	   An entry in this field requires that the PROTO column specify icmp
	   (1), tcp (6), udp (17), sctp (132) or udplite (136). Use '-' if any
	   of the following field is supplied.

       SOURCE PORT(S) (sport) - port-number-or-name-list
	   Optional -- added in Shorewall 4.4.23.2. Source port(s). If
	   omitted, any source port is acceptable. Specified as a
	   comma-separated list of port names, port numbers or port ranges.

	   An entry in this field requires that the PROTO column specify tcp
	   (6), udp (17), sctp (132) or udplite (136). Use '-' if any of the
	   following fields is supplied.

FILES
       /etc/shorewall/netmap

SEE ALSO
       http://shorewall.net/netmap.html

       http://shorewall.net/configuration_file_basics.htm#Pairs

       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-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. exclusion
	   http://www.shorewall.net/manpages/shorewall-exclusion.html

	2. shorewall-interfaces
	   http://www.shorewall.net/manpages/shorewall-interfaces.html

[FIXME: source]			  12/19/2013		   SHOREWALL-NETMAP(5)
[top]

List of man pages available for Mageia

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net