Kconfig 26 KB

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