administration tool for IPv4 packet filtering and NAT

-t, --table table
       This option specifies the packet matching table which the  command  should  operate  on.   If  the
       kernel  is  configured  with  automatic  module  loading,  an  attempt  will  be  made to load the
       appropriate module for that table if it is not already there.

              The tables are as follows:

              filter:
                  This is the default table (if no -t option is passed). It contains the built-in  chains  INPUT
                  (for  packets  destined to local sockets), FORWARD (for packets being routed through the box),
                  and OUTPUT (for locally-generated packets).

              nat:
                  This table is consulted when a packet that  creates  a  new  connection  is  encountered.   It
                  consists of three built-ins: PREROUTING (for altering packets as soon as they come in), OUTPUT
                  (for altering locally-generated packets before routing), and POSTROUTING (for altering packets
                  as they are about to go out).

              mangle:
                  This table is used for specialized packet alteration.  Until kernel 2.4.17 it had two built-in
                  chains: PREROUTING (for altering incoming packets before routing)  and  OUTPUT  (for  altering
                  locally-generated  packets  before routing).  Since kernel 2.4.18, three other built-in chains
                  are also supported: INPUT (for packets coming into the  box  itself),  FORWARD  (for  altering
                  packets being routed through the box), and POSTROUTING (for altering packets as they are about
                  to go out).

              raw:
                  This table is used mainly for configuring exemptions from connection tracking  in  combination
                  with the NOTRACK target.  It registers at the netfilter hooks with higher priority and is thus
                  called before ip_conntrack, or any other  IP  tables.   It  provides  the  following  built-in
                  chains:  PREROUTING  (for  packets  arriving  via  any  network interface) OUTPUT (for packets
                  generated by local processes)

              security:
                  This table is used for Mandatory Access Control (MAC) networking rules, such as those  enabled
                  by  the  SECMARK  and  CONNSECMARK  targets.  Mandatory Access Control is implemented by Linux
                  Security Modules such as SELinux.  The security  table  is  called  after  the  filter  table,
                  allowing  any  Discretionary  Access  Control  (DAC)  rules in the filter table to take effect
                  before MAC rules.  This table provides the  following  built-in  chains:  INPUT  (for  packets
                  coming  into  the box itself), OUTPUT (for altering locally-generated packets before routing),
                  and FORWARD (for altering packets being routed through the box).

-A, --append chain rule-specification
       Append one or more rules to the end of the selected chain.  When  the  source  and/or  destination
       names  resolve  to  more  than  one  address,  a  rule  will  be  added  for each possible address
       combination.

[!] -o, --out-interface name
       Name of an interface via which a packet is going to be sent (for  packets  entering  the  FORWARD,
       OUTPUT  and  POSTROUTING  chains).   When  the "!" argument is used before the interface name, the
       sense is inverted.  If the interface name ends in a "+", then any interface which begins with this
       name will match.  If this option is omitted, any interface name will match.

-j, --jump target
       This  specifies the target of the rule; i.e., what to do if the packet matches it.  The target can
       be a user-defined chain (other than the one this rule is in), one of the special  builtin  targets
       which  decide the fate of the packet immediately, or an extension (see EXTENSIONS below).  If this
       option is omitted in a rule (and -g is not used), then matching the rule will have  no  effect  on
       the packet's fate, but the counters on the rule will be incremented.

--to offset
       Set the offset up to which should be scanned. That is, byte offset-1 (counting from 0) is the last
       one that is scanned.  If not passed, default is the packet size.