Config.in.netfilter.ip4 5.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131
  1. config ADK_KPACKAGE_KMOD_NF_CONNTRACK_IPV4
  2. bool 'IPv4 connection tracking support (required for NAT)'
  3. select ADK_KPACKAGE_KMOD_NF_CONNTRACK
  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. config ADK_KPACKAGE_KMOD_IP_NF_CT_ACCT
  9. bool 'Connection tracking flow accounting'
  10. depends on ADK_KPACKAGE_KMOD_NF_CONNTRACK
  11. help
  12. If this option is enabled, the connection tracking code will
  13. keep per-flow packet and byte counters.
  14. Those counters can be used for flow-based accounting or the
  15. `connbytes' match.
  16. config ADK_KPACKAGE_KMOD_IP_NF_IPTABLES
  17. tristate 'IP tables support (required for filtering/masq/NAT)'
  18. select ADK_KERNEL_NETFILTER_XTABLES
  19. help
  20. iptables is a general, extensible packet identification framework.
  21. The packet filtering and full NAT (masquerading, port forwarding,
  22. etc) subsystems now use this: say `Y' or `M' here if you want to use
  23. either of those.
  24. config ADK_KPACKAGE_KMOD_IP_NF_FILTER
  25. tristate 'Packet Filtering'
  26. depends on ADK_KPACKAGE_KMOD_IP_NF_IPTABLES
  27. help
  28. Packet filtering defines a table `filter', which has a series of
  29. rules for simple packet filtering at local input, forwarding and
  30. local output. See the man page for iptables(8).
  31. config ADK_KPACKAGE_KMOD_FULL_NAT
  32. tristate "Meta package for Full NAT"
  33. select ADK_KPACKAGE_KMOD_NF_NAT if ADK_KERNEL_VERSION_3_4_71
  34. select ADK_KPACKAGE_KMOD_NF_NAT_IPV4 if ADK_KERNEL_VERSION_3_11_10
  35. select ADK_KPACKAGE_KMOD_NF_NAT_IPV4 if ADK_KERNEL_VERSION_3_12_6
  36. config ADK_KPACKAGE_KMOD_NF_NAT
  37. tristate 'Full NAT'
  38. depends on ADK_KPACKAGE_KMOD_IP_NF_IPTABLES
  39. depends on ADK_KERNEL_VERSION_3_4_71
  40. help
  41. The Full NAT option allows masquerading, port forwarding and other
  42. forms of full Network Address Port Translation. It is controlled by
  43. the `nat' table in iptables: see the man page for iptables(8).
  44. config ADK_KPACKAGE_KMOD_NF_NAT_IPV4
  45. tristate 'Full NAT'
  46. depends on ADK_KPACKAGE_KMOD_IP_NF_IPTABLES
  47. depends on ADK_KERNEL_VERSION_3_11_10 || ADK_KERNEL_VERSION_3_12_6
  48. help
  49. The Full NAT option allows masquerading, port forwarding and other
  50. forms of full Network Address Port Translation. It is controlled by
  51. the `nat' table in iptables: see the man page for iptables(8).
  52. config ADK_KPACKAGE_KMOD_IP_NF_TARGET_MASQUERADE
  53. tristate 'MASQUERADE target support'
  54. depends on ADK_KPACKAGE_KMOD_FULL_NAT
  55. help
  56. Masquerading is a special case of NAT: all outgoing connections are
  57. changed to seem to come from a particular interface's address, and
  58. if the interface goes down, those connections are lost. This is
  59. only useful for dialup accounts with dynamic IP address (ie. your IP
  60. address will be different on next dialup).
  61. config ADK_KPACKAGE_KMOD_IP_NF_TARGET_REJECT
  62. tristate 'REJECT target support'
  63. depends on ADK_KPACKAGE_KMOD_IP_NF_FILTER
  64. help
  65. The REJECT target allows a filtering rule to specify that an ICMP
  66. error should be issued in response to an incoming packet, rather
  67. than silently being dropped.
  68. config ADK_KPACKAGE_KMOD_IP_NF_TARGET_ULOG
  69. tristate 'ULOG target support (ipv4 only)'
  70. depends on ADK_KPACKAGE_KMOD_IP_NF_FILTER
  71. help
  72. This option enables the old IPv4-only "ipt_ULOG" implementation
  73. which has been obsoleted by the new "nfnetlink_log" code (see
  74. CONFIG_NETFILTER_NETLINK_LOG).
  75. This option adds a `ULOG' target, which allows you to create rules in
  76. any iptables table. The packet is passed to a userspace logging
  77. daemon using netlink multicast sockets; unlike the LOG target
  78. which can only be viewed through syslog.
  79. The appropriate userspace logging daemon (ulogd) may be obtained from
  80. <http://www.gnumonks.org/projects/ulogd/>
  81. config ADK_KPACKAGE_KMOD_IP_NF_TARGET_REDIRECT
  82. tristate 'REDIRECT target support'
  83. depends on ADK_KPACKAGE_KMOD_FULL_NAT
  84. help
  85. REDIRECT is a special case of NAT: all incoming connections are
  86. mapped onto the incoming interface's address, causing the packets to
  87. come to the local machine instead of passing through. This is
  88. useful for transparent proxies.
  89. config ADK_KPACKAGE_KMOD_IP_NF_TARGET_NETMAP
  90. tristate 'NETMAP target support'
  91. depends on ADK_KPACKAGE_KMOD_FULL_NAT
  92. help
  93. NETMAP is an implementation of static 1:1 NAT mapping of network
  94. addresses. It maps the network address part, while keeping the host
  95. address part intact. It is similar to Fast NAT, except that
  96. Netfilter's connection tracking doesn't work well with Fast NAT.
  97. config ADK_KPACKAGE_KMOD_IP_NF_MANGLE
  98. tristate 'Packet mangling'
  99. depends on ADK_KPACKAGE_KMOD_FULL_NAT
  100. help
  101. This option adds a `mangle' table to iptables: see the man page for
  102. iptables(8). This table is used for various packet alterations
  103. which can effect how the packet is routed.
  104. config ADK_KPACKAGE_KMOD_IP_NF_TARGET_ECN
  105. tristate 'ECN target support'
  106. depends on ADK_KPACKAGE_KMOD_IP_NF_MANGLE
  107. help
  108. This option adds a `ECN' target, which can be used in the iptables mangle
  109. table.
  110. You can use this target to remove the ECN bits from the IPv4 header of
  111. an IP packet. This is particularly useful, if you need to work around
  112. existing ECN blackholes on the internet, but don't want to disable
  113. ECN support in general.