Config.in.netfilter.core 8.1 KB

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