Kconfig 53 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697989910010110210310410510610710810911011111211311411511611711811912012112212312412512612712812913013113213313413513613713813914014114214314414514614714814915015115215315415515615715815916016116216316416516616716816917017117217317417517617717817918018118218318418518618718818919019119219319419519619719819920020120220320420520620720820921021121221321421521621721821922022122222322422522622722822923023123223323423523623723823924024124224324424524624724824925025125225325425525625725825926026126226326426526626726826927027127227327427527627727827928028128228328428528628728828929029129229329429529629729829930030130230330430530630730830931031131231331431531631731831932032132232332432532632732832933033133233333433533633733833934034134234334434534634734834935035135235335435535635735835936036136236336436536636736836937037137237337437537637737837938038138238338438538638738838939039139239339439539639739839940040140240340440540640740840941041141241341441541641741841942042142242342442542642742842943043143243343443543643743843944044144244344444544644744844945045145245345445545645745845946046146246346446546646746846947047147247347447547647747847948048148248348448548648748848949049149249349449549649749849950050150250350450550650750850951051151251351451551651751851952052152252352452552652752852953053153253353453553653753853954054154254354454554654754854955055155255355455555655755855956056156256356456556656756856957057157257357457557657757857958058158258358458558658758858959059159259359459559659759859960060160260360460560660760860961061161261361461561661761861962062162262362462562662762862963063163263363463563663763863964064164264364464564664764864965065165265365465565665765865966066166266366466566666766866967067167267367467567667767867968068168268368468568668768868969069169269369469569669769869970070170270370470570670770870971071171271371471571671771871972072172272372472572672772872973073173273373473573673773873974074174274374474574674774874975075175275375475575675775875976076176276376476576676776876977077177277377477577677777877978078178278378478578678778878979079179279379479579679779879980080180280380480580680780880981081181281381481581681781881982082182282382482582682782882983083183283383483583683783883984084184284384484584684784884985085185285385485585685785885986086186286386486586686786886987087187287387487587687787887988088188288388488588688788888989089189289389489589689789889990090190290390490590690790890991091191291391491591691791891992092192292392492592692792892993093193293393493593693793893994094194294394494594694794894995095195295395495595695795895996096196296396496596696796896997097197297397497597697797897998098198298398498598698798898999099199299399499599699799899910001001100210031004100510061007100810091010101110121013101410151016101710181019102010211022102310241025102610271028102910301031103210331034103510361037103810391040104110421043104410451046104710481049105010511052105310541055105610571058105910601061106210631064106510661067106810691070107110721073107410751076107710781079108010811082108310841085108610871088108910901091109210931094109510961097109810991100110111021103110411051106110711081109111011111112111311141115111611171118111911201121112211231124112511261127112811291130113111321133113411351136113711381139114011411142114311441145114611471148114911501151115211531154115511561157115811591160116111621163116411651166116711681169117011711172117311741175117611771178117911801181118211831184118511861187118811891190119111921193119411951196119711981199120012011202120312041205120612071208120912101211121212131214121512161217121812191220122112221223122412251226122712281229123012311232123312341235123612371238123912401241124212431244124512461247124812491250125112521253125412551256125712581259126012611262126312641265126612671268126912701271127212731274127512761277127812791280128112821283128412851286128712881289129012911292129312941295129612971298129913001301130213031304130513061307130813091310131113121313131413151316131713181319132013211322132313241325132613271328132913301331133213331334133513361337133813391340134113421343134413451346134713481349135013511352135313541355135613571358135913601361136213631364136513661367136813691370137113721373137413751376137713781379138013811382138313841385138613871388138913901391139213931394139513961397139813991400140114021403140414051406140714081409141014111412141314141415141614171418141914201421142214231424142514261427142814291430143114321433143414351436143714381439144014411442144314441445144614471448144914501451145214531454145514561457145814591460146114621463146414651466146714681469147014711472147314741475147614771478147914801481148214831484148514861487148814891490149114921493149414951496149714981499150015011502150315041505150615071508150915101511151215131514151515161517151815191520152115221523152415251526152715281529153015311532153315341535153615371538153915401541154215431544154515461547154815491550155115521553155415551556155715581559156015611562156315641565156615671568156915701571157215731574157515761577157815791580158115821583158415851586158715881589159015911592159315941595159615971598159916001601160216031604160516061607160816091610161116121613161416151616161716181619162016211622162316241625162616271628162916301631163216331634163516361637163816391640164116421643
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. menu "Core Netfilter Configuration"
  3. depends on NET && INET && NETFILTER
  4. config NETFILTER_INGRESS
  5. bool "Netfilter ingress support"
  6. default y
  7. select NET_INGRESS
  8. help
  9. This allows you to classify packets from ingress using the Netfilter
  10. infrastructure.
  11. config NETFILTER_NETLINK
  12. tristate
  13. config NETFILTER_FAMILY_BRIDGE
  14. bool
  15. config NETFILTER_FAMILY_ARP
  16. bool
  17. config NETFILTER_NETLINK_ACCT
  18. tristate "Netfilter NFACCT over NFNETLINK interface"
  19. depends on NETFILTER_ADVANCED
  20. select NETFILTER_NETLINK
  21. help
  22. If this option is enabled, the kernel will include support
  23. for extended accounting via NFNETLINK.
  24. config NETFILTER_NETLINK_QUEUE
  25. tristate "Netfilter NFQUEUE over NFNETLINK interface"
  26. depends on NETFILTER_ADVANCED
  27. select NETFILTER_NETLINK
  28. help
  29. If this option is enabled, the kernel will include support
  30. for queueing packets via NFNETLINK.
  31. config NETFILTER_NETLINK_LOG
  32. tristate "Netfilter LOG over NFNETLINK interface"
  33. default m if NETFILTER_ADVANCED=n
  34. select NETFILTER_NETLINK
  35. help
  36. If this option is enabled, the kernel will include support
  37. for logging packets via NFNETLINK.
  38. This obsoletes the existing ipt_ULOG and ebg_ulog mechanisms,
  39. and is also scheduled to replace the old syslog-based ipt_LOG
  40. and ip6t_LOG modules.
  41. config NETFILTER_NETLINK_OSF
  42. tristate "Netfilter OSF over NFNETLINK interface"
  43. depends on NETFILTER_ADVANCED
  44. select NETFILTER_NETLINK
  45. help
  46. If this option is enabled, the kernel will include support
  47. for passive OS fingerprint via NFNETLINK.
  48. config NF_CONNTRACK
  49. tristate "Netfilter connection tracking support"
  50. default m if NETFILTER_ADVANCED=n
  51. select NF_DEFRAG_IPV4
  52. select NF_DEFRAG_IPV6 if IPV6 != n
  53. help
  54. Connection tracking keeps a record of what packets have passed
  55. through your machine, in order to figure out how they are related
  56. into connections.
  57. This is required to do Masquerading or other kinds of Network
  58. Address Translation. It can also be used to enhance packet
  59. filtering (see `Connection state match support' below).
  60. To compile it as a module, choose M here. If unsure, say N.
  61. config NF_LOG_COMMON
  62. tristate
  63. config NF_LOG_NETDEV
  64. tristate "Netdev packet logging"
  65. select NF_LOG_COMMON
  66. if NF_CONNTRACK
  67. config NETFILTER_CONNCOUNT
  68. tristate
  69. config NF_CONNTRACK_MARK
  70. bool 'Connection mark tracking support'
  71. depends on NETFILTER_ADVANCED
  72. help
  73. This option enables support for connection marks, used by the
  74. `CONNMARK' target and `connmark' match. Similar to the mark value
  75. of packets, but this mark value is kept in the conntrack session
  76. instead of the individual packets.
  77. config NF_CONNTRACK_SECMARK
  78. bool 'Connection tracking security mark support'
  79. depends on NETWORK_SECMARK
  80. default y if NETFILTER_ADVANCED=n
  81. help
  82. This option enables security markings to be applied to
  83. connections. Typically they are copied to connections from
  84. packets using the CONNSECMARK target and copied back from
  85. connections to packets with the same target, with the packets
  86. being originally labeled via SECMARK.
  87. If unsure, say 'N'.
  88. config NF_CONNTRACK_ZONES
  89. bool 'Connection tracking zones'
  90. depends on NETFILTER_ADVANCED
  91. help
  92. This option enables support for connection tracking zones.
  93. Normally, each connection needs to have a unique system wide
  94. identity. Connection tracking zones allow to have multiple
  95. connections using the same identity, as long as they are
  96. contained in different zones.
  97. If unsure, say `N'.
  98. config NF_CONNTRACK_PROCFS
  99. bool "Supply CT list in procfs (OBSOLETE)"
  100. default y
  101. depends on PROC_FS
  102. help
  103. This option enables for the list of known conntrack entries
  104. to be shown in procfs under net/netfilter/nf_conntrack. This
  105. is considered obsolete in favor of using the conntrack(8)
  106. tool which uses Netlink.
  107. config NF_CONNTRACK_EVENTS
  108. bool "Connection tracking events"
  109. depends on NETFILTER_ADVANCED
  110. help
  111. If this option is enabled, the connection tracking code will
  112. provide a notifier chain that can be used by other kernel code
  113. to get notified about changes in the connection tracking state.
  114. If unsure, say `N'.
  115. config NF_CONNTRACK_TIMEOUT
  116. bool 'Connection tracking timeout'
  117. depends on NETFILTER_ADVANCED
  118. help
  119. This option enables support for connection tracking timeout
  120. extension. This allows you to attach timeout policies to flow
  121. via the CT target.
  122. If unsure, say `N'.
  123. config NF_CONNTRACK_TIMESTAMP
  124. bool 'Connection tracking timestamping'
  125. depends on NETFILTER_ADVANCED
  126. help
  127. This option enables support for connection tracking timestamping.
  128. This allows you to store the flow start-time and to obtain
  129. the flow-stop time (once it has been destroyed) via Connection
  130. tracking events.
  131. If unsure, say `N'.
  132. config NF_CONNTRACK_LABELS
  133. bool "Connection tracking labels"
  134. help
  135. This option enables support for assigning user-defined flag bits
  136. to connection tracking entries. It can be used with xtables connlabel
  137. match and the nftables ct expression.
  138. config NF_CT_PROTO_DCCP
  139. bool 'DCCP protocol connection tracking support'
  140. depends on NETFILTER_ADVANCED
  141. default y
  142. help
  143. With this option enabled, the layer 3 independent connection
  144. tracking code will be able to do state tracking on DCCP connections.
  145. If unsure, say Y.
  146. config NF_CT_PROTO_GRE
  147. bool
  148. config NF_CT_PROTO_SCTP
  149. bool 'SCTP protocol connection tracking support'
  150. depends on NETFILTER_ADVANCED
  151. default y
  152. select LIBCRC32C
  153. help
  154. With this option enabled, the layer 3 independent connection
  155. tracking code will be able to do state tracking on SCTP connections.
  156. If unsure, say Y.
  157. config NF_CT_PROTO_UDPLITE
  158. bool 'UDP-Lite protocol connection tracking support'
  159. depends on NETFILTER_ADVANCED
  160. default y
  161. help
  162. With this option enabled, the layer 3 independent connection
  163. tracking code will be able to do state tracking on UDP-Lite
  164. connections.
  165. If unsure, say Y.
  166. config NF_CONNTRACK_AMANDA
  167. tristate "Amanda backup protocol support"
  168. depends on NETFILTER_ADVANCED
  169. select TEXTSEARCH
  170. select TEXTSEARCH_KMP
  171. help
  172. If you are running the Amanda backup package <http://www.amanda.org/>
  173. on this machine or machines that will be MASQUERADED through this
  174. machine, then you may want to enable this feature. This allows the
  175. connection tracking and natting code to allow the sub-channels that
  176. Amanda requires for communication of the backup data, messages and
  177. index.
  178. To compile it as a module, choose M here. If unsure, say N.
  179. config NF_CONNTRACK_FTP
  180. tristate "FTP protocol support"
  181. default m if NETFILTER_ADVANCED=n
  182. help
  183. Tracking FTP connections is problematic: special helpers are
  184. required for tracking them, and doing masquerading and other forms
  185. of Network Address Translation on them.
  186. This is FTP support on Layer 3 independent connection tracking.
  187. To compile it as a module, choose M here. If unsure, say N.
  188. config NF_CONNTRACK_H323
  189. tristate "H.323 protocol support"
  190. depends on IPV6 || IPV6=n
  191. depends on NETFILTER_ADVANCED
  192. help
  193. H.323 is a VoIP signalling protocol from ITU-T. As one of the most
  194. important VoIP protocols, it is widely used by voice hardware and
  195. software including voice gateways, IP phones, Netmeeting, OpenPhone,
  196. Gnomemeeting, etc.
  197. With this module you can support H.323 on a connection tracking/NAT
  198. firewall.
  199. This module supports RAS, Fast Start, H.245 Tunnelling, Call
  200. Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
  201. whiteboard, file transfer, etc. For more information, please
  202. visit http://nath323.sourceforge.net/.
  203. To compile it as a module, choose M here. If unsure, say N.
  204. config NF_CONNTRACK_IRC
  205. tristate "IRC protocol support"
  206. default m if NETFILTER_ADVANCED=n
  207. help
  208. There is a commonly-used extension to IRC called
  209. Direct Client-to-Client Protocol (DCC). This enables users to send
  210. files to each other, and also chat to each other without the need
  211. of a server. DCC Sending is used anywhere you send files over IRC,
  212. and DCC Chat is most commonly used by Eggdrop bots. If you are
  213. using NAT, this extension will enable you to send files and initiate
  214. chats. Note that you do NOT need this extension to get files or
  215. have others initiate chats, or everything else in IRC.
  216. To compile it as a module, choose M here. If unsure, say N.
  217. config NF_CONNTRACK_BROADCAST
  218. tristate
  219. config NF_CONNTRACK_NETBIOS_NS
  220. tristate "NetBIOS name service protocol support"
  221. select NF_CONNTRACK_BROADCAST
  222. help
  223. NetBIOS name service requests are sent as broadcast messages from an
  224. unprivileged port and responded to with unicast messages to the
  225. same port. This make them hard to firewall properly because connection
  226. tracking doesn't deal with broadcasts. This helper tracks locally
  227. originating NetBIOS name service requests and the corresponding
  228. responses. It relies on correct IP address configuration, specifically
  229. netmask and broadcast address. When properly configured, the output
  230. of "ip address show" should look similar to this:
  231. $ ip -4 address show eth0
  232. 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
  233. inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
  234. To compile it as a module, choose M here. If unsure, say N.
  235. config NF_CONNTRACK_SNMP
  236. tristate "SNMP service protocol support"
  237. depends on NETFILTER_ADVANCED
  238. select NF_CONNTRACK_BROADCAST
  239. help
  240. SNMP service requests are sent as broadcast messages from an
  241. unprivileged port and responded to with unicast messages to the
  242. same port. This make them hard to firewall properly because connection
  243. tracking doesn't deal with broadcasts. This helper tracks locally
  244. originating SNMP service requests and the corresponding
  245. responses. It relies on correct IP address configuration, specifically
  246. netmask and broadcast address.
  247. To compile it as a module, choose M here. If unsure, say N.
  248. config NF_CONNTRACK_PPTP
  249. tristate "PPtP protocol support"
  250. depends on NETFILTER_ADVANCED
  251. select NF_CT_PROTO_GRE
  252. help
  253. This module adds support for PPTP (Point to Point Tunnelling
  254. Protocol, RFC2637) connection tracking and NAT.
  255. If you are running PPTP sessions over a stateful firewall or NAT
  256. box, you may want to enable this feature.
  257. Please note that not all PPTP modes of operation are supported yet.
  258. Specifically these limitations exist:
  259. - Blindly assumes that control connections are always established
  260. in PNS->PAC direction. This is a violation of RFC2637.
  261. - Only supports a single call within each session
  262. To compile it as a module, choose M here. If unsure, say N.
  263. config NF_CONNTRACK_SANE
  264. tristate "SANE protocol support"
  265. depends on NETFILTER_ADVANCED
  266. help
  267. SANE is a protocol for remote access to scanners as implemented
  268. by the 'saned' daemon. Like FTP, it uses separate control and
  269. data connections.
  270. With this module you can support SANE on a connection tracking
  271. firewall.
  272. To compile it as a module, choose M here. If unsure, say N.
  273. config NF_CONNTRACK_SIP
  274. tristate "SIP protocol support"
  275. default m if NETFILTER_ADVANCED=n
  276. help
  277. SIP is an application-layer control protocol that can establish,
  278. modify, and terminate multimedia sessions (conferences) such as
  279. Internet telephony calls. With the nf_conntrack_sip and
  280. the nf_nat_sip modules you can support the protocol on a connection
  281. tracking/NATing firewall.
  282. To compile it as a module, choose M here. If unsure, say N.
  283. config NF_CONNTRACK_TFTP
  284. tristate "TFTP protocol support"
  285. depends on NETFILTER_ADVANCED
  286. help
  287. TFTP connection tracking helper, this is required depending
  288. on how restrictive your ruleset is.
  289. If you are using a tftp client behind -j SNAT or -j MASQUERADING
  290. you will need this.
  291. To compile it as a module, choose M here. If unsure, say N.
  292. config NF_CT_NETLINK
  293. tristate 'Connection tracking netlink interface'
  294. select NETFILTER_NETLINK
  295. default m if NETFILTER_ADVANCED=n
  296. help
  297. This option enables support for a netlink-based userspace interface
  298. config NF_CT_NETLINK_TIMEOUT
  299. tristate 'Connection tracking timeout tuning via Netlink'
  300. select NETFILTER_NETLINK
  301. depends on NETFILTER_ADVANCED
  302. depends on NF_CONNTRACK_TIMEOUT
  303. help
  304. This option enables support for connection tracking timeout
  305. fine-grain tuning. This allows you to attach specific timeout
  306. policies to flows, instead of using the global timeout policy.
  307. If unsure, say `N'.
  308. config NF_CT_NETLINK_HELPER
  309. tristate 'Connection tracking helpers in user-space via Netlink'
  310. select NETFILTER_NETLINK
  311. depends on NF_CT_NETLINK
  312. depends on NETFILTER_NETLINK_QUEUE
  313. depends on NETFILTER_NETLINK_GLUE_CT
  314. depends on NETFILTER_ADVANCED
  315. help
  316. This option enables the user-space connection tracking helpers
  317. infrastructure.
  318. If unsure, say `N'.
  319. config NETFILTER_NETLINK_GLUE_CT
  320. bool "NFQUEUE and NFLOG integration with Connection Tracking"
  321. default n
  322. depends on (NETFILTER_NETLINK_QUEUE || NETFILTER_NETLINK_LOG) && NF_CT_NETLINK
  323. help
  324. If this option is enabled, NFQUEUE and NFLOG can include
  325. Connection Tracking information together with the packet is
  326. the enqueued via NFNETLINK.
  327. config NF_NAT
  328. tristate "Network Address Translation support"
  329. depends on NF_CONNTRACK
  330. default m if NETFILTER_ADVANCED=n
  331. help
  332. The NAT option allows masquerading, port forwarding and other
  333. forms of full Network Address Port Translation. This can be
  334. controlled by iptables, ip6tables or nft.
  335. config NF_NAT_AMANDA
  336. tristate
  337. depends on NF_CONNTRACK && NF_NAT
  338. default NF_NAT && NF_CONNTRACK_AMANDA
  339. config NF_NAT_FTP
  340. tristate
  341. depends on NF_CONNTRACK && NF_NAT
  342. default NF_NAT && NF_CONNTRACK_FTP
  343. config NF_NAT_IRC
  344. tristate
  345. depends on NF_CONNTRACK && NF_NAT
  346. default NF_NAT && NF_CONNTRACK_IRC
  347. config NF_NAT_SIP
  348. tristate
  349. depends on NF_CONNTRACK && NF_NAT
  350. default NF_NAT && NF_CONNTRACK_SIP
  351. config NF_NAT_TFTP
  352. tristate
  353. depends on NF_CONNTRACK && NF_NAT
  354. default NF_NAT && NF_CONNTRACK_TFTP
  355. config NF_NAT_REDIRECT
  356. bool
  357. config NF_NAT_MASQUERADE
  358. bool
  359. config NETFILTER_SYNPROXY
  360. tristate
  361. endif # NF_CONNTRACK
  362. config NF_TABLES
  363. select NETFILTER_NETLINK
  364. select LIBCRC32C
  365. tristate "Netfilter nf_tables support"
  366. help
  367. nftables is the new packet classification framework that intends to
  368. replace the existing {ip,ip6,arp,eb}_tables infrastructure. It
  369. provides a pseudo-state machine with an extensible instruction-set
  370. (also known as expressions) that the userspace 'nft' utility
  371. (https://www.netfilter.org/projects/nftables) uses to build the
  372. rule-set. It also comes with the generic set infrastructure that
  373. allows you to construct mappings between matchings and actions
  374. for performance lookups.
  375. To compile it as a module, choose M here.
  376. if NF_TABLES
  377. config NF_TABLES_INET
  378. depends on IPV6
  379. select NF_TABLES_IPV4
  380. select NF_TABLES_IPV6
  381. bool "Netfilter nf_tables mixed IPv4/IPv6 tables support"
  382. help
  383. This option enables support for a mixed IPv4/IPv6 "inet" table.
  384. config NF_TABLES_NETDEV
  385. bool "Netfilter nf_tables netdev tables support"
  386. help
  387. This option enables support for the "netdev" table.
  388. config NFT_NUMGEN
  389. tristate "Netfilter nf_tables number generator module"
  390. help
  391. This option adds the number generator expression used to perform
  392. incremental counting and random numbers bound to a upper limit.
  393. config NFT_CT
  394. depends on NF_CONNTRACK
  395. tristate "Netfilter nf_tables conntrack module"
  396. help
  397. This option adds the "ct" expression that you can use to match
  398. connection tracking information such as the flow state.
  399. config NFT_FLOW_OFFLOAD
  400. depends on NF_CONNTRACK && NF_FLOW_TABLE
  401. tristate "Netfilter nf_tables hardware flow offload module"
  402. help
  403. This option adds the "flow_offload" expression that you can use to
  404. choose what flows are placed into the hardware.
  405. config NFT_COUNTER
  406. tristate "Netfilter nf_tables counter module"
  407. help
  408. This option adds the "counter" expression that you can use to
  409. include packet and byte counters in a rule.
  410. config NFT_CONNLIMIT
  411. tristate "Netfilter nf_tables connlimit module"
  412. depends on NF_CONNTRACK
  413. depends on NETFILTER_ADVANCED
  414. select NETFILTER_CONNCOUNT
  415. help
  416. This option adds the "connlimit" expression that you can use to
  417. ratelimit rule matchings per connections.
  418. config NFT_LOG
  419. tristate "Netfilter nf_tables log module"
  420. help
  421. This option adds the "log" expression that you can use to log
  422. packets matching some criteria.
  423. config NFT_LIMIT
  424. tristate "Netfilter nf_tables limit module"
  425. help
  426. This option adds the "limit" expression that you can use to
  427. ratelimit rule matchings.
  428. config NFT_MASQ
  429. depends on NF_CONNTRACK
  430. depends on NF_NAT
  431. select NF_NAT_MASQUERADE
  432. tristate "Netfilter nf_tables masquerade support"
  433. help
  434. This option adds the "masquerade" expression that you can use
  435. to perform NAT in the masquerade flavour.
  436. config NFT_REDIR
  437. depends on NF_CONNTRACK
  438. depends on NF_NAT
  439. tristate "Netfilter nf_tables redirect support"
  440. select NF_NAT_REDIRECT
  441. help
  442. This options adds the "redirect" expression that you can use
  443. to perform NAT in the redirect flavour.
  444. config NFT_NAT
  445. depends on NF_CONNTRACK
  446. select NF_NAT
  447. depends on NF_TABLES_IPV4 || NF_TABLES_IPV6
  448. tristate "Netfilter nf_tables nat module"
  449. help
  450. This option adds the "nat" expression that you can use to perform
  451. typical Network Address Translation (NAT) packet transformations.
  452. config NFT_TUNNEL
  453. tristate "Netfilter nf_tables tunnel module"
  454. help
  455. This option adds the "tunnel" expression that you can use to set
  456. tunneling policies.
  457. config NFT_OBJREF
  458. tristate "Netfilter nf_tables stateful object reference module"
  459. help
  460. This option adds the "objref" expression that allows you to refer to
  461. stateful objects, such as counters and quotas.
  462. config NFT_QUEUE
  463. depends on NETFILTER_NETLINK_QUEUE
  464. tristate "Netfilter nf_tables queue module"
  465. help
  466. This is required if you intend to use the userspace queueing
  467. infrastructure (also known as NFQUEUE) from nftables.
  468. config NFT_QUOTA
  469. tristate "Netfilter nf_tables quota module"
  470. help
  471. This option adds the "quota" expression that you can use to match
  472. enforce bytes quotas.
  473. config NFT_REJECT
  474. default m if NETFILTER_ADVANCED=n
  475. tristate "Netfilter nf_tables reject support"
  476. depends on !NF_TABLES_INET || (IPV6!=m || m)
  477. help
  478. This option adds the "reject" expression that you can use to
  479. explicitly deny and notify via TCP reset/ICMP informational errors
  480. unallowed traffic.
  481. config NFT_REJECT_INET
  482. depends on NF_TABLES_INET
  483. default NFT_REJECT
  484. tristate
  485. config NFT_COMPAT
  486. depends on NETFILTER_XTABLES
  487. tristate "Netfilter x_tables over nf_tables module"
  488. help
  489. This is required if you intend to use any of existing
  490. x_tables match/target extensions over the nf_tables
  491. framework.
  492. config NFT_HASH
  493. tristate "Netfilter nf_tables hash module"
  494. help
  495. This option adds the "hash" expression that you can use to perform
  496. a hash operation on registers.
  497. config NFT_FIB
  498. tristate
  499. config NFT_FIB_INET
  500. depends on NF_TABLES_INET
  501. depends on NFT_FIB_IPV4
  502. depends on NFT_FIB_IPV6
  503. tristate "Netfilter nf_tables fib inet support"
  504. help
  505. This option allows using the FIB expression from the inet table.
  506. The lookup will be delegated to the IPv4 or IPv6 FIB depending
  507. on the protocol of the packet.
  508. config NFT_XFRM
  509. tristate "Netfilter nf_tables xfrm/IPSec security association matching"
  510. depends on XFRM
  511. help
  512. This option adds an expression that you can use to extract properties
  513. of a packets security association.
  514. config NFT_SOCKET
  515. tristate "Netfilter nf_tables socket match support"
  516. depends on IPV6 || IPV6=n
  517. select NF_SOCKET_IPV4
  518. select NF_SOCKET_IPV6 if NF_TABLES_IPV6
  519. help
  520. This option allows matching for the presence or absence of a
  521. corresponding socket and its attributes.
  522. config NFT_OSF
  523. tristate "Netfilter nf_tables passive OS fingerprint support"
  524. depends on NETFILTER_ADVANCED
  525. select NETFILTER_NETLINK_OSF
  526. help
  527. This option allows matching packets from an specific OS.
  528. config NFT_TPROXY
  529. tristate "Netfilter nf_tables tproxy support"
  530. depends on IPV6 || IPV6=n
  531. select NF_DEFRAG_IPV4
  532. select NF_DEFRAG_IPV6 if NF_TABLES_IPV6
  533. select NF_TPROXY_IPV4
  534. select NF_TPROXY_IPV6 if NF_TABLES_IPV6
  535. help
  536. This makes transparent proxy support available in nftables.
  537. config NFT_SYNPROXY
  538. tristate "Netfilter nf_tables SYNPROXY expression support"
  539. depends on NF_CONNTRACK && NETFILTER_ADVANCED
  540. select NETFILTER_SYNPROXY
  541. select SYN_COOKIES
  542. help
  543. The SYNPROXY expression allows you to intercept TCP connections and
  544. establish them using syncookies before they are passed on to the
  545. server. This allows to avoid conntrack and server resource usage
  546. during SYN-flood attacks.
  547. if NF_TABLES_NETDEV
  548. config NF_DUP_NETDEV
  549. tristate "Netfilter packet duplication support"
  550. help
  551. This option enables the generic packet duplication infrastructure
  552. for Netfilter.
  553. config NFT_DUP_NETDEV
  554. tristate "Netfilter nf_tables netdev packet duplication support"
  555. select NF_DUP_NETDEV
  556. help
  557. This option enables packet duplication for the "netdev" family.
  558. config NFT_FWD_NETDEV
  559. tristate "Netfilter nf_tables netdev packet forwarding support"
  560. select NF_DUP_NETDEV
  561. help
  562. This option enables packet forwarding for the "netdev" family.
  563. config NFT_FIB_NETDEV
  564. depends on NFT_FIB_IPV4
  565. depends on NFT_FIB_IPV6
  566. tristate "Netfilter nf_tables netdev fib lookups support"
  567. help
  568. This option allows using the FIB expression from the netdev table.
  569. The lookup will be delegated to the IPv4 or IPv6 FIB depending
  570. on the protocol of the packet.
  571. endif # NF_TABLES_NETDEV
  572. endif # NF_TABLES
  573. config NF_FLOW_TABLE_INET
  574. tristate "Netfilter flow table mixed IPv4/IPv6 module"
  575. depends on NF_FLOW_TABLE
  576. help
  577. This option adds the flow table mixed IPv4/IPv6 support.
  578. To compile it as a module, choose M here.
  579. config NF_FLOW_TABLE
  580. tristate "Netfilter flow table module"
  581. depends on NETFILTER_INGRESS
  582. depends on NF_CONNTRACK
  583. depends on NF_TABLES
  584. help
  585. This option adds the flow table core infrastructure.
  586. To compile it as a module, choose M here.
  587. config NETFILTER_XTABLES
  588. tristate "Netfilter Xtables support (required for ip_tables)"
  589. default m if NETFILTER_ADVANCED=n
  590. help
  591. This is required if you intend to use any of ip_tables,
  592. ip6_tables or arp_tables.
  593. if NETFILTER_XTABLES
  594. comment "Xtables combined modules"
  595. config NETFILTER_XT_MARK
  596. tristate 'nfmark target and match support'
  597. default m if NETFILTER_ADVANCED=n
  598. help
  599. This option adds the "MARK" target and "mark" match.
  600. Netfilter mark matching allows you to match packets based on the
  601. "nfmark" value in the packet.
  602. The target allows you to create rules in the "mangle" table which alter
  603. the netfilter mark (nfmark) field associated with the packet.
  604. Prior to routing, the nfmark can influence the routing method and can
  605. also be used by other subsystems to change their behavior.
  606. config NETFILTER_XT_CONNMARK
  607. tristate 'ctmark target and match support'
  608. depends on NF_CONNTRACK
  609. depends on NETFILTER_ADVANCED
  610. select NF_CONNTRACK_MARK
  611. help
  612. This option adds the "CONNMARK" target and "connmark" match.
  613. Netfilter allows you to store a mark value per connection (a.k.a.
  614. ctmark), similarly to the packet mark (nfmark). Using this
  615. target and match, you can set and match on this mark.
  616. config NETFILTER_XT_SET
  617. tristate 'set target and match support'
  618. depends on IP_SET
  619. depends on NETFILTER_ADVANCED
  620. help
  621. This option adds the "SET" target and "set" match.
  622. Using this target and match, you can add/delete and match
  623. elements in the sets created by ipset(8).
  624. To compile it as a module, choose M here. If unsure, say N.
  625. # alphabetically ordered list of targets
  626. comment "Xtables targets"
  627. config NETFILTER_XT_TARGET_AUDIT
  628. tristate "AUDIT target support"
  629. depends on AUDIT
  630. depends on NETFILTER_ADVANCED
  631. help
  632. This option adds a 'AUDIT' target, which can be used to create
  633. audit records for packets dropped/accepted.
  634. To compileit as a module, choose M here. If unsure, say N.
  635. config NETFILTER_XT_TARGET_CHECKSUM
  636. tristate "CHECKSUM target support"
  637. depends on IP_NF_MANGLE || IP6_NF_MANGLE
  638. depends on NETFILTER_ADVANCED
  639. help
  640. This option adds a `CHECKSUM' target, which can be used in the iptables mangle
  641. table to work around buggy DHCP clients in virtualized environments.
  642. Some old DHCP clients drop packets because they are not aware
  643. that the checksum would normally be offloaded to hardware and
  644. thus should be considered valid.
  645. This target can be used to fill in the checksum using iptables
  646. when such packets are sent via a virtual network device.
  647. To compile it as a module, choose M here. If unsure, say N.
  648. config NETFILTER_XT_TARGET_CLASSIFY
  649. tristate '"CLASSIFY" target support'
  650. depends on NETFILTER_ADVANCED
  651. help
  652. This option adds a `CLASSIFY' target, which enables the user to set
  653. the priority of a packet. Some qdiscs can use this value for
  654. classification, among these are:
  655. atm, cbq, dsmark, pfifo_fast, htb, prio
  656. To compile it as a module, choose M here. If unsure, say N.
  657. config NETFILTER_XT_TARGET_CONNMARK
  658. tristate '"CONNMARK" target support'
  659. depends on NF_CONNTRACK
  660. depends on NETFILTER_ADVANCED
  661. select NETFILTER_XT_CONNMARK
  662. help
  663. This is a backwards-compat option for the user's convenience
  664. (e.g. when running oldconfig). It selects
  665. CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
  666. config NETFILTER_XT_TARGET_CONNSECMARK
  667. tristate '"CONNSECMARK" target support'
  668. depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK
  669. default m if NETFILTER_ADVANCED=n
  670. help
  671. The CONNSECMARK target copies security markings from packets
  672. to connections, and restores security markings from connections
  673. to packets (if the packets are not already marked). This would
  674. normally be used in conjunction with the SECMARK target.
  675. To compile it as a module, choose M here. If unsure, say N.
  676. config NETFILTER_XT_TARGET_CT
  677. tristate '"CT" target support'
  678. depends on NF_CONNTRACK
  679. depends on IP_NF_RAW || IP6_NF_RAW
  680. depends on NETFILTER_ADVANCED
  681. help
  682. This options adds a `CT' target, which allows to specify initial
  683. connection tracking parameters like events to be delivered and
  684. the helper to be used.
  685. To compile it as a module, choose M here. If unsure, say N.
  686. config NETFILTER_XT_TARGET_DSCP
  687. tristate '"DSCP" and "TOS" target support'
  688. depends on IP_NF_MANGLE || IP6_NF_MANGLE
  689. depends on NETFILTER_ADVANCED
  690. help
  691. This option adds a `DSCP' target, which allows you to manipulate
  692. the IPv4/IPv6 header DSCP field (differentiated services codepoint).
  693. The DSCP field can have any value between 0x0 and 0x3f inclusive.
  694. It also adds the "TOS" target, which allows you to create rules in
  695. the "mangle" table which alter the Type Of Service field of an IPv4
  696. or the Priority field of an IPv6 packet, prior to routing.
  697. To compile it as a module, choose M here. If unsure, say N.
  698. config NETFILTER_XT_TARGET_HL
  699. tristate '"HL" hoplimit target support'
  700. depends on IP_NF_MANGLE || IP6_NF_MANGLE
  701. depends on NETFILTER_ADVANCED
  702. help
  703. This option adds the "HL" (for IPv6) and "TTL" (for IPv4)
  704. targets, which enable the user to change the
  705. hoplimit/time-to-live value of the IP header.
  706. While it is safe to decrement the hoplimit/TTL value, the
  707. modules also allow to increment and set the hoplimit value of
  708. the header to arbitrary values. This is EXTREMELY DANGEROUS
  709. since you can easily create immortal packets that loop
  710. forever on the network.
  711. config NETFILTER_XT_TARGET_HMARK
  712. tristate '"HMARK" target support'
  713. depends on IP6_NF_IPTABLES || IP6_NF_IPTABLES=n
  714. depends on NETFILTER_ADVANCED
  715. help
  716. This option adds the "HMARK" target.
  717. The target allows you to create rules in the "raw" and "mangle" tables
  718. which set the skbuff mark by means of hash calculation within a given
  719. range. The nfmark can influence the routing method and can also be used
  720. by other subsystems to change their behaviour.
  721. To compile it as a module, choose M here. If unsure, say N.
  722. config NETFILTER_XT_TARGET_IDLETIMER
  723. tristate "IDLETIMER target support"
  724. depends on NETFILTER_ADVANCED
  725. help
  726. This option adds the `IDLETIMER' target. Each matching packet
  727. resets the timer associated with label specified when the rule is
  728. added. When the timer expires, it triggers a sysfs notification.
  729. The remaining time for expiration can be read via sysfs.
  730. To compile it as a module, choose M here. If unsure, say N.
  731. config NETFILTER_XT_TARGET_LED
  732. tristate '"LED" target support'
  733. depends on LEDS_CLASS && LEDS_TRIGGERS
  734. depends on NETFILTER_ADVANCED
  735. help
  736. This option adds a `LED' target, which allows you to blink LEDs in
  737. response to particular packets passing through your machine.
  738. This can be used to turn a spare LED into a network activity LED,
  739. which only flashes in response to FTP transfers, for example. Or
  740. you could have an LED which lights up for a minute or two every time
  741. somebody connects to your machine via SSH.
  742. You will need support for the "led" class to make this work.
  743. To create an LED trigger for incoming SSH traffic:
  744. iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000
  745. Then attach the new trigger to an LED on your system:
  746. echo netfilter-ssh > /sys/class/leds/<ledname>/trigger
  747. For more information on the LEDs available on your system, see
  748. Documentation/leds/leds-class.rst
  749. config NETFILTER_XT_TARGET_LOG
  750. tristate "LOG target support"
  751. select NF_LOG_COMMON
  752. select NF_LOG_IPV4
  753. select NF_LOG_IPV6 if IP6_NF_IPTABLES
  754. default m if NETFILTER_ADVANCED=n
  755. help
  756. This option adds a `LOG' target, which allows you to create rules in
  757. any iptables table which records the packet header to the syslog.
  758. To compile it as a module, choose M here. If unsure, say N.
  759. config NETFILTER_XT_TARGET_MARK
  760. tristate '"MARK" target support'
  761. depends on NETFILTER_ADVANCED
  762. select NETFILTER_XT_MARK
  763. help
  764. This is a backwards-compat option for the user's convenience
  765. (e.g. when running oldconfig). It selects
  766. CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
  767. config NETFILTER_XT_NAT
  768. tristate '"SNAT and DNAT" targets support'
  769. depends on NF_NAT
  770. help
  771. This option enables the SNAT and DNAT targets.
  772. To compile it as a module, choose M here. If unsure, say N.
  773. config NETFILTER_XT_TARGET_NETMAP
  774. tristate '"NETMAP" target support'
  775. depends on NF_NAT
  776. help
  777. NETMAP is an implementation of static 1:1 NAT mapping of network
  778. addresses. It maps the network address part, while keeping the host
  779. address part intact.
  780. To compile it as a module, choose M here. If unsure, say N.
  781. config NETFILTER_XT_TARGET_NFLOG
  782. tristate '"NFLOG" target support'
  783. default m if NETFILTER_ADVANCED=n
  784. select NETFILTER_NETLINK_LOG
  785. help
  786. This option enables the NFLOG target, which allows to LOG
  787. messages through nfnetlink_log.
  788. To compile it as a module, choose M here. If unsure, say N.
  789. config NETFILTER_XT_TARGET_NFQUEUE
  790. tristate '"NFQUEUE" target Support'
  791. depends on NETFILTER_ADVANCED
  792. select NETFILTER_NETLINK_QUEUE
  793. help
  794. This target replaced the old obsolete QUEUE target.
  795. As opposed to QUEUE, it supports 65535 different queues,
  796. not just one.
  797. To compile it as a module, choose M here. If unsure, say N.
  798. config NETFILTER_XT_TARGET_NOTRACK
  799. tristate '"NOTRACK" target support (DEPRECATED)'
  800. depends on NF_CONNTRACK
  801. depends on IP_NF_RAW || IP6_NF_RAW
  802. depends on NETFILTER_ADVANCED
  803. select NETFILTER_XT_TARGET_CT
  804. config NETFILTER_XT_TARGET_RATEEST
  805. tristate '"RATEEST" target support'
  806. depends on NETFILTER_ADVANCED
  807. help
  808. This option adds a `RATEEST' target, which allows to measure
  809. rates similar to TC estimators. The `rateest' match can be
  810. used to match on the measured rates.
  811. To compile it as a module, choose M here. If unsure, say N.
  812. config NETFILTER_XT_TARGET_REDIRECT
  813. tristate "REDIRECT target support"
  814. depends on NF_NAT
  815. select NF_NAT_REDIRECT
  816. help
  817. REDIRECT is a special case of NAT: all incoming connections are
  818. mapped onto the incoming interface's address, causing the packets to
  819. come to the local machine instead of passing through. This is
  820. useful for transparent proxies.
  821. To compile it as a module, choose M here. If unsure, say N.
  822. config NETFILTER_XT_TARGET_MASQUERADE
  823. tristate "MASQUERADE target support"
  824. depends on NF_NAT
  825. default m if NETFILTER_ADVANCED=n
  826. select NF_NAT_MASQUERADE
  827. help
  828. Masquerading is a special case of NAT: all outgoing connections are
  829. changed to seem to come from a particular interface's address, and
  830. if the interface goes down, those connections are lost. This is
  831. only useful for dialup accounts with dynamic IP address (ie. your IP
  832. address will be different on next dialup).
  833. To compile it as a module, choose M here. If unsure, say N.
  834. config NETFILTER_XT_TARGET_TEE
  835. tristate '"TEE" - packet cloning to alternate destination'
  836. depends on NETFILTER_ADVANCED
  837. depends on IPV6 || IPV6=n
  838. depends on !NF_CONNTRACK || NF_CONNTRACK
  839. depends on IP6_NF_IPTABLES || !IP6_NF_IPTABLES
  840. select NF_DUP_IPV4
  841. select NF_DUP_IPV6 if IP6_NF_IPTABLES
  842. help
  843. This option adds a "TEE" target with which a packet can be cloned and
  844. this clone be rerouted to another nexthop.
  845. config NETFILTER_XT_TARGET_TPROXY
  846. tristate '"TPROXY" target transparent proxying support'
  847. depends on NETFILTER_XTABLES
  848. depends on NETFILTER_ADVANCED
  849. depends on IPV6 || IPV6=n
  850. depends on IP6_NF_IPTABLES || IP6_NF_IPTABLES=n
  851. depends on IP_NF_MANGLE
  852. select NF_DEFRAG_IPV4
  853. select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES != n
  854. select NF_TPROXY_IPV4
  855. select NF_TPROXY_IPV6 if IP6_NF_IPTABLES
  856. help
  857. This option adds a `TPROXY' target, which is somewhat similar to
  858. REDIRECT. It can only be used in the mangle table and is useful
  859. to redirect traffic to a transparent proxy. It does _not_ depend
  860. on Netfilter connection tracking and NAT, unlike REDIRECT.
  861. For it to work you will have to configure certain iptables rules
  862. and use policy routing. For more information on how to set it up
  863. see Documentation/networking/tproxy.rst.
  864. To compile it as a module, choose M here. If unsure, say N.
  865. config NETFILTER_XT_TARGET_TRACE
  866. tristate '"TRACE" target support'
  867. depends on IP_NF_RAW || IP6_NF_RAW
  868. depends on NETFILTER_ADVANCED
  869. help
  870. The TRACE target allows you to mark packets so that the kernel
  871. will log every rule which match the packets as those traverse
  872. the tables, chains, rules.
  873. If you want to compile it as a module, say M here and read
  874. <file:Documentation/kbuild/modules.rst>. If unsure, say `N'.
  875. config NETFILTER_XT_TARGET_SECMARK
  876. tristate '"SECMARK" target support'
  877. depends on NETWORK_SECMARK
  878. default m if NETFILTER_ADVANCED=n
  879. help
  880. The SECMARK target allows security marking of network
  881. packets, for use with security subsystems.
  882. To compile it as a module, choose M here. If unsure, say N.
  883. config NETFILTER_XT_TARGET_TCPMSS
  884. tristate '"TCPMSS" target support'
  885. depends on IPV6 || IPV6=n
  886. default m if NETFILTER_ADVANCED=n
  887. help
  888. This option adds a `TCPMSS' target, which allows you to alter the
  889. MSS value of TCP SYN packets, to control the maximum size for that
  890. connection (usually limiting it to your outgoing interface's MTU
  891. minus 40).
  892. This is used to overcome criminally braindead ISPs or servers which
  893. block ICMP Fragmentation Needed packets. The symptoms of this
  894. problem are that everything works fine from your Linux
  895. firewall/router, but machines behind it can never exchange large
  896. packets:
  897. 1) Web browsers connect, then hang with no data received.
  898. 2) Small mail works fine, but large emails hang.
  899. 3) ssh works fine, but scp hangs after initial handshaking.
  900. Workaround: activate this option and add a rule to your firewall
  901. configuration like:
  902. iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
  903. -j TCPMSS --clamp-mss-to-pmtu
  904. To compile it as a module, choose M here. If unsure, say N.
  905. config NETFILTER_XT_TARGET_TCPOPTSTRIP
  906. tristate '"TCPOPTSTRIP" target support'
  907. depends on IP_NF_MANGLE || IP6_NF_MANGLE
  908. depends on NETFILTER_ADVANCED
  909. help
  910. This option adds a "TCPOPTSTRIP" target, which allows you to strip
  911. TCP options from TCP packets.
  912. # alphabetically ordered list of matches
  913. comment "Xtables matches"
  914. config NETFILTER_XT_MATCH_ADDRTYPE
  915. tristate '"addrtype" address type match support'
  916. default m if NETFILTER_ADVANCED=n
  917. help
  918. This option allows you to match what routing thinks of an address,
  919. eg. UNICAST, LOCAL, BROADCAST, ...
  920. If you want to compile it as a module, say M here and read
  921. <file:Documentation/kbuild/modules.rst>. If unsure, say `N'.
  922. config NETFILTER_XT_MATCH_BPF
  923. tristate '"bpf" match support'
  924. depends on NETFILTER_ADVANCED
  925. help
  926. BPF matching applies a linux socket filter to each packet and
  927. accepts those for which the filter returns non-zero.
  928. To compile it as a module, choose M here. If unsure, say N.
  929. config NETFILTER_XT_MATCH_CGROUP
  930. tristate '"control group" match support'
  931. depends on NETFILTER_ADVANCED
  932. depends on CGROUPS
  933. select CGROUP_NET_CLASSID
  934. help
  935. Socket/process control group matching allows you to match locally
  936. generated packets based on which net_cls control group processes
  937. belong to.
  938. config NETFILTER_XT_MATCH_CLUSTER
  939. tristate '"cluster" match support'
  940. depends on NF_CONNTRACK
  941. depends on NETFILTER_ADVANCED
  942. help
  943. This option allows you to build work-load-sharing clusters of
  944. network servers/stateful firewalls without having a dedicated
  945. load-balancing router/server/switch. Basically, this match returns
  946. true when the packet must be handled by this cluster node. Thus,
  947. all nodes see all packets and this match decides which node handles
  948. what packets. The work-load sharing algorithm is based on source
  949. address hashing.
  950. If you say Y or M here, try `iptables -m cluster --help` for
  951. more information.
  952. config NETFILTER_XT_MATCH_COMMENT
  953. tristate '"comment" match support'
  954. depends on NETFILTER_ADVANCED
  955. help
  956. This option adds a `comment' dummy-match, which allows you to put
  957. comments in your iptables ruleset.
  958. If you want to compile it as a module, say M here and read
  959. <file:Documentation/kbuild/modules.rst>. If unsure, say `N'.
  960. config NETFILTER_XT_MATCH_CONNBYTES
  961. tristate '"connbytes" per-connection counter match support'
  962. depends on NF_CONNTRACK
  963. depends on NETFILTER_ADVANCED
  964. help
  965. This option adds a `connbytes' match, which allows you to match the
  966. number of bytes and/or packets for each direction within a connection.
  967. If you want to compile it as a module, say M here and read
  968. <file:Documentation/kbuild/modules.rst>. If unsure, say `N'.
  969. config NETFILTER_XT_MATCH_CONNLABEL
  970. tristate '"connlabel" match support'
  971. select NF_CONNTRACK_LABELS
  972. depends on NF_CONNTRACK
  973. depends on NETFILTER_ADVANCED
  974. help
  975. This match allows you to test and assign userspace-defined labels names
  976. to a connection. The kernel only stores bit values - mapping
  977. names to bits is done by userspace.
  978. Unlike connmark, more than 32 flag bits may be assigned to a
  979. connection simultaneously.
  980. config NETFILTER_XT_MATCH_CONNLIMIT
  981. tristate '"connlimit" match support'
  982. depends on NF_CONNTRACK
  983. depends on NETFILTER_ADVANCED
  984. select NETFILTER_CONNCOUNT
  985. help
  986. This match allows you to match against the number of parallel
  987. connections to a server per client IP address (or address block).
  988. config NETFILTER_XT_MATCH_CONNMARK
  989. tristate '"connmark" connection mark match support'
  990. depends on NF_CONNTRACK
  991. depends on NETFILTER_ADVANCED
  992. select NETFILTER_XT_CONNMARK
  993. help
  994. This is a backwards-compat option for the user's convenience
  995. (e.g. when running oldconfig). It selects
  996. CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
  997. config NETFILTER_XT_MATCH_CONNTRACK
  998. tristate '"conntrack" connection tracking match support'
  999. depends on NF_CONNTRACK
  1000. default m if NETFILTER_ADVANCED=n
  1001. help
  1002. This is a general conntrack match module, a superset of the state match.
  1003. It allows matching on additional conntrack information, which is
  1004. useful in complex configurations, such as NAT gateways with multiple
  1005. internet links or tunnels.
  1006. To compile it as a module, choose M here. If unsure, say N.
  1007. config NETFILTER_XT_MATCH_CPU
  1008. tristate '"cpu" match support'
  1009. depends on NETFILTER_ADVANCED
  1010. help
  1011. CPU matching allows you to match packets based on the CPU
  1012. currently handling the packet.
  1013. To compile it as a module, choose M here. If unsure, say N.
  1014. config NETFILTER_XT_MATCH_DCCP
  1015. tristate '"dccp" protocol match support'
  1016. depends on NETFILTER_ADVANCED
  1017. default IP_DCCP
  1018. help
  1019. With this option enabled, you will be able to use the iptables
  1020. `dccp' match in order to match on DCCP source/destination ports
  1021. and DCCP flags.
  1022. If you want to compile it as a module, say M here and read
  1023. <file:Documentation/kbuild/modules.rst>. If unsure, say `N'.
  1024. config NETFILTER_XT_MATCH_DEVGROUP
  1025. tristate '"devgroup" match support'
  1026. depends on NETFILTER_ADVANCED
  1027. help
  1028. This options adds a `devgroup' match, which allows to match on the
  1029. device group a network device is assigned to.
  1030. To compile it as a module, choose M here. If unsure, say N.
  1031. config NETFILTER_XT_MATCH_DSCP
  1032. tristate '"dscp" and "tos" match support'
  1033. depends on NETFILTER_ADVANCED
  1034. help
  1035. This option adds a `DSCP' match, which allows you to match against
  1036. the IPv4/IPv6 header DSCP field (differentiated services codepoint).
  1037. The DSCP field can have any value between 0x0 and 0x3f inclusive.
  1038. It will also add a "tos" match, which allows you to match packets
  1039. based on the Type Of Service fields of the IPv4 packet (which share
  1040. the same bits as DSCP).
  1041. To compile it as a module, choose M here. If unsure, say N.
  1042. config NETFILTER_XT_MATCH_ECN
  1043. tristate '"ecn" match support'
  1044. depends on NETFILTER_ADVANCED
  1045. help
  1046. This option adds an "ECN" match, which allows you to match against
  1047. the IPv4 and TCP header ECN fields.
  1048. To compile it as a module, choose M here. If unsure, say N.
  1049. config NETFILTER_XT_MATCH_ESP
  1050. tristate '"esp" match support'
  1051. depends on NETFILTER_ADVANCED
  1052. help
  1053. This match extension allows you to match a range of SPIs
  1054. inside ESP header of IPSec packets.
  1055. To compile it as a module, choose M here. If unsure, say N.
  1056. config NETFILTER_XT_MATCH_HASHLIMIT
  1057. tristate '"hashlimit" match support'
  1058. depends on IP6_NF_IPTABLES || IP6_NF_IPTABLES=n
  1059. depends on NETFILTER_ADVANCED
  1060. help
  1061. This option adds a `hashlimit' match.
  1062. As opposed to `limit', this match dynamically creates a hash table
  1063. of limit buckets, based on your selection of source/destination
  1064. addresses and/or ports.
  1065. It enables you to express policies like `10kpps for any given
  1066. destination address' or `500pps from any given source address'
  1067. with a single rule.
  1068. config NETFILTER_XT_MATCH_HELPER
  1069. tristate '"helper" match support'
  1070. depends on NF_CONNTRACK
  1071. depends on NETFILTER_ADVANCED
  1072. help
  1073. Helper matching allows you to match packets in dynamic connections
  1074. tracked by a conntrack-helper, ie. nf_conntrack_ftp
  1075. To compile it as a module, choose M here. If unsure, say Y.
  1076. config NETFILTER_XT_MATCH_HL
  1077. tristate '"hl" hoplimit/TTL match support'
  1078. depends on NETFILTER_ADVANCED
  1079. help
  1080. HL matching allows you to match packets based on the hoplimit
  1081. in the IPv6 header, or the time-to-live field in the IPv4
  1082. header of the packet.
  1083. config NETFILTER_XT_MATCH_IPCOMP
  1084. tristate '"ipcomp" match support'
  1085. depends on NETFILTER_ADVANCED
  1086. help
  1087. This match extension allows you to match a range of CPIs(16 bits)
  1088. inside IPComp header of IPSec packets.
  1089. To compile it as a module, choose M here. If unsure, say N.
  1090. config NETFILTER_XT_MATCH_IPRANGE
  1091. tristate '"iprange" address range match support'
  1092. depends on NETFILTER_ADVANCED
  1093. help
  1094. This option adds a "iprange" match, which allows you to match based on
  1095. an IP address range. (Normal iptables only matches on single addresses
  1096. with an optional mask.)
  1097. If unsure, say M.
  1098. config NETFILTER_XT_MATCH_IPVS
  1099. tristate '"ipvs" match support'
  1100. depends on IP_VS
  1101. depends on NETFILTER_ADVANCED
  1102. depends on NF_CONNTRACK
  1103. help
  1104. This option allows you to match against IPVS properties of a packet.
  1105. If unsure, say N.
  1106. config NETFILTER_XT_MATCH_L2TP
  1107. tristate '"l2tp" match support'
  1108. depends on NETFILTER_ADVANCED
  1109. default L2TP
  1110. help
  1111. This option adds an "L2TP" match, which allows you to match against
  1112. L2TP protocol header fields.
  1113. To compile it as a module, choose M here. If unsure, say N.
  1114. config NETFILTER_XT_MATCH_LENGTH
  1115. tristate '"length" match support'
  1116. depends on NETFILTER_ADVANCED
  1117. help
  1118. This option allows you to match the length of a packet against a
  1119. specific value or range of values.
  1120. To compile it as a module, choose M here. If unsure, say N.
  1121. config NETFILTER_XT_MATCH_LIMIT
  1122. tristate '"limit" match support'
  1123. depends on NETFILTER_ADVANCED
  1124. help
  1125. limit matching allows you to control the rate at which a rule can be
  1126. matched: mainly useful in combination with the LOG target ("LOG
  1127. target support", below) and to avoid some Denial of Service attacks.
  1128. To compile it as a module, choose M here. If unsure, say N.
  1129. config NETFILTER_XT_MATCH_MAC
  1130. tristate '"mac" address match support'
  1131. depends on NETFILTER_ADVANCED
  1132. help
  1133. MAC matching allows you to match packets based on the source
  1134. Ethernet address of the packet.
  1135. To compile it as a module, choose M here. If unsure, say N.
  1136. config NETFILTER_XT_MATCH_MARK
  1137. tristate '"mark" match support'
  1138. depends on NETFILTER_ADVANCED
  1139. select NETFILTER_XT_MARK
  1140. help
  1141. This is a backwards-compat option for the user's convenience
  1142. (e.g. when running oldconfig). It selects
  1143. CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
  1144. config NETFILTER_XT_MATCH_MULTIPORT
  1145. tristate '"multiport" Multiple port match support'
  1146. depends on NETFILTER_ADVANCED
  1147. help
  1148. Multiport matching allows you to match TCP or UDP packets based on
  1149. a series of source or destination ports: normally a rule can only
  1150. match a single range of ports.
  1151. To compile it as a module, choose M here. If unsure, say N.
  1152. config NETFILTER_XT_MATCH_NFACCT
  1153. tristate '"nfacct" match support'
  1154. depends on NETFILTER_ADVANCED
  1155. select NETFILTER_NETLINK_ACCT
  1156. help
  1157. This option allows you to use the extended accounting through
  1158. nfnetlink_acct.
  1159. To compile it as a module, choose M here. If unsure, say N.
  1160. config NETFILTER_XT_MATCH_OSF
  1161. tristate '"osf" Passive OS fingerprint match'
  1162. depends on NETFILTER_ADVANCED
  1163. select NETFILTER_NETLINK_OSF
  1164. help
  1165. This option selects the Passive OS Fingerprinting match module
  1166. that allows to passively match the remote operating system by
  1167. analyzing incoming TCP SYN packets.
  1168. Rules and loading software can be downloaded from
  1169. http://www.ioremap.net/projects/osf
  1170. To compile it as a module, choose M here. If unsure, say N.
  1171. config NETFILTER_XT_MATCH_OWNER
  1172. tristate '"owner" match support'
  1173. depends on NETFILTER_ADVANCED
  1174. help
  1175. Socket owner matching allows you to match locally-generated packets
  1176. based on who created the socket: the user or group. It is also
  1177. possible to check whether a socket actually exists.
  1178. config NETFILTER_XT_MATCH_POLICY
  1179. tristate 'IPsec "policy" match support'
  1180. depends on XFRM
  1181. default m if NETFILTER_ADVANCED=n
  1182. help
  1183. Policy matching allows you to match packets based on the
  1184. IPsec policy that was used during decapsulation/will
  1185. be used during encapsulation.
  1186. To compile it as a module, choose M here. If unsure, say N.
  1187. config NETFILTER_XT_MATCH_PHYSDEV
  1188. tristate '"physdev" match support'
  1189. depends on BRIDGE && BRIDGE_NETFILTER
  1190. depends on NETFILTER_ADVANCED
  1191. help
  1192. Physdev packet matching matches against the physical bridge ports
  1193. the IP packet arrived on or will leave by.
  1194. To compile it as a module, choose M here. If unsure, say N.
  1195. config NETFILTER_XT_MATCH_PKTTYPE
  1196. tristate '"pkttype" packet type match support'
  1197. depends on NETFILTER_ADVANCED
  1198. help
  1199. Packet type matching allows you to match a packet by
  1200. its "class", eg. BROADCAST, MULTICAST, ...
  1201. Typical usage:
  1202. iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
  1203. To compile it as a module, choose M here. If unsure, say N.
  1204. config NETFILTER_XT_MATCH_QUOTA
  1205. tristate '"quota" match support'
  1206. depends on NETFILTER_ADVANCED
  1207. help
  1208. This option adds a `quota' match, which allows to match on a
  1209. byte counter.
  1210. If you want to compile it as a module, say M here and read
  1211. <file:Documentation/kbuild/modules.rst>. If unsure, say `N'.
  1212. config NETFILTER_XT_MATCH_QUOTA2
  1213. tristate '"quota2" match support'
  1214. depends on NETFILTER_ADVANCED
  1215. help
  1216. This option adds a `quota2' match, which allows to match on a
  1217. byte counter correctly and not per CPU.
  1218. It allows naming the quotas.
  1219. This is based on http://xtables-addons.git.sourceforge.net
  1220. If you want to compile it as a module, say M here and read
  1221. <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
  1222. config NETFILTER_XT_MATCH_QUOTA2_LOG
  1223. bool '"quota2" Netfilter LOG support'
  1224. depends on NETFILTER_XT_MATCH_QUOTA2
  1225. default n
  1226. help
  1227. This option allows `quota2' to log ONCE when a quota limit
  1228. is passed. It logs via NETLINK using the NETLINK_NFLOG family.
  1229. It logs similarly to how ipt_ULOG would without data.
  1230. If unsure, say `N'.
  1231. config NETFILTER_XT_MATCH_RATEEST
  1232. tristate '"rateest" match support'
  1233. depends on NETFILTER_ADVANCED
  1234. select NETFILTER_XT_TARGET_RATEEST
  1235. help
  1236. This option adds a `rateest' match, which allows to match on the
  1237. rate estimated by the RATEEST target.
  1238. To compile it as a module, choose M here. If unsure, say N.
  1239. config NETFILTER_XT_MATCH_REALM
  1240. tristate '"realm" match support'
  1241. depends on NETFILTER_ADVANCED
  1242. select IP_ROUTE_CLASSID
  1243. help
  1244. This option adds a `realm' match, which allows you to use the realm
  1245. key from the routing subsystem inside iptables.
  1246. This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
  1247. in tc world.
  1248. If you want to compile it as a module, say M here and read
  1249. <file:Documentation/kbuild/modules.rst>. If unsure, say `N'.
  1250. config NETFILTER_XT_MATCH_RECENT
  1251. tristate '"recent" match support'
  1252. depends on NETFILTER_ADVANCED
  1253. help
  1254. This match is used for creating one or many lists of recently
  1255. used addresses and then matching against that/those list(s).
  1256. Short options are available by using 'iptables -m recent -h'
  1257. Official Website: <http://snowman.net/projects/ipt_recent/>
  1258. config NETFILTER_XT_MATCH_SCTP
  1259. tristate '"sctp" protocol match support'
  1260. depends on NETFILTER_ADVANCED
  1261. default IP_SCTP
  1262. help
  1263. With this option enabled, you will be able to use the
  1264. `sctp' match in order to match on SCTP source/destination ports
  1265. and SCTP chunk types.
  1266. If you want to compile it as a module, say M here and read
  1267. <file:Documentation/kbuild/modules.rst>. If unsure, say `N'.
  1268. config NETFILTER_XT_MATCH_SOCKET
  1269. tristate '"socket" match support'
  1270. depends on NETFILTER_XTABLES
  1271. depends on NETFILTER_ADVANCED
  1272. depends on IPV6 || IPV6=n
  1273. depends on IP6_NF_IPTABLES || IP6_NF_IPTABLES=n
  1274. select NF_SOCKET_IPV4
  1275. select NF_SOCKET_IPV6 if IP6_NF_IPTABLES
  1276. select NF_DEFRAG_IPV4
  1277. select NF_DEFRAG_IPV6 if IP6_NF_IPTABLES != n
  1278. help
  1279. This option adds a `socket' match, which can be used to match
  1280. packets for which a TCP or UDP socket lookup finds a valid socket.
  1281. It can be used in combination with the MARK target and policy
  1282. routing to implement full featured non-locally bound sockets.
  1283. To compile it as a module, choose M here. If unsure, say N.
  1284. config NETFILTER_XT_MATCH_STATE
  1285. tristate '"state" match support'
  1286. depends on NF_CONNTRACK
  1287. default m if NETFILTER_ADVANCED=n
  1288. help
  1289. Connection state matching allows you to match packets based on their
  1290. relationship to a tracked connection (ie. previous packets). This
  1291. is a powerful tool for packet classification.
  1292. To compile it as a module, choose M here. If unsure, say N.
  1293. config NETFILTER_XT_MATCH_STATISTIC
  1294. tristate '"statistic" match support'
  1295. depends on NETFILTER_ADVANCED
  1296. help
  1297. This option adds a `statistic' match, which allows you to match
  1298. on packets periodically or randomly with a given percentage.
  1299. To compile it as a module, choose M here. If unsure, say N.
  1300. config NETFILTER_XT_MATCH_STRING
  1301. tristate '"string" match support'
  1302. depends on NETFILTER_ADVANCED
  1303. select TEXTSEARCH
  1304. select TEXTSEARCH_KMP
  1305. select TEXTSEARCH_BM
  1306. select TEXTSEARCH_FSM
  1307. help
  1308. This option adds a `string' match, which allows you to look for
  1309. pattern matchings in packets.
  1310. To compile it as a module, choose M here. If unsure, say N.
  1311. config NETFILTER_XT_MATCH_TCPMSS
  1312. tristate '"tcpmss" match support'
  1313. depends on NETFILTER_ADVANCED
  1314. help
  1315. This option adds a `tcpmss' match, which allows you to examine the
  1316. MSS value of TCP SYN packets, which control the maximum packet size
  1317. for that connection.
  1318. To compile it as a module, choose M here. If unsure, say N.
  1319. config NETFILTER_XT_MATCH_TIME
  1320. tristate '"time" match support'
  1321. depends on NETFILTER_ADVANCED
  1322. help
  1323. This option adds a "time" match, which allows you to match based on
  1324. the packet arrival time (at the machine which netfilter is running)
  1325. on) or departure time/date (for locally generated packets).
  1326. If you say Y here, try `iptables -m time --help` for
  1327. more information.
  1328. If you want to compile it as a module, say M here.
  1329. If unsure, say N.
  1330. config NETFILTER_XT_MATCH_U32
  1331. tristate '"u32" match support'
  1332. depends on NETFILTER_ADVANCED
  1333. help
  1334. u32 allows you to extract quantities of up to 4 bytes from a packet,
  1335. AND them with specified masks, shift them by specified amounts and
  1336. test whether the results are in any of a set of specified ranges.
  1337. The specification of what to extract is general enough to skip over
  1338. headers with lengths stored in the packet, as in IP or TCP header
  1339. lengths.
  1340. Details and examples are in the kernel module source.
  1341. endif # NETFILTER_XTABLES
  1342. endmenu
  1343. source "net/netfilter/ipset/Kconfig"
  1344. source "net/netfilter/ipvs/Kconfig"