Config.in.netfilter.core 7.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182
  1. config ADK_KPACKAGE_KMOD_NF_CONNTRACK
  2. tristate 'Netfilter connection tracking support'
  3. select ADK_KERNEL_NETFILTER_XTABLES
  4. help
  5. Connection tracking keeps a record of what packets have passed
  6. through your machine, in order to figure out how they are related
  7. into connections.
  8. Layer 3 independent connection tracking is experimental scheme
  9. which generalize ip_conntrack to support other layer 3 protocols.
  10. config ADK_KPACKAGE_KMOD_NETFILTER_XT_TARGET_CLASSIFY
  11. tristate '"CLASSIFY" target support'
  12. select ADK_KERNEL_NETFILTER_XTABLES
  13. help
  14. This option adds a `CLASSIFY' target, which enables the user to set
  15. the priority of a packet. Some qdiscs can use this value for
  16. classification, among these are:
  17. atm, cbq, dsmark, pfifo_fast, htb, prio
  18. config ADK_KPACKAGE_KMOD_NETFILTER_XT_TARGET_CONNMARK
  19. tristate '"CONNMARK" target support'
  20. select ADK_KERNEL_NETFILTER_XTABLES
  21. select ADK_KPACKAGE_KMOD_NF_CONNTRACK
  22. help
  23. This option adds a `CONNMARK' target, which allows one to manipulate
  24. the connection mark value. Similar to the MARK target, but
  25. affects the connection mark value rather than the packet mark value.
  26. config ADK_KPACKAGE_KMOD_NETFILTER_XT_TARGET_MARK
  27. tristate '"MARK" target support'
  28. select ADK_KERNEL_NETFILTER_XTABLES
  29. help
  30. This option adds a `MARK' target, which allows you to create rules
  31. in the `mangle' table which alter the netfilter mark (nfmark) field
  32. associated with the packet prior to routing. This can change
  33. the routing method (see `Use netfilter MARK value as routing
  34. key') and can also be used by other subsystems to change their
  35. behavior.
  36. config ADK_KPACKAGE_KMOD_NETFILTER_XT_TARGET_NFQUEUE
  37. tristate '"NFQUEUE" target support'
  38. select ADK_KERNEL_NETFILTER_XTABLES
  39. help
  40. This target replaced the old obsolete QUEUE target.
  41. As opposed to QUEUE, it supports 65535 different queues,
  42. not just one.
  43. config ADK_KPACKAGE_KMOD_NETFILTER_XT_TARGET_TCPMSS
  44. tristate 'TCPMSS target'
  45. select ADK_KERNEL_NETFILTER_XTABLES
  46. help
  47. config ADK_KPACKAGE_KMOD_NF_CONNTRACK_MARK
  48. bool 'Connection mark tracking support'
  49. depends on ADK_KPACKAGE_KMOD_NF_CONNTRACK
  50. select ADK_KERNEL_IP_NF_MATCH_CONNMARK
  51. help
  52. This option enables support for connection marks, used by the
  53. `CONNMARK' target and `connmark' match. Similar to the mark value
  54. of packets, but this mark value is kept in the conntrack session
  55. instead of the individual packets.
  56. config ADK_KPACKAGE_KMOD_NF_CONNTRACK_SECMARK
  57. bool 'Connection tracking security mark support'
  58. depends on ADK_KPACKAGE_KMOD_NF_CONNTRACK
  59. #FIXME select NETWORK_SECMARK
  60. help
  61. This option enables security markings to be applied to
  62. connections. Typically they are copied to connections from
  63. packets using the CONNSECMARK target and copied back from
  64. connections to packets with the same target, with the packets
  65. being originally labeled via SECMARK.
  66. config ADK_KPACKAGE_KMOD_NF_CONNTRACK_FTP
  67. tristate 'FTP protocol support'
  68. depends on ADK_KPACKAGE_KMOD_NF_CONNTRACK
  69. help
  70. Tracking FTP connections is problematic: special helpers are
  71. required for tracking them, and doing masquerading and other forms
  72. of Network Address Translation on them.
  73. #config ADK_KPACKAGE_KMOD_NF_CONNTRACK_RTSP
  74. # tristate 'RTSP protocol support'
  75. # depends on ADK_KPACKAGE_KMOD_NF_CONNTRACK
  76. # help
  77. # Tracking RTSP connections might be required for IPTV.
  78. config ADK_KPACKAGE_KMOD_NF_CONNTRACK_IRC
  79. tristate 'IRC protocol support'
  80. depends on ADK_KPACKAGE_KMOD_NF_CONNTRACK
  81. help
  82. There is a commonly-used extension to IRC called
  83. Direct Client-to-Client Protocol (DCC). This enables users to send
  84. files to each other, and also chat to each other without the need
  85. of a server. DCC Sending is used anywhere you send files over IRC,
  86. and DCC Chat is most commonly used by Eggdrop bots. If you are
  87. using NAT, this extension will enable you to send files and initiate
  88. chats. Note that you do NOT need this extension to get files or
  89. have others initiate chats, or everything else in IRC.
  90. config ADK_KPACKAGE_KMOD_NF_CONNTRACK_NETBIOS_NS
  91. tristate 'NetBIOS name service protocol support (EXPERIMENTAL)'
  92. depends on ADK_KPACKAGE_KMOD_NF_CONNTRACK
  93. help
  94. NetBIOS name service requests are sent as broadcast messages from an
  95. unprivileged port and responded to with unicast messages to the
  96. same port. This make them hard to firewall properly because connection
  97. tracking doesn't deal with broadcasts. This helper tracks locally
  98. originating NetBIOS name service requests and the corresponding
  99. responses. It relies on correct IP address configuration, specifically
  100. netmask and broadcast address. When properly configured, the output
  101. of "ip address show" should look similar to this:
  102. $ ip -4 address show eth0
  103. 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
  104. inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
  105. config ADK_KPACKAGE_KMOD_NF_CONNTRACK_TFTP
  106. tristate 'TFTP protocol support'
  107. depends on ADK_KPACKAGE_KMOD_NF_CONNTRACK
  108. help
  109. TFTP connection tracking helper, this is required depending
  110. on how restrictive your ruleset is.
  111. If you are using a tftp client behind -j SNAT or -j MASQUERADING
  112. you will need this.
  113. #config ADK_KPACKAGE_KMOD_NF_CONNTRACK_AMANDA
  114. # tristate 'Amanda backup protocol support'
  115. # depends on ADK_KPACKAGE_KMOD_NF_CONNTRACK
  116. # #FIXME TEXTSEARCH && TEXTSEARCH_KMP
  117. # help
  118. # If you are running the Amanda backup package <http://www.amanda.org/>
  119. # on this machine or machines that will be MASQUERADED through this
  120. # machine, then you may want to enable this feature. This allows the
  121. # connection tracking and natting code to allow the sub-channels that
  122. # Amanda requires for communication of the backup data, messages and
  123. # index.
  124. config ADK_KPACKAGE_KMOD_NF_CONNTRACK_PPTP
  125. tristate 'PPTP protocol support'
  126. depends on ADK_KPACKAGE_KMOD_NF_CONNTRACK
  127. help
  128. This module adds support for PPTP (Point to Point Tunnelling
  129. Protocol, RFC2637) connection tracking and NAT.
  130. If you are running PPTP sessions over a stateful firewall or NAT
  131. box, you may want to enable this feature.
  132. Please note that not all PPTP modes of operation are supported yet.
  133. For more info, read top of the file
  134. net/ipv4/netfilter/ip_conntrack_pptp.c
  135. config ADK_KPACKAGE_KMOD_NF_CONNTRACK_H323
  136. tristate 'H.323 protocol support (EXPERIMENTAL)'
  137. depends on ADK_KPACKAGE_KMOD_NF_CONNTRACK
  138. help
  139. H.323 is a VoIP signalling protocol from ITU-T. As one of the most
  140. important VoIP protocols, it is widely used by voice hardware and
  141. software including voice gateways, IP phones, Netmeeting, OpenPhone,
  142. Gnomemeeting, etc.
  143. With this module you can support H.323 on a connection tracking/NAT
  144. firewall.
  145. This module supports RAS, Fast Start, H.245 Tunnelling, Call
  146. Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
  147. whiteboard, file transfer, etc. For more information, please
  148. visit http://nath323.sourceforge.net/.
  149. config ADK_KPACKAGE_KMOD_NF_CONNTRACK_SIP
  150. tristate 'SIP protocol support (EXPERIMENTAL)'
  151. depends on ADK_KPACKAGE_KMOD_NF_CONNTRACK
  152. help
  153. SIP is an application-layer control protocol that can establish,
  154. modify, and terminate multimedia sessions (conferences) such as
  155. Internet telephony calls. With the ip_conntrack_sip and
  156. the ip_nat_sip modules you can support the protocol on a connection
  157. tracking/NATing firewall.