Config.in.netfilter.core 7.2 KB

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