Yasuyuki Kozakai | 9fb9cbb | 2005-11-09 16:38:16 -0800 | [diff] [blame] | 1 | menu "Core Netfilter Configuration" |
| 2 | depends on NET && NETFILTER |
| 3 | |
Harald Welte | f9e815b | 2005-08-09 19:30:24 -0700 | [diff] [blame] | 4 | config NETFILTER_NETLINK |
| 5 | tristate "Netfilter netlink interface" |
| 6 | help |
| 7 | If this option is enabled, the kernel will include support |
| 8 | for the new netfilter netlink interface. |
Harald Welte | 7af4cc3 | 2005-08-09 19:44:15 -0700 | [diff] [blame] | 9 | |
| 10 | config NETFILTER_NETLINK_QUEUE |
| 11 | tristate "Netfilter NFQUEUE over NFNETLINK interface" |
| 12 | depends on NETFILTER_NETLINK |
| 13 | help |
Thomas Vögtle | 50b521a | 2006-03-22 13:53:48 -0800 | [diff] [blame] | 14 | If this option is enabled, the kernel will include support |
Harald Welte | 7af4cc3 | 2005-08-09 19:44:15 -0700 | [diff] [blame] | 15 | for queueing packets via NFNETLINK. |
| 16 | |
Harald Welte | 0597f26 | 2005-08-09 19:58:39 -0700 | [diff] [blame] | 17 | config NETFILTER_NETLINK_LOG |
| 18 | tristate "Netfilter LOG over NFNETLINK interface" |
| 19 | depends on NETFILTER_NETLINK |
| 20 | help |
| 21 | If this option is enabled, the kernel will include support |
| 22 | for logging packets via NFNETLINK. |
| 23 | |
| 24 | This obsoletes the existing ipt_ULOG and ebg_ulog mechanisms, |
| 25 | and is also scheduled to replace the old syslog-based ipt_LOG |
| 26 | and ip6t_LOG modules. |
| 27 | |
Patrick McHardy | b321e14 | 2006-12-02 22:05:46 -0800 | [diff] [blame] | 28 | config NF_CONNTRACK_ENABLED |
| 29 | tristate "Netfilter connection tracking support" |
| 30 | help |
Yasuyuki Kozakai | 9fb9cbb | 2005-11-09 16:38:16 -0800 | [diff] [blame] | 31 | Connection tracking keeps a record of what packets have passed |
| 32 | through your machine, in order to figure out how they are related |
| 33 | into connections. |
| 34 | |
Patrick McHardy | b321e14 | 2006-12-02 22:05:46 -0800 | [diff] [blame] | 35 | This is required to do Masquerading or other kinds of Network |
| 36 | Address Translation (except for Fast NAT). It can also be used to |
| 37 | enhance packet filtering (see `Connection state match support' |
| 38 | below). |
| 39 | |
| 40 | To compile it as a module, choose M here. If unsure, say N. |
| 41 | |
| 42 | choice |
| 43 | prompt "Netfilter connection tracking support" |
| 44 | depends on NF_CONNTRACK_ENABLED |
| 45 | |
| 46 | config NF_CONNTRACK_SUPPORT |
| 47 | bool "Layer 3 Independent Connection tracking (EXPERIMENTAL)" |
| 48 | depends on EXPERIMENTAL |
| 49 | help |
Yasuyuki Kozakai | 9fb9cbb | 2005-11-09 16:38:16 -0800 | [diff] [blame] | 50 | Layer 3 independent connection tracking is experimental scheme |
| 51 | which generalize ip_conntrack to support other layer 3 protocols. |
| 52 | |
Patrick McHardy | b321e14 | 2006-12-02 22:05:46 -0800 | [diff] [blame] | 53 | This is required to do Masquerading or other kinds of Network |
| 54 | Address Translation (except for Fast NAT). It can also be used to |
| 55 | enhance packet filtering (see `Connection state match support' |
| 56 | below). |
| 57 | |
| 58 | config IP_NF_CONNTRACK_SUPPORT |
| 59 | bool "Layer 3 Dependent Connection tracking" |
| 60 | help |
| 61 | The old, Layer 3 dependent ip_conntrack subsystem of netfilter. |
| 62 | |
| 63 | This is required to do Masquerading or other kinds of Network |
| 64 | Address Translation (except for Fast NAT). It can also be used to |
| 65 | enhance packet filtering (see `Connection state match support' |
| 66 | below). |
| 67 | |
| 68 | endchoice |
| 69 | |
| 70 | config NF_CONNTRACK |
| 71 | tristate |
| 72 | default m if NF_CONNTRACK_SUPPORT && NF_CONNTRACK_ENABLED=m |
| 73 | default y if NF_CONNTRACK_SUPPORT && NF_CONNTRACK_ENABLED=y |
| 74 | |
| 75 | config IP_NF_CONNTRACK |
| 76 | tristate |
| 77 | default m if IP_NF_CONNTRACK_SUPPORT && NF_CONNTRACK_ENABLED=m |
| 78 | default y if IP_NF_CONNTRACK_SUPPORT && NF_CONNTRACK_ENABLED=y |
Yasuyuki Kozakai | 9fb9cbb | 2005-11-09 16:38:16 -0800 | [diff] [blame] | 79 | |
| 80 | config NF_CT_ACCT |
| 81 | bool "Connection tracking flow accounting" |
| 82 | depends on NF_CONNTRACK |
| 83 | help |
| 84 | If this option is enabled, the connection tracking code will |
| 85 | keep per-flow packet and byte counters. |
| 86 | |
| 87 | Those counters can be used for flow-based accounting or the |
| 88 | `connbytes' match. |
| 89 | |
| 90 | If unsure, say `N'. |
| 91 | |
| 92 | config NF_CONNTRACK_MARK |
| 93 | bool 'Connection mark tracking support' |
| 94 | depends on NF_CONNTRACK |
| 95 | help |
| 96 | This option enables support for connection marks, used by the |
| 97 | `CONNMARK' target and `connmark' match. Similar to the mark value |
| 98 | of packets, but this mark value is kept in the conntrack session |
| 99 | instead of the individual packets. |
| 100 | |
James Morris | 7c9728c | 2006-06-09 00:31:46 -0700 | [diff] [blame] | 101 | config NF_CONNTRACK_SECMARK |
| 102 | bool 'Connection tracking security mark support' |
| 103 | depends on NF_CONNTRACK && NETWORK_SECMARK |
| 104 | help |
| 105 | This option enables security markings to be applied to |
| 106 | connections. Typically they are copied to connections from |
| 107 | packets using the CONNSECMARK target and copied back from |
| 108 | connections to packets with the same target, with the packets |
| 109 | being originally labeled via SECMARK. |
| 110 | |
| 111 | If unsure, say 'N'. |
| 112 | |
Yasuyuki Kozakai | 9fb9cbb | 2005-11-09 16:38:16 -0800 | [diff] [blame] | 113 | config NF_CONNTRACK_EVENTS |
Patrick McHardy | a795756 | 2005-12-05 13:36:25 -0800 | [diff] [blame] | 114 | bool "Connection tracking events (EXPERIMENTAL)" |
| 115 | depends on EXPERIMENTAL && NF_CONNTRACK |
Yasuyuki Kozakai | 9fb9cbb | 2005-11-09 16:38:16 -0800 | [diff] [blame] | 116 | help |
| 117 | If this option is enabled, the connection tracking code will |
| 118 | provide a notifier chain that can be used by other kernel code |
Thomas Vögtle | 50b521a | 2006-03-22 13:53:48 -0800 | [diff] [blame] | 119 | to get notified about changes in the connection tracking state. |
Yasuyuki Kozakai | 9fb9cbb | 2005-11-09 16:38:16 -0800 | [diff] [blame] | 120 | |
| 121 | If unsure, say `N'. |
| 122 | |
| 123 | config NF_CT_PROTO_SCTP |
| 124 | tristate 'SCTP protocol on new connection tracking support (EXPERIMENTAL)' |
| 125 | depends on EXPERIMENTAL && NF_CONNTRACK |
| 126 | default n |
| 127 | help |
| 128 | With this option enabled, the layer 3 independent connection |
| 129 | tracking code will be able to do state tracking on SCTP connections. |
| 130 | |
| 131 | If you want to compile it as a module, say M here and read |
| 132 | Documentation/modules.txt. If unsure, say `N'. |
| 133 | |
Patrick McHardy | 1695890 | 2006-12-02 22:08:26 -0800 | [diff] [blame] | 134 | config NF_CONNTRACK_AMANDA |
| 135 | tristate "Amanda backup protocol support (EXPERIMENTAL)" |
| 136 | depends on EXPERIMENTAL && NF_CONNTRACK |
| 137 | select TEXTSEARCH |
| 138 | select TEXTSEARCH_KMP |
| 139 | help |
| 140 | If you are running the Amanda backup package <http://www.amanda.org/> |
| 141 | on this machine or machines that will be MASQUERADED through this |
| 142 | machine, then you may want to enable this feature. This allows the |
| 143 | connection tracking and natting code to allow the sub-channels that |
| 144 | Amanda requires for communication of the backup data, messages and |
| 145 | index. |
| 146 | |
| 147 | To compile it as a module, choose M here. If unsure, say N. |
| 148 | |
Yasuyuki Kozakai | 9fb9cbb | 2005-11-09 16:38:16 -0800 | [diff] [blame] | 149 | config NF_CONNTRACK_FTP |
| 150 | tristate "FTP support on new connection tracking (EXPERIMENTAL)" |
| 151 | depends on EXPERIMENTAL && NF_CONNTRACK |
| 152 | help |
| 153 | Tracking FTP connections is problematic: special helpers are |
| 154 | required for tracking them, and doing masquerading and other forms |
| 155 | of Network Address Translation on them. |
| 156 | |
| 157 | This is FTP support on Layer 3 independent connection tracking. |
| 158 | Layer 3 independent connection tracking is experimental scheme |
| 159 | which generalize ip_conntrack to support other layer 3 protocols. |
| 160 | |
| 161 | To compile it as a module, choose M here. If unsure, say N. |
| 162 | |
Patrick McHardy | f587de0 | 2006-12-02 22:08:46 -0800 | [diff] [blame^] | 163 | config NF_CONNTRACK_H323 |
| 164 | tristate "H.323 protocol support (EXPERIMENTAL)" |
| 165 | depends on EXPERIMENTAL && NF_CONNTRACK |
| 166 | help |
| 167 | H.323 is a VoIP signalling protocol from ITU-T. As one of the most |
| 168 | important VoIP protocols, it is widely used by voice hardware and |
| 169 | software including voice gateways, IP phones, Netmeeting, OpenPhone, |
| 170 | Gnomemeeting, etc. |
| 171 | |
| 172 | With this module you can support H.323 on a connection tracking/NAT |
| 173 | firewall. |
| 174 | |
| 175 | This module supports RAS, Fast Start, H.245 Tunnelling, Call |
| 176 | Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat, |
| 177 | whiteboard, file transfer, etc. For more information, please |
| 178 | visit http://nath323.sourceforge.net/. |
| 179 | |
| 180 | To compile it as a module, choose M here. If unsure, say N. |
| 181 | |
Pablo Neira Ayuso | c1d10ad | 2006-01-05 12:19:05 -0800 | [diff] [blame] | 182 | config NF_CT_NETLINK |
| 183 | tristate 'Connection tracking netlink interface (EXPERIMENTAL)' |
| 184 | depends on EXPERIMENTAL && NF_CONNTRACK && NETFILTER_NETLINK |
| 185 | depends on NF_CONNTRACK!=y || NETFILTER_NETLINK!=m |
| 186 | help |
| 187 | This option enables support for a netlink-based userspace interface |
| 188 | |
Harald Welte | 2e4e6a1 | 2006-01-12 13:30:04 -0800 | [diff] [blame] | 189 | config NETFILTER_XTABLES |
| 190 | tristate "Netfilter Xtables support (required for ip_tables)" |
| 191 | help |
| 192 | This is required if you intend to use any of ip_tables, |
| 193 | ip6_tables or arp_tables. |
| 194 | |
| 195 | # alphabetically ordered list of targets |
| 196 | |
| 197 | config NETFILTER_XT_TARGET_CLASSIFY |
| 198 | tristate '"CLASSIFY" target support' |
| 199 | depends on NETFILTER_XTABLES |
| 200 | help |
| 201 | This option adds a `CLASSIFY' target, which enables the user to set |
| 202 | the priority of a packet. Some qdiscs can use this value for |
| 203 | classification, among these are: |
| 204 | |
| 205 | atm, cbq, dsmark, pfifo_fast, htb, prio |
| 206 | |
| 207 | To compile it as a module, choose M here. If unsure, say N. |
| 208 | |
| 209 | config NETFILTER_XT_TARGET_CONNMARK |
| 210 | tristate '"CONNMARK" target support' |
| 211 | depends on NETFILTER_XTABLES |
| 212 | depends on IP_NF_MANGLE || IP6_NF_MANGLE |
Yasuyuki Kozakai | deac0cc | 2006-02-15 15:21:31 -0800 | [diff] [blame] | 213 | depends on (IP_NF_CONNTRACK && IP_NF_CONNTRACK_MARK) || (NF_CONNTRACK_MARK && NF_CONNTRACK) |
Harald Welte | 2e4e6a1 | 2006-01-12 13:30:04 -0800 | [diff] [blame] | 214 | help |
| 215 | This option adds a `CONNMARK' target, which allows one to manipulate |
| 216 | the connection mark value. Similar to the MARK target, but |
| 217 | affects the connection mark value rather than the packet mark value. |
| 218 | |
| 219 | If you want to compile it as a module, say M here and read |
| 220 | <file:Documentation/modules.txt>. The module will be called |
| 221 | ipt_CONNMARK.o. If unsure, say `N'. |
| 222 | |
Yasuyuki Kozakai | a468701 | 2006-08-22 00:30:26 -0700 | [diff] [blame] | 223 | config NETFILTER_XT_TARGET_DSCP |
| 224 | tristate '"DSCP" target support' |
| 225 | depends on NETFILTER_XTABLES |
| 226 | depends on IP_NF_MANGLE || IP6_NF_MANGLE |
| 227 | help |
| 228 | This option adds a `DSCP' target, which allows you to manipulate |
| 229 | the IPv4/IPv6 header DSCP field (differentiated services codepoint). |
| 230 | |
| 231 | The DSCP field can have any value between 0x0 and 0x3f inclusive. |
| 232 | |
| 233 | To compile it as a module, choose M here. If unsure, say N. |
| 234 | |
Harald Welte | 2e4e6a1 | 2006-01-12 13:30:04 -0800 | [diff] [blame] | 235 | config NETFILTER_XT_TARGET_MARK |
| 236 | tristate '"MARK" target support' |
| 237 | depends on NETFILTER_XTABLES |
| 238 | help |
| 239 | This option adds a `MARK' target, which allows you to create rules |
| 240 | in the `mangle' table which alter the netfilter mark (nfmark) field |
| 241 | associated with the packet prior to routing. This can change |
| 242 | the routing method (see `Use netfilter MARK value as routing |
| 243 | key') and can also be used by other subsystems to change their |
| 244 | behavior. |
| 245 | |
| 246 | To compile it as a module, choose M here. If unsure, say N. |
| 247 | |
| 248 | config NETFILTER_XT_TARGET_NFQUEUE |
| 249 | tristate '"NFQUEUE" target Support' |
| 250 | depends on NETFILTER_XTABLES |
| 251 | help |
Thomas Vögtle | 50b521a | 2006-03-22 13:53:48 -0800 | [diff] [blame] | 252 | This target replaced the old obsolete QUEUE target. |
Harald Welte | 2e4e6a1 | 2006-01-12 13:30:04 -0800 | [diff] [blame] | 253 | |
| 254 | As opposed to QUEUE, it supports 65535 different queues, |
| 255 | not just one. |
| 256 | |
| 257 | To compile it as a module, choose M here. If unsure, say N. |
| 258 | |
Patrick McHardy | baf7b1e | 2006-11-29 02:35:38 +0100 | [diff] [blame] | 259 | config NETFILTER_XT_TARGET_NFLOG |
| 260 | tristate '"NFLOG" target support' |
| 261 | depends on NETFILTER_XTABLES |
| 262 | help |
| 263 | This option enables the NFLOG target, which allows to LOG |
| 264 | messages through the netfilter logging API, which can use |
| 265 | either the old LOG target, the old ULOG target or nfnetlink_log |
| 266 | as backend. |
| 267 | |
| 268 | To compile it as a module, choose M here. If unsure, say N. |
| 269 | |
Harald Welte | 2e4e6a1 | 2006-01-12 13:30:04 -0800 | [diff] [blame] | 270 | config NETFILTER_XT_TARGET_NOTRACK |
| 271 | tristate '"NOTRACK" target support' |
| 272 | depends on NETFILTER_XTABLES |
| 273 | depends on IP_NF_RAW || IP6_NF_RAW |
| 274 | depends on IP_NF_CONNTRACK || NF_CONNTRACK |
| 275 | help |
| 276 | The NOTRACK target allows a select rule to specify |
| 277 | which packets *not* to enter the conntrack/NAT |
| 278 | subsystem with all the consequences (no ICMP error tracking, |
| 279 | no protocol helpers for the selected packets). |
| 280 | |
| 281 | If you want to compile it as a module, say M here and read |
| 282 | <file:Documentation/modules.txt>. If unsure, say `N'. |
| 283 | |
James Morris | 5e6874cd | 2006-06-09 00:30:57 -0700 | [diff] [blame] | 284 | config NETFILTER_XT_TARGET_SECMARK |
| 285 | tristate '"SECMARK" target support' |
| 286 | depends on NETFILTER_XTABLES && NETWORK_SECMARK |
| 287 | help |
| 288 | The SECMARK target allows security marking of network |
| 289 | packets, for use with security subsystems. |
| 290 | |
| 291 | To compile it as a module, choose M here. If unsure, say N. |
| 292 | |
James Morris | 100468e | 2006-06-09 00:32:39 -0700 | [diff] [blame] | 293 | config NETFILTER_XT_TARGET_CONNSECMARK |
| 294 | tristate '"CONNSECMARK" target support' |
Patrick McHardy | c08de5d | 2006-10-12 14:08:41 -0700 | [diff] [blame] | 295 | depends on NETFILTER_XTABLES && \ |
| 296 | ((NF_CONNTRACK && NF_CONNTRACK_SECMARK) || \ |
| 297 | (IP_NF_CONNTRACK && IP_NF_CONNTRACK_SECMARK)) |
James Morris | 100468e | 2006-06-09 00:32:39 -0700 | [diff] [blame] | 298 | help |
| 299 | The CONNSECMARK target copies security markings from packets |
| 300 | to connections, and restores security markings from connections |
| 301 | to packets (if the packets are not already marked). This would |
| 302 | normally be used in conjunction with the SECMARK target. |
| 303 | |
| 304 | To compile it as a module, choose M here. If unsure, say N. |
| 305 | |
Harald Welte | 2e4e6a1 | 2006-01-12 13:30:04 -0800 | [diff] [blame] | 306 | config NETFILTER_XT_MATCH_COMMENT |
| 307 | tristate '"comment" match support' |
| 308 | depends on NETFILTER_XTABLES |
| 309 | help |
| 310 | This option adds a `comment' dummy-match, which allows you to put |
| 311 | comments in your iptables ruleset. |
| 312 | |
| 313 | If you want to compile it as a module, say M here and read |
| 314 | <file:Documentation/modules.txt>. If unsure, say `N'. |
| 315 | |
| 316 | config NETFILTER_XT_MATCH_CONNBYTES |
| 317 | tristate '"connbytes" per-connection counter match support' |
| 318 | depends on NETFILTER_XTABLES |
Yasuyuki Kozakai | deac0cc | 2006-02-15 15:21:31 -0800 | [diff] [blame] | 319 | depends on (IP_NF_CONNTRACK && IP_NF_CT_ACCT) || (NF_CT_ACCT && NF_CONNTRACK) |
Harald Welte | 2e4e6a1 | 2006-01-12 13:30:04 -0800 | [diff] [blame] | 320 | help |
| 321 | This option adds a `connbytes' match, which allows you to match the |
| 322 | number of bytes and/or packets for each direction within a connection. |
| 323 | |
| 324 | If you want to compile it as a module, say M here and read |
| 325 | <file:Documentation/modules.txt>. If unsure, say `N'. |
| 326 | |
| 327 | config NETFILTER_XT_MATCH_CONNMARK |
| 328 | tristate '"connmark" connection mark match support' |
| 329 | depends on NETFILTER_XTABLES |
Yasuyuki Kozakai | deac0cc | 2006-02-15 15:21:31 -0800 | [diff] [blame] | 330 | depends on (IP_NF_CONNTRACK && IP_NF_CONNTRACK_MARK) || (NF_CONNTRACK_MARK && NF_CONNTRACK) |
Harald Welte | 2e4e6a1 | 2006-01-12 13:30:04 -0800 | [diff] [blame] | 331 | help |
| 332 | This option adds a `connmark' match, which allows you to match the |
| 333 | connection mark value previously set for the session by `CONNMARK'. |
| 334 | |
| 335 | If you want to compile it as a module, say M here and read |
| 336 | <file:Documentation/modules.txt>. The module will be called |
| 337 | ipt_connmark.o. If unsure, say `N'. |
| 338 | |
| 339 | config NETFILTER_XT_MATCH_CONNTRACK |
| 340 | tristate '"conntrack" connection tracking match support' |
| 341 | depends on NETFILTER_XTABLES |
| 342 | depends on IP_NF_CONNTRACK || NF_CONNTRACK |
| 343 | help |
| 344 | This is a general conntrack match module, a superset of the state match. |
| 345 | |
| 346 | It allows matching on additional conntrack information, which is |
| 347 | useful in complex configurations, such as NAT gateways with multiple |
| 348 | internet links or tunnels. |
| 349 | |
| 350 | To compile it as a module, choose M here. If unsure, say N. |
| 351 | |
| 352 | config NETFILTER_XT_MATCH_DCCP |
| 353 | tristate '"DCCP" protocol match support' |
| 354 | depends on NETFILTER_XTABLES |
| 355 | help |
| 356 | With this option enabled, you will be able to use the iptables |
| 357 | `dccp' match in order to match on DCCP source/destination ports |
| 358 | and DCCP flags. |
| 359 | |
| 360 | If you want to compile it as a module, say M here and read |
| 361 | <file:Documentation/modules.txt>. If unsure, say `N'. |
| 362 | |
Yasuyuki Kozakai | 9ba1627 | 2006-08-22 00:29:37 -0700 | [diff] [blame] | 363 | config NETFILTER_XT_MATCH_DSCP |
| 364 | tristate '"DSCP" match support' |
| 365 | depends on NETFILTER_XTABLES |
| 366 | help |
| 367 | This option adds a `DSCP' match, which allows you to match against |
| 368 | the IPv4/IPv6 header DSCP field (differentiated services codepoint). |
| 369 | |
| 370 | The DSCP field can have any value between 0x0 and 0x3f inclusive. |
| 371 | |
| 372 | To compile it as a module, choose M here. If unsure, say N. |
| 373 | |
Yasuyuki Kozakai | dc5ab2f | 2006-04-01 02:22:30 -0800 | [diff] [blame] | 374 | config NETFILTER_XT_MATCH_ESP |
| 375 | tristate '"ESP" match support' |
| 376 | depends on NETFILTER_XTABLES |
| 377 | help |
| 378 | This match extension allows you to match a range of SPIs |
| 379 | inside ESP header of IPSec packets. |
| 380 | |
| 381 | To compile it as a module, choose M here. If unsure, say N. |
| 382 | |
Harald Welte | 2e4e6a1 | 2006-01-12 13:30:04 -0800 | [diff] [blame] | 383 | config NETFILTER_XT_MATCH_HELPER |
| 384 | tristate '"helper" match support' |
| 385 | depends on NETFILTER_XTABLES |
| 386 | depends on IP_NF_CONNTRACK || NF_CONNTRACK |
| 387 | help |
| 388 | Helper matching allows you to match packets in dynamic connections |
| 389 | tracked by a conntrack-helper, ie. ip_conntrack_ftp |
| 390 | |
| 391 | To compile it as a module, choose M here. If unsure, say Y. |
| 392 | |
| 393 | config NETFILTER_XT_MATCH_LENGTH |
| 394 | tristate '"length" match support' |
| 395 | depends on NETFILTER_XTABLES |
| 396 | help |
| 397 | This option allows you to match the length of a packet against a |
| 398 | specific value or range of values. |
| 399 | |
| 400 | To compile it as a module, choose M here. If unsure, say N. |
| 401 | |
| 402 | config NETFILTER_XT_MATCH_LIMIT |
| 403 | tristate '"limit" match support' |
| 404 | depends on NETFILTER_XTABLES |
| 405 | help |
| 406 | limit matching allows you to control the rate at which a rule can be |
| 407 | matched: mainly useful in combination with the LOG target ("LOG |
| 408 | target support", below) and to avoid some Denial of Service attacks. |
| 409 | |
| 410 | To compile it as a module, choose M here. If unsure, say N. |
| 411 | |
| 412 | config NETFILTER_XT_MATCH_MAC |
| 413 | tristate '"mac" address match support' |
| 414 | depends on NETFILTER_XTABLES |
| 415 | help |
| 416 | MAC matching allows you to match packets based on the source |
| 417 | Ethernet address of the packet. |
| 418 | |
| 419 | To compile it as a module, choose M here. If unsure, say N. |
| 420 | |
| 421 | config NETFILTER_XT_MATCH_MARK |
| 422 | tristate '"mark" match support' |
| 423 | depends on NETFILTER_XTABLES |
| 424 | help |
| 425 | Netfilter mark matching allows you to match packets based on the |
| 426 | `nfmark' value in the packet. This can be set by the MARK target |
| 427 | (see below). |
| 428 | |
| 429 | To compile it as a module, choose M here. If unsure, say N. |
| 430 | |
Patrick McHardy | c4b8851 | 2006-03-20 18:03:40 -0800 | [diff] [blame] | 431 | config NETFILTER_XT_MATCH_POLICY |
| 432 | tristate 'IPsec "policy" match support' |
| 433 | depends on NETFILTER_XTABLES && XFRM |
| 434 | help |
| 435 | Policy matching allows you to match packets based on the |
| 436 | IPsec policy that was used during decapsulation/will |
| 437 | be used during encapsulation. |
| 438 | |
| 439 | To compile it as a module, choose M here. If unsure, say N. |
| 440 | |
Yasuyuki Kozakai | a89ecb6 | 2006-04-01 02:22:54 -0800 | [diff] [blame] | 441 | config NETFILTER_XT_MATCH_MULTIPORT |
| 442 | tristate "Multiple port match support" |
| 443 | depends on NETFILTER_XTABLES |
| 444 | help |
| 445 | Multiport matching allows you to match TCP or UDP packets based on |
| 446 | a series of source or destination ports: normally a rule can only |
| 447 | match a single range of ports. |
| 448 | |
| 449 | To compile it as a module, choose M here. If unsure, say N. |
| 450 | |
Harald Welte | 2e4e6a1 | 2006-01-12 13:30:04 -0800 | [diff] [blame] | 451 | config NETFILTER_XT_MATCH_PHYSDEV |
| 452 | tristate '"physdev" match support' |
Patrick McHardy | f1da706 | 2006-10-02 16:10:47 -0700 | [diff] [blame] | 453 | depends on NETFILTER_XTABLES && BRIDGE && BRIDGE_NETFILTER |
Harald Welte | 2e4e6a1 | 2006-01-12 13:30:04 -0800 | [diff] [blame] | 454 | help |
| 455 | Physdev packet matching matches against the physical bridge ports |
| 456 | the IP packet arrived on or will leave by. |
| 457 | |
| 458 | To compile it as a module, choose M here. If unsure, say N. |
| 459 | |
| 460 | config NETFILTER_XT_MATCH_PKTTYPE |
| 461 | tristate '"pkttype" packet type match support' |
| 462 | depends on NETFILTER_XTABLES |
| 463 | help |
| 464 | Packet type matching allows you to match a packet by |
| 465 | its "class", eg. BROADCAST, MULTICAST, ... |
| 466 | |
| 467 | Typical usage: |
| 468 | iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG |
| 469 | |
| 470 | To compile it as a module, choose M here. If unsure, say N. |
| 471 | |
Patrick McHardy | 62b7743 | 2006-05-29 18:20:32 -0700 | [diff] [blame] | 472 | config NETFILTER_XT_MATCH_QUOTA |
| 473 | tristate '"quota" match support' |
| 474 | depends on NETFILTER_XTABLES |
| 475 | help |
| 476 | This option adds a `quota' match, which allows to match on a |
| 477 | byte counter. |
| 478 | |
| 479 | If you want to compile it as a module, say M here and read |
| 480 | <file:Documentation/modules.txt>. If unsure, say `N'. |
| 481 | |
Harald Welte | 2e4e6a1 | 2006-01-12 13:30:04 -0800 | [diff] [blame] | 482 | config NETFILTER_XT_MATCH_REALM |
| 483 | tristate '"realm" match support' |
| 484 | depends on NETFILTER_XTABLES |
| 485 | select NET_CLS_ROUTE |
| 486 | help |
| 487 | This option adds a `realm' match, which allows you to use the realm |
| 488 | key from the routing subsystem inside iptables. |
| 489 | |
| 490 | This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option |
| 491 | in tc world. |
| 492 | |
| 493 | If you want to compile it as a module, say M here and read |
| 494 | <file:Documentation/modules.txt>. If unsure, say `N'. |
| 495 | |
| 496 | config NETFILTER_XT_MATCH_SCTP |
Patrick McHardy | d5af981 | 2006-07-24 22:55:29 -0700 | [diff] [blame] | 497 | tristate '"sctp" protocol match support (EXPERIMENTAL)' |
| 498 | depends on NETFILTER_XTABLES && EXPERIMENTAL |
Harald Welte | 2e4e6a1 | 2006-01-12 13:30:04 -0800 | [diff] [blame] | 499 | help |
| 500 | With this option enabled, you will be able to use the |
| 501 | `sctp' match in order to match on SCTP source/destination ports |
| 502 | and SCTP chunk types. |
| 503 | |
| 504 | If you want to compile it as a module, say M here and read |
| 505 | <file:Documentation/modules.txt>. If unsure, say `N'. |
| 506 | |
| 507 | config NETFILTER_XT_MATCH_STATE |
| 508 | tristate '"state" match support' |
| 509 | depends on NETFILTER_XTABLES |
| 510 | depends on IP_NF_CONNTRACK || NF_CONNTRACK |
| 511 | help |
| 512 | Connection state matching allows you to match packets based on their |
| 513 | relationship to a tracked connection (ie. previous packets). This |
| 514 | is a powerful tool for packet classification. |
| 515 | |
| 516 | To compile it as a module, choose M here. If unsure, say N. |
| 517 | |
Patrick McHardy | f338980 | 2006-05-29 18:21:00 -0700 | [diff] [blame] | 518 | config NETFILTER_XT_MATCH_STATISTIC |
| 519 | tristate '"statistic" match support' |
| 520 | depends on NETFILTER_XTABLES |
| 521 | help |
Patrick McHardy | 68c1692 | 2006-06-27 03:02:14 -0700 | [diff] [blame] | 522 | This option adds a `statistic' match, which allows you to match |
| 523 | on packets periodically or randomly with a given percentage. |
| 524 | |
| 525 | To compile it as a module, choose M here. If unsure, say N. |
Patrick McHardy | f338980 | 2006-05-29 18:21:00 -0700 | [diff] [blame] | 526 | |
Harald Welte | 2e4e6a1 | 2006-01-12 13:30:04 -0800 | [diff] [blame] | 527 | config NETFILTER_XT_MATCH_STRING |
| 528 | tristate '"string" match support' |
| 529 | depends on NETFILTER_XTABLES |
| 530 | select TEXTSEARCH |
| 531 | select TEXTSEARCH_KMP |
| 532 | select TEXTSEARCH_BM |
| 533 | select TEXTSEARCH_FSM |
| 534 | help |
| 535 | This option adds a `string' match, which allows you to look for |
| 536 | pattern matchings in packets. |
| 537 | |
| 538 | To compile it as a module, choose M here. If unsure, say N. |
| 539 | |
| 540 | config NETFILTER_XT_MATCH_TCPMSS |
| 541 | tristate '"tcpmss" match support' |
| 542 | depends on NETFILTER_XTABLES |
| 543 | help |
| 544 | This option adds a `tcpmss' match, which allows you to examine the |
| 545 | MSS value of TCP SYN packets, which control the maximum packet size |
| 546 | for that connection. |
| 547 | |
| 548 | To compile it as a module, choose M here. If unsure, say N. |
| 549 | |
Patrick McHardy | 39b46fc | 2006-11-29 02:35:36 +0100 | [diff] [blame] | 550 | config NETFILTER_XT_MATCH_HASHLIMIT |
| 551 | tristate '"hashlimit" match support' |
| 552 | depends on NETFILTER_XTABLES |
| 553 | help |
| 554 | This option adds a `hashlimit' match. |
| 555 | |
| 556 | As opposed to `limit', this match dynamically creates a hash table |
| 557 | of limit buckets, based on your selection of source/destination |
| 558 | addresses and/or ports. |
| 559 | |
| 560 | It enables you to express policies like `10kpps for any given |
| 561 | destination address' or `500pps from any given source address' |
| 562 | with a single rule. |
| 563 | |
Harald Welte | a6c1cd57 | 2006-02-13 15:42:48 -0800 | [diff] [blame] | 564 | endmenu |
| 565 | |