| 1 |
<h2>Rule options for iptables policy rules</h2> |
| 2 |
|
| 3 |
<a name="general"> |
| 4 |
<h2>Tab General</h2> |
| 5 |
|
| 6 |
<h3>Assume firewall is part of 'any'</h3> |
| 7 |
|
| 8 |
<p> |
| 9 |
This option overrides global setting of the option with the same |
| 10 |
name in the firewall object "advanced" settings dialog. |
| 11 |
</p> |
| 12 |
|
| 13 |
<p> |
| 14 |
On some firewall platforms there is a difference in the |
| 15 |
configuration command used to control access through the firewall |
| 16 |
versus the command that controls access to the firewall itself. For |
| 17 |
example, in iptables, packets headed for the firewall machine should |
| 18 |
be inspected in the INPUT chain, while packets going through the |
| 19 |
firewall are inspected in the FORWARD chain. If this option is ON, |
| 20 |
the compiler generates code for both FORWARD and INPUT chains if it |
| 21 |
sees ’any’ as the destination of the policy rule. In other words, it |
| 22 |
assumes that the firewall is part of ’any’, and packets may either |
| 23 |
go to or through the firewall. If this option is off, the compiler |
| 24 |
only generates code for the FORWARD chain. Compiler treats ’any’ in |
| 25 |
the source of the rule in a similar way, generating code either for |
| 26 |
the OUTPUT and FORWARD, or only for the FORWARD chain. |
| 27 |
</p> |
| 28 |
|
| 29 |
<h3>Stateless rule</h3> |
| 30 |
<p> |
| 31 |
Firewall Builder always uses stateful packet inspection if it is |
| 32 |
available in the target firewall. In case of iptables, this means it |
| 33 |
always uses module "state" by adding the following parameters to the |
| 34 |
generated rules: "-m state --state NEW". It also adds a rule to |
| 35 |
match states "ESTABLISHED,RELATED" on top of the policy. However, |
| 36 |
sometimes it might be desirable to create a rule without state |
| 37 |
matching. Checking this checkbox on makes the rule stateless, which |
| 38 |
means parameters "-m state --state NEW" will not be added. |
| 39 |
</p> |
| 40 |
|
| 41 |
<p> |
| 42 |
Rules with action Deny are always stateless by default and do not get |
| 43 |
the "-m state --state NEW" parameters, although you can make them |
| 44 |
stateful by checking this checkbox. |
| 45 |
</p> |
| 46 |
|
| 47 |
<a name="logging"> |
| 48 |
<hr> |
| 49 |
<h2>Tab Logging</h2> |
| 50 |
|
| 51 |
<p> |
| 52 |
Options in this tab override the same options configured globally in |
| 53 |
the firewall object "advanced" settings dialog. |
| 54 |
</p> |
| 55 |
|
| 56 |
|
| 57 |
<h3>Log prefix</h3> |
| 58 |
|
| 59 |
<p> |
| 60 |
Log records will be prefixed with a string you enter in this option. |
| 61 |
Firewall Builder supports the following macros in the log prefix that |
| 62 |
are expanded at the compile time: |
| 63 |
</p> |
| 64 |
|
| 65 |
<p> |
| 66 |
<ul> |
| 67 |
<li>%N rule number in the GUI. </li> |
| 68 |
<li>%A rule action </li> |
| 69 |
<li>%I interface the rule is associated with </li> |
| 70 |
<li>%C (iptables only) iptables chain that this rule generated |
| 71 |
code for. </li> |
| 72 |
</ul> |
| 73 |
</p> |
| 74 |
|
| 75 |
|
| 76 |
<h3>Log level</h3> |
| 77 |
|
| 78 |
<p> |
| 79 |
Choose one of the standard syslog log levels for the "--log-level" |
| 80 |
option of the LOG iptables target. |
| 81 |
</p> |
| 82 |
|
| 83 |
|
| 84 |
<h3>Netlink group</h3> |
| 85 |
|
| 86 |
<p> |
| 87 |
This specifies the netlink group (1-32) to which the packet is sent. |
| 88 |
Used to add "--ulog-nlgroup" parameter if ULOG logging is chosen in |
| 89 |
the firewall settings dialog, tab "Logging". |
| 90 |
</p> |
| 91 |
|
| 92 |
|
| 93 |
<a name="limit"> |
| 94 |
<hr> |
| 95 |
<h2>Tab limit</h2> |
| 96 |
|
| 97 |
<p> |
| 98 |
Options in this tab are used to configure parameters for the module |
| 99 |
"limit". |
| 100 |
</p> |
| 101 |
|
| 102 |
<h3>Rate, burst</h3> |
| 103 |
|
| 104 |
<p> |
| 105 |
These translate into " --limit rate" and "--limit-burst number" |
| 106 |
options for the module "limit". If rate is set to 0 (the default), |
| 107 |
parameter "-m limit --limit rate" is not added to the generated |
| 108 |
iptables command. |
| 109 |
</p> |
| 110 |
|
| 111 |
|
| 112 |
<a name="connlimit"> |
| 113 |
<hr> |
| 114 |
<h2>Tab connlimit</h2> |
| 115 |
|
| 116 |
<p> |
| 117 |
Options in this tab are used to configure parameters for the module |
| 118 |
"connlimit". |
| 119 |
</p> |
| 120 |
|
| 121 |
<h3>Number of allowed connections per client host</h3> |
| 122 |
|
| 123 |
<p> |
| 124 |
If this option is set to non-zero value, it adds the following |
| 125 |
clause to the generated iptables command: "-m |
| 126 |
connlimit --connlimit-above ". |
| 127 |
</p> |
| 128 |
|
| 129 |
<h3>...per network with netmask of ... </h3> |
| 130 |
|
| 131 |
<p> |
| 132 |
If this option is set to non-zero value, it adds the following |
| 133 |
to the generated iptables command: " --connlimit-mask mask". |
| 134 |
</p> |
| 135 |
|
| 136 |
<p> |
| 137 |
Note that <b>conntrack</b> module must be compiled into the kernel |
| 138 |
and iptables in order for these options to work on the firewall. |
| 139 |
</p> |
| 140 |
|
| 141 |
|
| 142 |
<a name="hashlimit"> |
| 143 |
<hr> |
| 144 |
<h2>Tab hashlimit</h2> |
| 145 |
|
| 146 |
<p> |
| 147 |
Options in this tab are used to configure parameters for the module |
| 148 |
"hashlimit". Please see man page for iptables, section "hashlimit" |
| 149 |
for the explanation of all parameters it accepts. Note that on some |
| 150 |
older Linux systems this module used to be called |
| 151 |
"dstlimit". Checking corresponding checkbox in this dialog causes |
| 152 |
compiler to generate parameter as "-m dstlimit" instead of "-m |
| 153 |
hashlimit". |
| 154 |
</p> |
| 155 |
|
| 156 |
|
| 157 |
|