Kconfig 3.3 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798
  1. menu "Core Netfilter Configuration"
  2. depends on NET && NETFILTER
  3. config NETFILTER_NETLINK
  4. tristate "Netfilter netlink interface"
  5. help
  6. If this option is enabled, the kernel will include support
  7. for the new netfilter netlink interface.
  8. config NETFILTER_NETLINK_QUEUE
  9. tristate "Netfilter NFQUEUE over NFNETLINK interface"
  10. depends on NETFILTER_NETLINK
  11. help
  12. If this option isenabled, the kernel will include support
  13. for queueing packets via NFNETLINK.
  14. config NETFILTER_NETLINK_LOG
  15. tristate "Netfilter LOG over NFNETLINK interface"
  16. depends on NETFILTER_NETLINK
  17. help
  18. If this option is enabled, the kernel will include support
  19. for logging packets via NFNETLINK.
  20. This obsoletes the existing ipt_ULOG and ebg_ulog mechanisms,
  21. and is also scheduled to replace the old syslog-based ipt_LOG
  22. and ip6t_LOG modules.
  23. config NF_CONNTRACK
  24. tristate "Layer 3 Independent Connection tracking (EXPERIMENTAL)"
  25. depends on EXPERIMENTAL && IP_NF_CONNTRACK=n
  26. default n
  27. ---help---
  28. Connection tracking keeps a record of what packets have passed
  29. through your machine, in order to figure out how they are related
  30. into connections.
  31. Layer 3 independent connection tracking is experimental scheme
  32. which generalize ip_conntrack to support other layer 3 protocols.
  33. To compile it as a module, choose M here. If unsure, say N.
  34. config NF_CT_ACCT
  35. bool "Connection tracking flow accounting"
  36. depends on NF_CONNTRACK
  37. help
  38. If this option is enabled, the connection tracking code will
  39. keep per-flow packet and byte counters.
  40. Those counters can be used for flow-based accounting or the
  41. `connbytes' match.
  42. If unsure, say `N'.
  43. config NF_CONNTRACK_MARK
  44. bool 'Connection mark tracking support'
  45. depends on NF_CONNTRACK
  46. help
  47. This option enables support for connection marks, used by the
  48. `CONNMARK' target and `connmark' match. Similar to the mark value
  49. of packets, but this mark value is kept in the conntrack session
  50. instead of the individual packets.
  51. config NF_CONNTRACK_EVENTS
  52. bool "Connection tracking events (EXPERIMENTAL)"
  53. depends on EXPERIMENTAL && NF_CONNTRACK
  54. help
  55. If this option is enabled, the connection tracking code will
  56. provide a notifier chain that can be used by other kernel code
  57. to get notified aboutchanges in the connection tracking state.
  58. If unsure, say `N'.
  59. config NF_CT_PROTO_SCTP
  60. tristate 'SCTP protocol on new connection tracking support (EXPERIMENTAL)'
  61. depends on EXPERIMENTAL && NF_CONNTRACK
  62. default n
  63. help
  64. With this option enabled, the layer 3 independent connection
  65. tracking code will be able to do state tracking on SCTP connections.
  66. If you want to compile it as a module, say M here and read
  67. Documentation/modules.txt. If unsure, say `N'.
  68. config NF_CONNTRACK_FTP
  69. tristate "FTP support on new connection tracking (EXPERIMENTAL)"
  70. depends on EXPERIMENTAL && NF_CONNTRACK
  71. help
  72. Tracking FTP connections is problematic: special helpers are
  73. required for tracking them, and doing masquerading and other forms
  74. of Network Address Translation on them.
  75. This is FTP support on Layer 3 independent connection tracking.
  76. Layer 3 independent connection tracking is experimental scheme
  77. which generalize ip_conntrack to support other layer 3 protocols.
  78. To compile it as a module, choose M here. If unsure, say N.
  79. endmenu