Kconfig 23 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653
  1. menu "Core Netfilter Configuration"
  2. depends on NET && INET && NETFILTER
  3. config NETFILTER_NETLINK
  4. tristate "Netfilter netlink interface"
  5. help
  6. If this option is enabled, the kernel will include support
  7. for the new netfilter netlink interface.
  8. config NETFILTER_NETLINK_QUEUE
  9. tristate "Netfilter NFQUEUE over NFNETLINK interface"
  10. depends on NETFILTER_NETLINK
  11. help
  12. If this option is enabled, the kernel will include support
  13. for queueing packets via NFNETLINK.
  14. config NETFILTER_NETLINK_LOG
  15. tristate "Netfilter LOG over NFNETLINK interface"
  16. depends on NETFILTER_NETLINK
  17. help
  18. If this option is enabled, the kernel will include support
  19. for logging packets via NFNETLINK.
  20. This obsoletes the existing ipt_ULOG and ebg_ulog mechanisms,
  21. and is also scheduled to replace the old syslog-based ipt_LOG
  22. and ip6t_LOG modules.
  23. # Rename this to NF_CONNTRACK in a 2.6.25
  24. config NF_CONNTRACK_ENABLED
  25. tristate "Netfilter connection tracking support"
  26. help
  27. Connection tracking keeps a record of what packets have passed
  28. through your machine, in order to figure out how they are related
  29. into connections.
  30. This is required to do Masquerading or other kinds of Network
  31. Address Translation (except for Fast NAT). It can also be used to
  32. enhance packet filtering (see `Connection state match support'
  33. below).
  34. To compile it as a module, choose M here. If unsure, say N.
  35. config NF_CONNTRACK
  36. tristate
  37. default NF_CONNTRACK_ENABLED
  38. config NF_CT_ACCT
  39. bool "Connection tracking flow accounting"
  40. depends on NF_CONNTRACK
  41. help
  42. If this option is enabled, the connection tracking code will
  43. keep per-flow packet and byte counters.
  44. Those counters can be used for flow-based accounting or the
  45. `connbytes' match.
  46. If unsure, say `N'.
  47. config NF_CONNTRACK_MARK
  48. bool 'Connection mark tracking support'
  49. depends on NF_CONNTRACK
  50. help
  51. This option enables support for connection marks, used by the
  52. `CONNMARK' target and `connmark' match. Similar to the mark value
  53. of packets, but this mark value is kept in the conntrack session
  54. instead of the individual packets.
  55. config NF_CONNTRACK_SECMARK
  56. bool 'Connection tracking security mark support'
  57. depends on NF_CONNTRACK && NETWORK_SECMARK
  58. help
  59. This option enables security markings to be applied to
  60. connections. Typically they are copied to connections from
  61. packets using the CONNSECMARK target and copied back from
  62. connections to packets with the same target, with the packets
  63. being originally labeled via SECMARK.
  64. If unsure, say 'N'.
  65. config NF_CONNTRACK_EVENTS
  66. bool "Connection tracking events (EXPERIMENTAL)"
  67. depends on EXPERIMENTAL && NF_CONNTRACK
  68. help
  69. If this option is enabled, the connection tracking code will
  70. provide a notifier chain that can be used by other kernel code
  71. to get notified about changes in the connection tracking state.
  72. If unsure, say `N'.
  73. config NF_CT_PROTO_GRE
  74. tristate
  75. depends on NF_CONNTRACK
  76. config NF_CT_PROTO_SCTP
  77. tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
  78. depends on EXPERIMENTAL && NF_CONNTRACK
  79. default n
  80. help
  81. With this option enabled, the layer 3 independent connection
  82. tracking code will be able to do state tracking on SCTP connections.
  83. If you want to compile it as a module, say M here and read
  84. <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
  85. config NF_CONNTRACK_AMANDA
  86. tristate "Amanda backup protocol support"
  87. depends on NF_CONNTRACK
  88. select TEXTSEARCH
  89. select TEXTSEARCH_KMP
  90. help
  91. If you are running the Amanda backup package <http://www.amanda.org/>
  92. on this machine or machines that will be MASQUERADED through this
  93. machine, then you may want to enable this feature. This allows the
  94. connection tracking and natting code to allow the sub-channels that
  95. Amanda requires for communication of the backup data, messages and
  96. index.
  97. To compile it as a module, choose M here. If unsure, say N.
  98. config NF_CONNTRACK_FTP
  99. tristate "FTP protocol support"
  100. depends on NF_CONNTRACK
  101. help
  102. Tracking FTP connections is problematic: special helpers are
  103. required for tracking them, and doing masquerading and other forms
  104. of Network Address Translation on them.
  105. This is FTP support on Layer 3 independent connection tracking.
  106. Layer 3 independent connection tracking is experimental scheme
  107. which generalize ip_conntrack to support other layer 3 protocols.
  108. To compile it as a module, choose M here. If unsure, say N.
  109. config NF_CONNTRACK_H323
  110. tristate "H.323 protocol support (EXPERIMENTAL)"
  111. depends on EXPERIMENTAL && NF_CONNTRACK && (IPV6 || IPV6=n)
  112. help
  113. H.323 is a VoIP signalling protocol from ITU-T. As one of the most
  114. important VoIP protocols, it is widely used by voice hardware and
  115. software including voice gateways, IP phones, Netmeeting, OpenPhone,
  116. Gnomemeeting, etc.
  117. With this module you can support H.323 on a connection tracking/NAT
  118. firewall.
  119. This module supports RAS, Fast Start, H.245 Tunnelling, Call
  120. Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
  121. whiteboard, file transfer, etc. For more information, please
  122. visit http://nath323.sourceforge.net/.
  123. To compile it as a module, choose M here. If unsure, say N.
  124. config NF_CONNTRACK_IRC
  125. tristate "IRC protocol support"
  126. depends on NF_CONNTRACK
  127. help
  128. There is a commonly-used extension to IRC called
  129. Direct Client-to-Client Protocol (DCC). This enables users to send
  130. files to each other, and also chat to each other without the need
  131. of a server. DCC Sending is used anywhere you send files over IRC,
  132. and DCC Chat is most commonly used by Eggdrop bots. If you are
  133. using NAT, this extension will enable you to send files and initiate
  134. chats. Note that you do NOT need this extension to get files or
  135. have others initiate chats, or everything else in IRC.
  136. To compile it as a module, choose M here. If unsure, say N.
  137. config NF_CONNTRACK_NETBIOS_NS
  138. tristate "NetBIOS name service protocol support (EXPERIMENTAL)"
  139. depends on EXPERIMENTAL && NF_CONNTRACK
  140. help
  141. NetBIOS name service requests are sent as broadcast messages from an
  142. unprivileged port and responded to with unicast messages to the
  143. same port. This make them hard to firewall properly because connection
  144. tracking doesn't deal with broadcasts. This helper tracks locally
  145. originating NetBIOS name service requests and the corresponding
  146. responses. It relies on correct IP address configuration, specifically
  147. netmask and broadcast address. When properly configured, the output
  148. of "ip address show" should look similar to this:
  149. $ ip -4 address show eth0
  150. 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
  151. inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
  152. To compile it as a module, choose M here. If unsure, say N.
  153. config NF_CONNTRACK_PPTP
  154. tristate "PPtP protocol support"
  155. depends on NF_CONNTRACK
  156. select NF_CT_PROTO_GRE
  157. help
  158. This module adds support for PPTP (Point to Point Tunnelling
  159. Protocol, RFC2637) connection tracking and NAT.
  160. If you are running PPTP sessions over a stateful firewall or NAT
  161. box, you may want to enable this feature.
  162. Please note that not all PPTP modes of operation are supported yet.
  163. Specifically these limitations exist:
  164. - Blindly assumes that control connections are always established
  165. in PNS->PAC direction. This is a violation of RFC2637.
  166. - Only supports a single call within each session
  167. To compile it as a module, choose M here. If unsure, say N.
  168. config NF_CONNTRACK_SANE
  169. tristate "SANE protocol support (EXPERIMENTAL)"
  170. depends on EXPERIMENTAL && NF_CONNTRACK
  171. help
  172. SANE is a protocol for remote access to scanners as implemented
  173. by the 'saned' daemon. Like FTP, it uses separate control and
  174. data connections.
  175. With this module you can support SANE on a connection tracking
  176. firewall.
  177. To compile it as a module, choose M here. If unsure, say N.
  178. config NF_CONNTRACK_SIP
  179. tristate "SIP protocol support (EXPERIMENTAL)"
  180. depends on EXPERIMENTAL && NF_CONNTRACK
  181. help
  182. SIP is an application-layer control protocol that can establish,
  183. modify, and terminate multimedia sessions (conferences) such as
  184. Internet telephony calls. With the ip_conntrack_sip and
  185. the nf_nat_sip modules you can support the protocol on a connection
  186. tracking/NATing firewall.
  187. To compile it as a module, choose M here. If unsure, say N.
  188. config NF_CONNTRACK_TFTP
  189. tristate "TFTP protocol support"
  190. depends on NF_CONNTRACK
  191. help
  192. TFTP connection tracking helper, this is required depending
  193. on how restrictive your ruleset is.
  194. If you are using a tftp client behind -j SNAT or -j MASQUERADING
  195. you will need this.
  196. To compile it as a module, choose M here. If unsure, say N.
  197. config NF_CT_NETLINK
  198. tristate 'Connection tracking netlink interface (EXPERIMENTAL)'
  199. depends on EXPERIMENTAL && NF_CONNTRACK && NETFILTER_NETLINK
  200. depends on NF_CONNTRACK!=y || NETFILTER_NETLINK!=m
  201. depends on NF_NAT=n || NF_NAT
  202. help
  203. This option enables support for a netlink-based userspace interface
  204. config NETFILTER_XTABLES
  205. tristate "Netfilter Xtables support (required for ip_tables)"
  206. help
  207. This is required if you intend to use any of ip_tables,
  208. ip6_tables or arp_tables.
  209. # alphabetically ordered list of targets
  210. config NETFILTER_XT_TARGET_CLASSIFY
  211. tristate '"CLASSIFY" target support'
  212. depends on NETFILTER_XTABLES
  213. help
  214. This option adds a `CLASSIFY' target, which enables the user to set
  215. the priority of a packet. Some qdiscs can use this value for
  216. classification, among these are:
  217. atm, cbq, dsmark, pfifo_fast, htb, prio
  218. To compile it as a module, choose M here. If unsure, say N.
  219. config NETFILTER_XT_TARGET_CONNMARK
  220. tristate '"CONNMARK" target support'
  221. depends on NETFILTER_XTABLES
  222. depends on IP_NF_MANGLE || IP6_NF_MANGLE
  223. depends on NF_CONNTRACK
  224. select NF_CONNTRACK_MARK
  225. help
  226. This option adds a `CONNMARK' target, which allows one to manipulate
  227. the connection mark value. Similar to the MARK target, but
  228. affects the connection mark value rather than the packet mark value.
  229. If you want to compile it as a module, say M here and read
  230. <file:Documentation/kbuild/modules.txt>. The module will be called
  231. ipt_CONNMARK.ko. If unsure, say `N'.
  232. config NETFILTER_XT_TARGET_DSCP
  233. tristate '"DSCP" target support'
  234. depends on NETFILTER_XTABLES
  235. depends on IP_NF_MANGLE || IP6_NF_MANGLE
  236. help
  237. This option adds a `DSCP' target, which allows you to manipulate
  238. the IPv4/IPv6 header DSCP field (differentiated services codepoint).
  239. The DSCP field can have any value between 0x0 and 0x3f inclusive.
  240. To compile it as a module, choose M here. If unsure, say N.
  241. config NETFILTER_XT_TARGET_MARK
  242. tristate '"MARK" target support'
  243. depends on NETFILTER_XTABLES
  244. help
  245. This option adds a `MARK' target, which allows you to create rules
  246. in the `mangle' table which alter the netfilter mark (nfmark) field
  247. associated with the packet prior to routing. This can change
  248. the routing method (see `Use netfilter MARK value as routing
  249. key') and can also be used by other subsystems to change their
  250. behavior.
  251. To compile it as a module, choose M here. If unsure, say N.
  252. config NETFILTER_XT_TARGET_NFQUEUE
  253. tristate '"NFQUEUE" target Support'
  254. depends on NETFILTER_XTABLES
  255. help
  256. This target replaced the old obsolete QUEUE target.
  257. As opposed to QUEUE, it supports 65535 different queues,
  258. not just one.
  259. To compile it as a module, choose M here. If unsure, say N.
  260. config NETFILTER_XT_TARGET_NFLOG
  261. tristate '"NFLOG" target support'
  262. depends on NETFILTER_XTABLES
  263. help
  264. This option enables the NFLOG target, which allows to LOG
  265. messages through the netfilter logging API, which can use
  266. either the old LOG target, the old ULOG target or nfnetlink_log
  267. as backend.
  268. To compile it as a module, choose M here. If unsure, say N.
  269. config NETFILTER_XT_TARGET_NOTRACK
  270. tristate '"NOTRACK" target support'
  271. depends on NETFILTER_XTABLES
  272. depends on IP_NF_RAW || IP6_NF_RAW
  273. depends on NF_CONNTRACK
  274. help
  275. The NOTRACK target allows a select rule to specify
  276. which packets *not* to enter the conntrack/NAT
  277. subsystem with all the consequences (no ICMP error tracking,
  278. no protocol helpers for the selected packets).
  279. If you want to compile it as a module, say M here and read
  280. <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
  281. config NETFILTER_XT_TARGET_SECMARK
  282. tristate '"SECMARK" target support'
  283. depends on NETFILTER_XTABLES && NETWORK_SECMARK
  284. help
  285. The SECMARK target allows security marking of network
  286. packets, for use with security subsystems.
  287. To compile it as a module, choose M here. If unsure, say N.
  288. config NETFILTER_XT_TARGET_CONNSECMARK
  289. tristate '"CONNSECMARK" target support'
  290. depends on NETFILTER_XTABLES && NF_CONNTRACK && NF_CONNTRACK_SECMARK
  291. help
  292. The CONNSECMARK target copies security markings from packets
  293. to connections, and restores security markings from connections
  294. to packets (if the packets are not already marked). This would
  295. normally be used in conjunction with the SECMARK target.
  296. To compile it as a module, choose M here. If unsure, say N.
  297. config NETFILTER_XT_TARGET_TCPMSS
  298. tristate '"TCPMSS" target support'
  299. depends on NETFILTER_XTABLES && (IPV6 || IPV6=n)
  300. ---help---
  301. This option adds a `TCPMSS' target, which allows you to alter the
  302. MSS value of TCP SYN packets, to control the maximum size for that
  303. connection (usually limiting it to your outgoing interface's MTU
  304. minus 40).
  305. This is used to overcome criminally braindead ISPs or servers which
  306. block ICMP Fragmentation Needed packets. The symptoms of this
  307. problem are that everything works fine from your Linux
  308. firewall/router, but machines behind it can never exchange large
  309. packets:
  310. 1) Web browsers connect, then hang with no data received.
  311. 2) Small mail works fine, but large emails hang.
  312. 3) ssh works fine, but scp hangs after initial handshaking.
  313. Workaround: activate this option and add a rule to your firewall
  314. configuration like:
  315. iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
  316. -j TCPMSS --clamp-mss-to-pmtu
  317. To compile it as a module, choose M here. If unsure, say N.
  318. config NETFILTER_XT_MATCH_COMMENT
  319. tristate '"comment" match support'
  320. depends on NETFILTER_XTABLES
  321. help
  322. This option adds a `comment' dummy-match, which allows you to put
  323. comments in your iptables ruleset.
  324. If you want to compile it as a module, say M here and read
  325. <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
  326. config NETFILTER_XT_MATCH_CONNBYTES
  327. tristate '"connbytes" per-connection counter match support'
  328. depends on NETFILTER_XTABLES
  329. depends on NF_CONNTRACK
  330. select NF_CT_ACCT
  331. help
  332. This option adds a `connbytes' match, which allows you to match the
  333. number of bytes and/or packets for each direction within a connection.
  334. If you want to compile it as a module, say M here and read
  335. <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
  336. config NETFILTER_XT_MATCH_CONNMARK
  337. tristate '"connmark" connection mark match support'
  338. depends on NETFILTER_XTABLES
  339. depends on NF_CONNTRACK
  340. select NF_CONNTRACK_MARK
  341. help
  342. This option adds a `connmark' match, which allows you to match the
  343. connection mark value previously set for the session by `CONNMARK'.
  344. If you want to compile it as a module, say M here and read
  345. <file:Documentation/kbuild/modules.txt>. The module will be called
  346. ipt_connmark.ko. If unsure, say `N'.
  347. config NETFILTER_XT_MATCH_CONNTRACK
  348. tristate '"conntrack" connection tracking match support'
  349. depends on NETFILTER_XTABLES
  350. depends on NF_CONNTRACK
  351. help
  352. This is a general conntrack match module, a superset of the state match.
  353. It allows matching on additional conntrack information, which is
  354. useful in complex configurations, such as NAT gateways with multiple
  355. internet links or tunnels.
  356. To compile it as a module, choose M here. If unsure, say N.
  357. config NETFILTER_XT_MATCH_DCCP
  358. tristate '"DCCP" protocol match support'
  359. depends on NETFILTER_XTABLES
  360. help
  361. With this option enabled, you will be able to use the iptables
  362. `dccp' match in order to match on DCCP source/destination ports
  363. and DCCP flags.
  364. If you want to compile it as a module, say M here and read
  365. <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
  366. config NETFILTER_XT_MATCH_DSCP
  367. tristate '"DSCP" match support'
  368. depends on NETFILTER_XTABLES
  369. help
  370. This option adds a `DSCP' match, which allows you to match against
  371. the IPv4/IPv6 header DSCP field (differentiated services codepoint).
  372. The DSCP field can have any value between 0x0 and 0x3f inclusive.
  373. To compile it as a module, choose M here. If unsure, say N.
  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. To compile it as a module, choose M here. If unsure, say N.
  381. config NETFILTER_XT_MATCH_HELPER
  382. tristate '"helper" match support'
  383. depends on NETFILTER_XTABLES
  384. depends on NF_CONNTRACK
  385. help
  386. Helper matching allows you to match packets in dynamic connections
  387. tracked by a conntrack-helper, ie. ip_conntrack_ftp
  388. To compile it as a module, choose M here. If unsure, say Y.
  389. config NETFILTER_XT_MATCH_LENGTH
  390. tristate '"length" match support'
  391. depends on NETFILTER_XTABLES
  392. help
  393. This option allows you to match the length of a packet against a
  394. specific value or range of values.
  395. To compile it as a module, choose M here. If unsure, say N.
  396. config NETFILTER_XT_MATCH_LIMIT
  397. tristate '"limit" match support'
  398. depends on NETFILTER_XTABLES
  399. help
  400. limit matching allows you to control the rate at which a rule can be
  401. matched: mainly useful in combination with the LOG target ("LOG
  402. target support", below) and to avoid some Denial of Service attacks.
  403. To compile it as a module, choose M here. If unsure, say N.
  404. config NETFILTER_XT_MATCH_MAC
  405. tristate '"mac" address match support'
  406. depends on NETFILTER_XTABLES
  407. help
  408. MAC matching allows you to match packets based on the source
  409. Ethernet address of the packet.
  410. To compile it as a module, choose M here. If unsure, say N.
  411. config NETFILTER_XT_MATCH_MARK
  412. tristate '"mark" match support'
  413. depends on NETFILTER_XTABLES
  414. help
  415. Netfilter mark matching allows you to match packets based on the
  416. `nfmark' value in the packet. This can be set by the MARK target
  417. (see below).
  418. To compile it as a module, choose M here. If unsure, say N.
  419. config NETFILTER_XT_MATCH_POLICY
  420. tristate 'IPsec "policy" match support'
  421. depends on NETFILTER_XTABLES && XFRM
  422. help
  423. Policy matching allows you to match packets based on the
  424. IPsec policy that was used during decapsulation/will
  425. be used during encapsulation.
  426. To compile it as a module, choose M here. If unsure, say N.
  427. config NETFILTER_XT_MATCH_MULTIPORT
  428. tristate "Multiple port match support"
  429. depends on NETFILTER_XTABLES
  430. help
  431. Multiport matching allows you to match TCP or UDP packets based on
  432. a series of source or destination ports: normally a rule can only
  433. match a single range of ports.
  434. To compile it as a module, choose M here. If unsure, say N.
  435. config NETFILTER_XT_MATCH_PHYSDEV
  436. tristate '"physdev" match support'
  437. depends on NETFILTER_XTABLES && BRIDGE && BRIDGE_NETFILTER
  438. help
  439. Physdev packet matching matches against the physical bridge ports
  440. the IP packet arrived on or will leave by.
  441. To compile it as a module, choose M here. If unsure, say N.
  442. config NETFILTER_XT_MATCH_PKTTYPE
  443. tristate '"pkttype" packet type match support'
  444. depends on NETFILTER_XTABLES
  445. help
  446. Packet type matching allows you to match a packet by
  447. its "class", eg. BROADCAST, MULTICAST, ...
  448. Typical usage:
  449. iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
  450. To compile it as a module, choose M here. If unsure, say N.
  451. config NETFILTER_XT_MATCH_QUOTA
  452. tristate '"quota" match support'
  453. depends on NETFILTER_XTABLES
  454. help
  455. This option adds a `quota' match, which allows to match on a
  456. byte counter.
  457. If you want to compile it as a module, say M here and read
  458. <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
  459. config NETFILTER_XT_MATCH_REALM
  460. tristate '"realm" match support'
  461. depends on NETFILTER_XTABLES
  462. select NET_CLS_ROUTE
  463. help
  464. This option adds a `realm' match, which allows you to use the realm
  465. key from the routing subsystem inside iptables.
  466. This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
  467. in tc world.
  468. If you want to compile it as a module, say M here and read
  469. <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
  470. config NETFILTER_XT_MATCH_SCTP
  471. tristate '"sctp" protocol match support (EXPERIMENTAL)'
  472. depends on NETFILTER_XTABLES && EXPERIMENTAL
  473. help
  474. With this option enabled, you will be able to use the
  475. `sctp' match in order to match on SCTP source/destination ports
  476. and SCTP chunk types.
  477. If you want to compile it as a module, say M here and read
  478. <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
  479. config NETFILTER_XT_MATCH_STATE
  480. tristate '"state" match support'
  481. depends on NETFILTER_XTABLES
  482. depends on NF_CONNTRACK
  483. help
  484. Connection state matching allows you to match packets based on their
  485. relationship to a tracked connection (ie. previous packets). This
  486. is a powerful tool for packet classification.
  487. To compile it as a module, choose M here. If unsure, say N.
  488. config NETFILTER_XT_MATCH_STATISTIC
  489. tristate '"statistic" match support'
  490. depends on NETFILTER_XTABLES
  491. help
  492. This option adds a `statistic' match, which allows you to match
  493. on packets periodically or randomly with a given percentage.
  494. To compile it as a module, choose M here. If unsure, say N.
  495. config NETFILTER_XT_MATCH_STRING
  496. tristate '"string" match support'
  497. depends on NETFILTER_XTABLES
  498. select TEXTSEARCH
  499. select TEXTSEARCH_KMP
  500. select TEXTSEARCH_BM
  501. select TEXTSEARCH_FSM
  502. help
  503. This option adds a `string' match, which allows you to look for
  504. pattern matchings in packets.
  505. To compile it as a module, choose M here. If unsure, say N.
  506. config NETFILTER_XT_MATCH_TCPMSS
  507. tristate '"tcpmss" match support'
  508. depends on NETFILTER_XTABLES
  509. help
  510. This option adds a `tcpmss' match, which allows you to examine the
  511. MSS value of TCP SYN packets, which control the maximum packet size
  512. for that connection.
  513. To compile it as a module, choose M here. If unsure, say N.
  514. config NETFILTER_XT_MATCH_HASHLIMIT
  515. tristate '"hashlimit" match support'
  516. depends on NETFILTER_XTABLES && (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
  517. help
  518. This option adds a `hashlimit' match.
  519. As opposed to `limit', this match dynamically creates a hash table
  520. of limit buckets, based on your selection of source/destination
  521. addresses and/or ports.
  522. It enables you to express policies like `10kpps for any given
  523. destination address' or `500pps from any given source address'
  524. with a single rule.
  525. endmenu