Config.in.netfilter.core 7.3 KB

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