Kconfig 24 KB

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