Kconfig 36 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992993994995996997998999100010011002100310041005100610071008100910101011101210131014101510161017101810191020102110221023102410251026102710281029103010311032103310341035103610371038103910401041104210431044
  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. depends on NETFILTER_ADVANCED
  8. select NETFILTER_NETLINK
  9. help
  10. If this option is enabled, the kernel will include support
  11. for queueing packets via NFNETLINK.
  12. config NETFILTER_NETLINK_LOG
  13. tristate "Netfilter LOG over NFNETLINK interface"
  14. default m if NETFILTER_ADVANCED=n
  15. select NETFILTER_NETLINK
  16. help
  17. If this option is enabled, the kernel will include support
  18. for logging packets via NFNETLINK.
  19. This obsoletes the existing ipt_ULOG and ebg_ulog mechanisms,
  20. and is also scheduled to replace the old syslog-based ipt_LOG
  21. and ip6t_LOG modules.
  22. config NF_CONNTRACK
  23. tristate "Netfilter connection tracking support"
  24. default m if NETFILTER_ADVANCED=n
  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. It can also be used to enhance packet
  31. filtering (see `Connection state match support' below).
  32. To compile it as a module, choose M here. If unsure, say N.
  33. if NF_CONNTRACK
  34. config NF_CONNTRACK_MARK
  35. bool 'Connection mark tracking support'
  36. depends on NETFILTER_ADVANCED
  37. help
  38. This option enables support for connection marks, used by the
  39. `CONNMARK' target and `connmark' match. Similar to the mark value
  40. of packets, but this mark value is kept in the conntrack session
  41. instead of the individual packets.
  42. config NF_CONNTRACK_SECMARK
  43. bool 'Connection tracking security mark support'
  44. depends on NETWORK_SECMARK
  45. default m if NETFILTER_ADVANCED=n
  46. help
  47. This option enables security markings to be applied to
  48. connections. Typically they are copied to connections from
  49. packets using the CONNSECMARK target and copied back from
  50. connections to packets with the same target, with the packets
  51. being originally labeled via SECMARK.
  52. If unsure, say 'N'.
  53. config NF_CONNTRACK_ZONES
  54. bool 'Connection tracking zones'
  55. depends on NETFILTER_ADVANCED
  56. depends on NETFILTER_XT_TARGET_CT
  57. help
  58. This option enables support for connection tracking zones.
  59. Normally, each connection needs to have a unique system wide
  60. identity. Connection tracking zones allow to have multiple
  61. connections using the same identity, as long as they are
  62. contained in different zones.
  63. If unsure, say `N'.
  64. config NF_CONNTRACK_EVENTS
  65. bool "Connection tracking events"
  66. depends on NETFILTER_ADVANCED
  67. help
  68. If this option is enabled, the connection tracking code will
  69. provide a notifier chain that can be used by other kernel code
  70. to get notified about changes in the connection tracking state.
  71. If unsure, say `N'.
  72. config NF_CT_PROTO_DCCP
  73. tristate 'DCCP protocol connection tracking support (EXPERIMENTAL)'
  74. depends on EXPERIMENTAL
  75. depends on NETFILTER_ADVANCED
  76. default IP_DCCP
  77. help
  78. With this option enabled, the layer 3 independent connection
  79. tracking code will be able to do state tracking on DCCP connections.
  80. If unsure, say 'N'.
  81. config NF_CT_PROTO_GRE
  82. tristate
  83. config NF_CT_PROTO_SCTP
  84. tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'
  85. depends on EXPERIMENTAL
  86. depends on NETFILTER_ADVANCED
  87. default IP_SCTP
  88. help
  89. With this option enabled, the layer 3 independent connection
  90. tracking code will be able to do state tracking on SCTP connections.
  91. If you want to compile it as a module, say M here and read
  92. <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
  93. config NF_CT_PROTO_UDPLITE
  94. tristate 'UDP-Lite protocol connection tracking support'
  95. depends on NETFILTER_ADVANCED
  96. help
  97. With this option enabled, the layer 3 independent connection
  98. tracking code will be able to do state tracking on UDP-Lite
  99. connections.
  100. To compile it as a module, choose M here. If unsure, say N.
  101. config NF_CONNTRACK_AMANDA
  102. tristate "Amanda backup protocol support"
  103. depends on NETFILTER_ADVANCED
  104. select TEXTSEARCH
  105. select TEXTSEARCH_KMP
  106. help
  107. If you are running the Amanda backup package <http://www.amanda.org/>
  108. on this machine or machines that will be MASQUERADED through this
  109. machine, then you may want to enable this feature. This allows the
  110. connection tracking and natting code to allow the sub-channels that
  111. Amanda requires for communication of the backup data, messages and
  112. index.
  113. To compile it as a module, choose M here. If unsure, say N.
  114. config NF_CONNTRACK_FTP
  115. tristate "FTP protocol support"
  116. default m if NETFILTER_ADVANCED=n
  117. help
  118. Tracking FTP connections is problematic: special helpers are
  119. required for tracking them, and doing masquerading and other forms
  120. of Network Address Translation on them.
  121. This is FTP support on Layer 3 independent connection tracking.
  122. Layer 3 independent connection tracking is experimental scheme
  123. which generalize ip_conntrack to support other layer 3 protocols.
  124. To compile it as a module, choose M here. If unsure, say N.
  125. config NF_CONNTRACK_H323
  126. tristate "H.323 protocol support"
  127. depends on (IPV6 || IPV6=n)
  128. depends on NETFILTER_ADVANCED
  129. help
  130. H.323 is a VoIP signalling protocol from ITU-T. As one of the most
  131. important VoIP protocols, it is widely used by voice hardware and
  132. software including voice gateways, IP phones, Netmeeting, OpenPhone,
  133. Gnomemeeting, etc.
  134. With this module you can support H.323 on a connection tracking/NAT
  135. firewall.
  136. This module supports RAS, Fast Start, H.245 Tunnelling, Call
  137. Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
  138. whiteboard, file transfer, etc. For more information, please
  139. visit http://nath323.sourceforge.net/.
  140. To compile it as a module, choose M here. If unsure, say N.
  141. config NF_CONNTRACK_IRC
  142. tristate "IRC protocol support"
  143. default m if NETFILTER_ADVANCED=n
  144. help
  145. There is a commonly-used extension to IRC called
  146. Direct Client-to-Client Protocol (DCC). This enables users to send
  147. files to each other, and also chat to each other without the need
  148. of a server. DCC Sending is used anywhere you send files over IRC,
  149. and DCC Chat is most commonly used by Eggdrop bots. If you are
  150. using NAT, this extension will enable you to send files and initiate
  151. chats. Note that you do NOT need this extension to get files or
  152. have others initiate chats, or everything else in IRC.
  153. To compile it as a module, choose M here. If unsure, say N.
  154. config NF_CONNTRACK_BROADCAST
  155. tristate
  156. config NF_CONNTRACK_NETBIOS_NS
  157. tristate "NetBIOS name service protocol support"
  158. depends on NETFILTER_ADVANCED
  159. select NF_CONNTRACK_BROADCAST
  160. help
  161. NetBIOS name service requests are sent as broadcast messages from an
  162. unprivileged port and responded to with unicast messages to the
  163. same port. This make them hard to firewall properly because connection
  164. tracking doesn't deal with broadcasts. This helper tracks locally
  165. originating NetBIOS name service requests and the corresponding
  166. responses. It relies on correct IP address configuration, specifically
  167. netmask and broadcast address. When properly configured, the output
  168. of "ip address show" should look similar to this:
  169. $ ip -4 address show eth0
  170. 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
  171. inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
  172. To compile it as a module, choose M here. If unsure, say N.
  173. config NF_CONNTRACK_SNMP
  174. tristate "SNMP service protocol support"
  175. depends on NETFILTER_ADVANCED
  176. select NF_CONNTRACK_BROADCAST
  177. help
  178. SNMP service requests are sent as broadcast messages from an
  179. unprivileged port and responded to with unicast messages to the
  180. same port. This make them hard to firewall properly because connection
  181. tracking doesn't deal with broadcasts. This helper tracks locally
  182. originating SNMP service requests and the corresponding
  183. responses. It relies on correct IP address configuration, specifically
  184. netmask and broadcast address.
  185. To compile it as a module, choose M here. If unsure, say N.
  186. config NF_CONNTRACK_PPTP
  187. tristate "PPtP protocol support"
  188. depends on NETFILTER_ADVANCED
  189. select NF_CT_PROTO_GRE
  190. help
  191. This module adds support for PPTP (Point to Point Tunnelling
  192. Protocol, RFC2637) connection tracking and NAT.
  193. If you are running PPTP sessions over a stateful firewall or NAT
  194. box, you may want to enable this feature.
  195. Please note that not all PPTP modes of operation are supported yet.
  196. Specifically these limitations exist:
  197. - Blindly assumes that control connections are always established
  198. in PNS->PAC direction. This is a violation of RFC2637.
  199. - Only supports a single call within each session
  200. To compile it as a module, choose M here. If unsure, say N.
  201. config NF_CONNTRACK_SANE
  202. tristate "SANE protocol support (EXPERIMENTAL)"
  203. depends on EXPERIMENTAL
  204. depends on NETFILTER_ADVANCED
  205. help
  206. SANE is a protocol for remote access to scanners as implemented
  207. by the 'saned' daemon. Like FTP, it uses separate control and
  208. data connections.
  209. With this module you can support SANE on a connection tracking
  210. firewall.
  211. To compile it as a module, choose M here. If unsure, say N.
  212. config NF_CONNTRACK_SIP
  213. tristate "SIP protocol support"
  214. default m if NETFILTER_ADVANCED=n
  215. help
  216. SIP is an application-layer control protocol that can establish,
  217. modify, and terminate multimedia sessions (conferences) such as
  218. Internet telephony calls. With the ip_conntrack_sip and
  219. the nf_nat_sip modules you can support the protocol on a connection
  220. tracking/NATing firewall.
  221. To compile it as a module, choose M here. If unsure, say N.
  222. config NF_CONNTRACK_TFTP
  223. tristate "TFTP protocol support"
  224. depends on NETFILTER_ADVANCED
  225. help
  226. TFTP connection tracking helper, this is required depending
  227. on how restrictive your ruleset is.
  228. If you are using a tftp client behind -j SNAT or -j MASQUERADING
  229. you will need this.
  230. To compile it as a module, choose M here. If unsure, say N.
  231. config NF_CT_NETLINK
  232. tristate 'Connection tracking netlink interface'
  233. select NETFILTER_NETLINK
  234. default m if NETFILTER_ADVANCED=n
  235. help
  236. This option enables support for a netlink-based userspace interface
  237. endif # NF_CONNTRACK
  238. # transparent proxy support
  239. config NETFILTER_TPROXY
  240. tristate "Transparent proxying support (EXPERIMENTAL)"
  241. depends on EXPERIMENTAL
  242. depends on IP_NF_MANGLE
  243. depends on NETFILTER_ADVANCED
  244. help
  245. This option enables transparent proxying support, that is,
  246. support for handling non-locally bound IPv4 TCP and UDP sockets.
  247. For it to work you will have to configure certain iptables rules
  248. and use policy routing. For more information on how to set it up
  249. see Documentation/networking/tproxy.txt.
  250. To compile it as a module, choose M here. If unsure, say N.
  251. config NETFILTER_XTABLES
  252. tristate "Netfilter Xtables support (required for ip_tables)"
  253. default m if NETFILTER_ADVANCED=n
  254. help
  255. This is required if you intend to use any of ip_tables,
  256. ip6_tables or arp_tables.
  257. if NETFILTER_XTABLES
  258. comment "Xtables combined modules"
  259. config NETFILTER_XT_MARK
  260. tristate 'nfmark target and match support'
  261. default m if NETFILTER_ADVANCED=n
  262. ---help---
  263. This option adds the "MARK" target and "mark" match.
  264. Netfilter mark matching allows you to match packets based on the
  265. "nfmark" value in the packet.
  266. The target allows you to create rules in the "mangle" table which alter
  267. the netfilter mark (nfmark) field associated with the packet.
  268. Prior to routing, the nfmark can influence the routing method (see
  269. "Use netfilter MARK value as routing key") and can also be used by
  270. other subsystems to change their behavior.
  271. config NETFILTER_XT_CONNMARK
  272. tristate 'ctmark target and match support'
  273. depends on NF_CONNTRACK
  274. depends on NETFILTER_ADVANCED
  275. select NF_CONNTRACK_MARK
  276. ---help---
  277. This option adds the "CONNMARK" target and "connmark" match.
  278. Netfilter allows you to store a mark value per connection (a.k.a.
  279. ctmark), similarly to the packet mark (nfmark). Using this
  280. target and match, you can set and match on this mark.
  281. # alphabetically ordered list of targets
  282. comment "Xtables targets"
  283. config NETFILTER_XT_TARGET_AUDIT
  284. tristate "AUDIT target support"
  285. depends on AUDIT
  286. depends on NETFILTER_ADVANCED
  287. ---help---
  288. This option adds a 'AUDIT' target, which can be used to create
  289. audit records for packets dropped/accepted.
  290. To compileit as a module, choose M here. If unsure, say N.
  291. config NETFILTER_XT_TARGET_CHECKSUM
  292. tristate "CHECKSUM target support"
  293. depends on IP_NF_MANGLE || IP6_NF_MANGLE
  294. depends on NETFILTER_ADVANCED
  295. ---help---
  296. This option adds a `CHECKSUM' target, which can be used in the iptables mangle
  297. table.
  298. You can use this target to compute and fill in the checksum in
  299. a packet that lacks a checksum. This is particularly useful,
  300. if you need to work around old applications such as dhcp clients,
  301. that do not work well with checksum offloads, but don't want to disable
  302. checksum offload in your device.
  303. To compile it as a module, choose M here. If unsure, say N.
  304. config NETFILTER_XT_TARGET_CLASSIFY
  305. tristate '"CLASSIFY" target support'
  306. depends on NETFILTER_ADVANCED
  307. help
  308. This option adds a `CLASSIFY' target, which enables the user to set
  309. the priority of a packet. Some qdiscs can use this value for
  310. classification, among these are:
  311. atm, cbq, dsmark, pfifo_fast, htb, prio
  312. To compile it as a module, choose M here. If unsure, say N.
  313. config NETFILTER_XT_TARGET_CONNMARK
  314. tristate '"CONNMARK" target support'
  315. depends on NF_CONNTRACK
  316. depends on NETFILTER_ADVANCED
  317. select NETFILTER_XT_CONNMARK
  318. ---help---
  319. This is a backwards-compat option for the user's convenience
  320. (e.g. when running oldconfig). It selects
  321. CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
  322. config NETFILTER_XT_TARGET_CONNSECMARK
  323. tristate '"CONNSECMARK" target support'
  324. depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
  325. default m if NETFILTER_ADVANCED=n
  326. help
  327. The CONNSECMARK target copies security markings from packets
  328. to connections, and restores security markings from connections
  329. to packets (if the packets are not already marked). This would
  330. normally be used in conjunction with the SECMARK target.
  331. To compile it as a module, choose M here. If unsure, say N.
  332. config NETFILTER_XT_TARGET_CT
  333. tristate '"CT" target support'
  334. depends on NF_CONNTRACK
  335. depends on IP_NF_RAW || IP6_NF_RAW
  336. depends on NETFILTER_ADVANCED
  337. help
  338. This options adds a `CT' target, which allows to specify initial
  339. connection tracking parameters like events to be delivered and
  340. the helper to be used.
  341. To compile it as a module, choose M here. If unsure, say N.
  342. config NETFILTER_XT_TARGET_DSCP
  343. tristate '"DSCP" and "TOS" target support'
  344. depends on IP_NF_MANGLE || IP6_NF_MANGLE
  345. depends on NETFILTER_ADVANCED
  346. help
  347. This option adds a `DSCP' target, which allows you to manipulate
  348. the IPv4/IPv6 header DSCP field (differentiated services codepoint).
  349. The DSCP field can have any value between 0x0 and 0x3f inclusive.
  350. It also adds the "TOS" target, which allows you to create rules in
  351. the "mangle" table which alter the Type Of Service field of an IPv4
  352. or the Priority field of an IPv6 packet, prior to routing.
  353. To compile it as a module, choose M here. If unsure, say N.
  354. config NETFILTER_XT_TARGET_HL
  355. tristate '"HL" hoplimit target support'
  356. depends on IP_NF_MANGLE || IP6_NF_MANGLE
  357. depends on NETFILTER_ADVANCED
  358. ---help---
  359. This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
  360. targets, which enable the user to change the
  361. hoplimit/time-to-live value of the IP header.
  362. While it is safe to decrement the hoplimit/TTL value, the
  363. modules also allow to increment and set the hoplimit value of
  364. the header to arbitrary values. This is EXTREMELY DANGEROUS
  365. since you can easily create immortal packets that loop
  366. forever on the network.
  367. config NETFILTER_XT_TARGET_IDLETIMER
  368. tristate "IDLETIMER target support"
  369. depends on NETFILTER_ADVANCED
  370. help
  371. This option adds the `IDLETIMER' target. Each matching packet
  372. resets the timer associated with label specified when the rule is
  373. added. When the timer expires, it triggers a sysfs notification.
  374. The remaining time for expiration can be read via sysfs.
  375. To compile it as a module, choose M here. If unsure, say N.
  376. config NETFILTER_XT_TARGET_LED
  377. tristate '"LED" target support'
  378. depends on LEDS_CLASS && LEDS_TRIGGERS
  379. depends on NETFILTER_ADVANCED
  380. help
  381. This option adds a `LED' target, which allows you to blink LEDs in
  382. response to particular packets passing through your machine.
  383. This can be used to turn a spare LED into a network activity LED,
  384. which only flashes in response to FTP transfers, for example. Or
  385. you could have an LED which lights up for a minute or two every time
  386. somebody connects to your machine via SSH.
  387. You will need support for the "led" class to make this work.
  388. To create an LED trigger for incoming SSH traffic:
  389. iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
  390. Then attach the new trigger to an LED on your system:
  391. echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
  392. For more information on the LEDs available on your system, see
  393. Documentation/leds-class.txt
  394. config NETFILTER_XT_TARGET_MARK
  395. tristate '"MARK" target support'
  396. depends on NETFILTER_ADVANCED
  397. select NETFILTER_XT_MARK
  398. ---help---
  399. This is a backwards-compat option for the user's convenience
  400. (e.g. when running oldconfig). It selects
  401. CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
  402. config NETFILTER_XT_TARGET_NFLOG
  403. tristate '"NFLOG" target support'
  404. default m if NETFILTER_ADVANCED=n
  405. select NETFILTER_NETLINK_LOG
  406. help
  407. This option enables the NFLOG target, which allows to LOG
  408. messages through nfnetlink_log.
  409. To compile it as a module, choose M here. If unsure, say N.
  410. config NETFILTER_XT_TARGET_NFQUEUE
  411. tristate '"NFQUEUE" target Support'
  412. depends on NETFILTER_ADVANCED
  413. select NETFILTER_NETLINK_QUEUE
  414. help
  415. This target replaced the old obsolete QUEUE target.
  416. As opposed to QUEUE, it supports 65535 different queues,
  417. not just one.
  418. To compile it as a module, choose M here. If unsure, say N.
  419. config NETFILTER_XT_TARGET_NOTRACK
  420. tristate '"NOTRACK" target support'
  421. depends on IP_NF_RAW || IP6_NF_RAW
  422. depends on NF_CONNTRACK
  423. depends on NETFILTER_ADVANCED
  424. help
  425. The NOTRACK target allows a select rule to specify
  426. which packets *not* to enter the conntrack/NAT
  427. subsystem with all the consequences (no ICMP error tracking,
  428. no protocol helpers for the selected packets).
  429. If you want to compile it as a module, say M here and read
  430. <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
  431. config NETFILTER_XT_TARGET_RATEEST
  432. tristate '"RATEEST" target support'
  433. depends on NETFILTER_ADVANCED
  434. help
  435. This option adds a `RATEEST' target, which allows to measure
  436. rates similar to TC estimators. The `rateest' match can be
  437. used to match on the measured rates.
  438. To compile it as a module, choose M here. If unsure, say N.
  439. config NETFILTER_XT_TARGET_TEE
  440. tristate '"TEE" - packet cloning to alternate destination'
  441. depends on NETFILTER_ADVANCED
  442. depends on (IPV6 || IPV6=n)
  443. depends on !NF_CONNTRACK || NF_CONNTRACK
  444. ---help---
  445. This option adds a "TEE" target with which a packet can be cloned and
  446. this clone be rerouted to another nexthop.
  447. config NETFILTER_XT_TARGET_TPROXY
  448. tristate '"TPROXY" target support (EXPERIMENTAL)'
  449. depends on EXPERIMENTAL
  450. depends on NETFILTER_TPROXY
  451. depends on NETFILTER_XTABLES
  452. depends on NETFILTER_ADVANCED
  453. select NF_DEFRAG_IPV4
  454. select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
  455. help
  456. This option adds a `TPROXY' target, which is somewhat similar to
  457. REDIRECT. It can only be used in the mangle table and is useful
  458. to redirect traffic to a transparent proxy. It does _not_ depend
  459. on Netfilter connection tracking and NAT, unlike REDIRECT.
  460. To compile it as a module, choose M here. If unsure, say N.
  461. config NETFILTER_XT_TARGET_TRACE
  462. tristate '"TRACE" target support'
  463. depends on IP_NF_RAW || IP6_NF_RAW
  464. depends on NETFILTER_ADVANCED
  465. help
  466. The TRACE target allows you to mark packets so that the kernel
  467. will log every rule which match the packets as those traverse
  468. the tables, chains, rules.
  469. If you want to compile it as a module, say M here and read
  470. <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
  471. config NETFILTER_XT_TARGET_SECMARK
  472. tristate '"SECMARK" target support'
  473. depends on NETWORK_SECMARK
  474. default m if NETFILTER_ADVANCED=n
  475. help
  476. The SECMARK target allows security marking of network
  477. packets, for use with security subsystems.
  478. To compile it as a module, choose M here. If unsure, say N.
  479. config NETFILTER_XT_TARGET_TCPMSS
  480. tristate '"TCPMSS" target support'
  481. depends on (IPV6 || IPV6=n)
  482. default m if NETFILTER_ADVANCED=n
  483. ---help---
  484. This option adds a `TCPMSS' target, which allows you to alter the
  485. MSS value of TCP SYN packets, to control the maximum size for that
  486. connection (usually limiting it to your outgoing interface's MTU
  487. minus 40).
  488. This is used to overcome criminally braindead ISPs or servers which
  489. block ICMP Fragmentation Needed packets. The symptoms of this
  490. problem are that everything works fine from your Linux
  491. firewall/router, but machines behind it can never exchange large
  492. packets:
  493. 1) Web browsers connect, then hang with no data received.
  494. 2) Small mail works fine, but large emails hang.
  495. 3) ssh works fine, but scp hangs after initial handshaking.
  496. Workaround: activate this option and add a rule to your firewall
  497. configuration like:
  498. iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
  499. -j TCPMSS --clamp-mss-to-pmtu
  500. To compile it as a module, choose M here. If unsure, say N.
  501. config NETFILTER_XT_TARGET_TCPOPTSTRIP
  502. tristate '"TCPOPTSTRIP" target support (EXPERIMENTAL)'
  503. depends on EXPERIMENTAL
  504. depends on IP_NF_MANGLE || IP6_NF_MANGLE
  505. depends on NETFILTER_ADVANCED
  506. help
  507. This option adds a "TCPOPTSTRIP" target, which allows you to strip
  508. TCP options from TCP packets.
  509. # alphabetically ordered list of matches
  510. comment "Xtables matches"
  511. config NETFILTER_XT_MATCH_CLUSTER
  512. tristate '"cluster" match support'
  513. depends on NF_CONNTRACK
  514. depends on NETFILTER_ADVANCED
  515. ---help---
  516. This option allows you to build work-load-sharing clusters of
  517. network servers/stateful firewalls without having a dedicated
  518. load-balancing router/server/switch. Basically, this match returns
  519. true when the packet must be handled by this cluster node. Thus,
  520. all nodes see all packets and this match decides which node handles
  521. what packets. The work-load sharing algorithm is based on source
  522. address hashing.
  523. If you say Y or M here, try `iptables -m cluster --help` for
  524. more information.
  525. config NETFILTER_XT_MATCH_COMMENT
  526. tristate '"comment" match support'
  527. depends on NETFILTER_ADVANCED
  528. help
  529. This option adds a `comment' dummy-match, which allows you to put
  530. comments in your iptables ruleset.
  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_CONNBYTES
  534. tristate '"connbytes" per-connection counter match support'
  535. depends on NF_CONNTRACK
  536. depends on NETFILTER_ADVANCED
  537. help
  538. This option adds a `connbytes' match, which allows you to match the
  539. number of bytes and/or packets for each direction within a connection.
  540. If you want to compile it as a module, say M here and read
  541. <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
  542. config NETFILTER_XT_MATCH_CONNLIMIT
  543. tristate '"connlimit" match support"'
  544. depends on NF_CONNTRACK
  545. depends on NETFILTER_ADVANCED
  546. ---help---
  547. This match allows you to match against the number of parallel
  548. connections to a server per client IP address (or address block).
  549. config NETFILTER_XT_MATCH_CONNMARK
  550. tristate '"connmark" connection mark match support'
  551. depends on NF_CONNTRACK
  552. depends on NETFILTER_ADVANCED
  553. select NETFILTER_XT_CONNMARK
  554. ---help---
  555. This is a backwards-compat option for the user's convenience
  556. (e.g. when running oldconfig). It selects
  557. CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
  558. config NETFILTER_XT_MATCH_CONNTRACK
  559. tristate '"conntrack" connection tracking match support'
  560. depends on NF_CONNTRACK
  561. default m if NETFILTER_ADVANCED=n
  562. help
  563. This is a general conntrack match module, a superset of the state match.
  564. It allows matching on additional conntrack information, which is
  565. useful in complex configurations, such as NAT gateways with multiple
  566. internet links or tunnels.
  567. To compile it as a module, choose M here. If unsure, say N.
  568. config NETFILTER_XT_MATCH_CPU
  569. tristate '"cpu" match support'
  570. depends on NETFILTER_ADVANCED
  571. help
  572. CPU matching allows you to match packets based on the CPU
  573. currently handling the packet.
  574. To compile it as a module, choose M here. If unsure, say N.
  575. config NETFILTER_XT_MATCH_DCCP
  576. tristate '"dccp" protocol match support'
  577. depends on NETFILTER_ADVANCED
  578. default IP_DCCP
  579. help
  580. With this option enabled, you will be able to use the iptables
  581. `dccp' match in order to match on DCCP source/destination ports
  582. and DCCP flags.
  583. If you want to compile it as a module, say M here and read
  584. <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
  585. config NETFILTER_XT_MATCH_DSCP
  586. tristate '"dscp" and "tos" match support'
  587. depends on NETFILTER_ADVANCED
  588. help
  589. This option adds a `DSCP' match, which allows you to match against
  590. the IPv4/IPv6 header DSCP field (differentiated services codepoint).
  591. The DSCP field can have any value between 0x0 and 0x3f inclusive.
  592. It will also add a "tos" match, which allows you to match packets
  593. based on the Type Of Service fields of the IPv4 packet (which share
  594. the same bits as DSCP).
  595. To compile it as a module, choose M here. If unsure, say N.
  596. config NETFILTER_XT_MATCH_ESP
  597. tristate '"esp" match support'
  598. depends on NETFILTER_ADVANCED
  599. help
  600. This match extension allows you to match a range of SPIs
  601. inside ESP header of IPSec packets.
  602. To compile it as a module, choose M here. If unsure, say N.
  603. config NETFILTER_XT_MATCH_HASHLIMIT
  604. tristate '"hashlimit" match support'
  605. depends on (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
  606. depends on NETFILTER_ADVANCED
  607. help
  608. This option adds a `hashlimit' match.
  609. As opposed to `limit', this match dynamically creates a hash table
  610. of limit buckets, based on your selection of source/destination
  611. addresses and/or ports.
  612. It enables you to express policies like `10kpps for any given
  613. destination address' or `500pps from any given source address'
  614. with a single rule.
  615. config NETFILTER_XT_MATCH_HELPER
  616. tristate '"helper" match support'
  617. depends on NF_CONNTRACK
  618. depends on NETFILTER_ADVANCED
  619. help
  620. Helper matching allows you to match packets in dynamic connections
  621. tracked by a conntrack-helper, ie. ip_conntrack_ftp
  622. To compile it as a module, choose M here. If unsure, say Y.
  623. config NETFILTER_XT_MATCH_HL
  624. tristate '"hl" hoplimit/TTL match support'
  625. depends on NETFILTER_ADVANCED
  626. ---help---
  627. HL matching allows you to match packets based on the hoplimit
  628. in the IPv6 header, or the time-to-live field in the IPv4
  629. header of the packet.
  630. config NETFILTER_XT_MATCH_IPRANGE
  631. tristate '"iprange" address range match support'
  632. depends on NETFILTER_ADVANCED
  633. ---help---
  634. This option adds a "iprange" match, which allows you to match based on
  635. an IP address range. (Normal iptables only matches on single addresses
  636. with an optional mask.)
  637. If unsure, say M.
  638. config NETFILTER_XT_MATCH_IPVS
  639. tristate '"ipvs" match support'
  640. depends on IP_VS
  641. depends on NETFILTER_ADVANCED
  642. depends on NF_CONNTRACK
  643. help
  644. This option allows you to match against IPVS properties of a packet.
  645. If unsure, say N.
  646. config NETFILTER_XT_MATCH_LENGTH
  647. tristate '"length" match support'
  648. depends on NETFILTER_ADVANCED
  649. help
  650. This option allows you to match the length of a packet against a
  651. specific value or range of values.
  652. To compile it as a module, choose M here. If unsure, say N.
  653. config NETFILTER_XT_MATCH_LIMIT
  654. tristate '"limit" match support'
  655. depends on NETFILTER_ADVANCED
  656. help
  657. limit matching allows you to control the rate at which a rule can be
  658. matched: mainly useful in combination with the LOG target ("LOG
  659. target support", below) and to avoid some Denial of Service attacks.
  660. To compile it as a module, choose M here. If unsure, say N.
  661. config NETFILTER_XT_MATCH_MAC
  662. tristate '"mac" address match support'
  663. depends on NETFILTER_ADVANCED
  664. help
  665. MAC matching allows you to match packets based on the source
  666. Ethernet address of the packet.
  667. To compile it as a module, choose M here. If unsure, say N.
  668. config NETFILTER_XT_MATCH_MARK
  669. tristate '"mark" match support'
  670. depends on NETFILTER_ADVANCED
  671. select NETFILTER_XT_MARK
  672. ---help---
  673. This is a backwards-compat option for the user's convenience
  674. (e.g. when running oldconfig). It selects
  675. CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
  676. config NETFILTER_XT_MATCH_MULTIPORT
  677. tristate '"multiport" Multiple port match support'
  678. depends on NETFILTER_ADVANCED
  679. help
  680. Multiport matching allows you to match TCP or UDP packets based on
  681. a series of source or destination ports: normally a rule can only
  682. match a single range of ports.
  683. To compile it as a module, choose M here. If unsure, say N.
  684. config NETFILTER_XT_MATCH_OSF
  685. tristate '"osf" Passive OS fingerprint match'
  686. depends on NETFILTER_ADVANCED && NETFILTER_NETLINK
  687. help
  688. This option selects the Passive OS Fingerprinting match module
  689. that allows to passively match the remote operating system by
  690. analyzing incoming TCP SYN packets.
  691. Rules and loading software can be downloaded from
  692. http://www.ioremap.net/projects/osf
  693. To compile it as a module, choose M here. If unsure, say N.
  694. config NETFILTER_XT_MATCH_OWNER
  695. tristate '"owner" match support'
  696. depends on NETFILTER_ADVANCED
  697. ---help---
  698. Socket owner matching allows you to match locally-generated packets
  699. based on who created the socket: the user or group. It is also
  700. possible to check whether a socket actually exists.
  701. config NETFILTER_XT_MATCH_POLICY
  702. tristate 'IPsec "policy" match support'
  703. depends on XFRM
  704. default m if NETFILTER_ADVANCED=n
  705. help
  706. Policy matching allows you to match packets based on the
  707. IPsec policy that was used during decapsulation/will
  708. be used during encapsulation.
  709. To compile it as a module, choose M here. If unsure, say N.
  710. config NETFILTER_XT_MATCH_PHYSDEV
  711. tristate '"physdev" match support'
  712. depends on BRIDGE && BRIDGE_NETFILTER
  713. depends on NETFILTER_ADVANCED
  714. help
  715. Physdev packet matching matches against the physical bridge ports
  716. the IP packet arrived on or will leave by.
  717. To compile it as a module, choose M here. If unsure, say N.
  718. config NETFILTER_XT_MATCH_PKTTYPE
  719. tristate '"pkttype" packet type match support'
  720. depends on NETFILTER_ADVANCED
  721. help
  722. Packet type matching allows you to match a packet by
  723. its "class", eg. BROADCAST, MULTICAST, ...
  724. Typical usage:
  725. iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
  726. To compile it as a module, choose M here. If unsure, say N.
  727. config NETFILTER_XT_MATCH_QUOTA
  728. tristate '"quota" match support'
  729. depends on NETFILTER_ADVANCED
  730. help
  731. This option adds a `quota' match, which allows to match on a
  732. byte counter.
  733. If you want to compile it as a module, say M here and read
  734. <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
  735. config NETFILTER_XT_MATCH_RATEEST
  736. tristate '"rateest" match support'
  737. depends on NETFILTER_ADVANCED
  738. select NETFILTER_XT_TARGET_RATEEST
  739. help
  740. This option adds a `rateest' match, which allows to match on the
  741. rate estimated by the RATEEST target.
  742. To compile it as a module, choose M here. If unsure, say N.
  743. config NETFILTER_XT_MATCH_REALM
  744. tristate '"realm" match support'
  745. depends on NETFILTER_ADVANCED
  746. select IP_ROUTE_CLASSID
  747. help
  748. This option adds a `realm' match, which allows you to use the realm
  749. key from the routing subsystem inside iptables.
  750. This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
  751. in tc world.
  752. If you want to compile it as a module, say M here and read
  753. <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
  754. config NETFILTER_XT_MATCH_RECENT
  755. tristate '"recent" match support'
  756. depends on NETFILTER_ADVANCED
  757. ---help---
  758. This match is used for creating one or many lists of recently
  759. used addresses and then matching against that/those list(s).
  760. Short options are available by using 'iptables -m recent -h'
  761. Official Website: <http://snowman.net/projects/ipt_recent/>
  762. config NETFILTER_XT_MATCH_SCTP
  763. tristate '"sctp" protocol match support (EXPERIMENTAL)'
  764. depends on EXPERIMENTAL
  765. depends on NETFILTER_ADVANCED
  766. default IP_SCTP
  767. help
  768. With this option enabled, you will be able to use the
  769. `sctp' match in order to match on SCTP source/destination ports
  770. and SCTP chunk types.
  771. If you want to compile it as a module, say M here and read
  772. <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
  773. config NETFILTER_XT_MATCH_SOCKET
  774. tristate '"socket" match support (EXPERIMENTAL)'
  775. depends on EXPERIMENTAL
  776. depends on NETFILTER_TPROXY
  777. depends on NETFILTER_XTABLES
  778. depends on NETFILTER_ADVANCED
  779. depends on !NF_CONNTRACK || NF_CONNTRACK
  780. select NF_DEFRAG_IPV4
  781. select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES
  782. help
  783. This option adds a `socket' match, which can be used to match
  784. packets for which a TCP or UDP socket lookup finds a valid socket.
  785. It can be used in combination with the MARK target and policy
  786. routing to implement full featured non-locally bound sockets.
  787. To compile it as a module, choose M here. If unsure, say N.
  788. config NETFILTER_XT_MATCH_STATE
  789. tristate '"state" match support'
  790. depends on NF_CONNTRACK
  791. default m if NETFILTER_ADVANCED=n
  792. help
  793. Connection state matching allows you to match packets based on their
  794. relationship to a tracked connection (ie. previous packets). This
  795. is a powerful tool for packet classification.
  796. To compile it as a module, choose M here. If unsure, say N.
  797. config NETFILTER_XT_MATCH_STATISTIC
  798. tristate '"statistic" match support'
  799. depends on NETFILTER_ADVANCED
  800. help
  801. This option adds a `statistic' match, which allows you to match
  802. on packets periodically or randomly with a given percentage.
  803. To compile it as a module, choose M here. If unsure, say N.
  804. config NETFILTER_XT_MATCH_STRING
  805. tristate '"string" match support'
  806. depends on NETFILTER_ADVANCED
  807. select TEXTSEARCH
  808. select TEXTSEARCH_KMP
  809. select TEXTSEARCH_BM
  810. select TEXTSEARCH_FSM
  811. help
  812. This option adds a `string' match, which allows you to look for
  813. pattern matchings in packets.
  814. To compile it as a module, choose M here. If unsure, say N.
  815. config NETFILTER_XT_MATCH_TCPMSS
  816. tristate '"tcpmss" match support'
  817. depends on NETFILTER_ADVANCED
  818. help
  819. This option adds a `tcpmss' match, which allows you to examine the
  820. MSS value of TCP SYN packets, which control the maximum packet size
  821. for that connection.
  822. To compile it as a module, choose M here. If unsure, say N.
  823. config NETFILTER_XT_MATCH_TIME
  824. tristate '"time" match support'
  825. depends on NETFILTER_ADVANCED
  826. ---help---
  827. This option adds a "time" match, which allows you to match based on
  828. the packet arrival time (at the machine which netfilter is running)
  829. on) or departure time/date (for locally generated packets).
  830. If you say Y here, try `iptables -m time --help` for
  831. more information.
  832. If you want to compile it as a module, say M here.
  833. If unsure, say N.
  834. config NETFILTER_XT_MATCH_U32
  835. tristate '"u32" match support'
  836. depends on NETFILTER_ADVANCED
  837. ---help---
  838. u32 allows you to extract quantities of up to 4 bytes from a packet,
  839. AND them with specified masks, shift them by specified amounts and
  840. test whether the results are in any of a set of specified ranges.
  841. The specification of what to extract is general enough to skip over
  842. headers with lengths stored in the packet, as in IP or TCP header
  843. lengths.
  844. Details and examples are in the kernel module source.
  845. endif # NETFILTER_XTABLES
  846. endmenu
  847. source "net/netfilter/ipvs/Kconfig"