Guide to configuring the linux kernel/net/netfilter

Guide to configuring the linux kernel / net / netfilter

=Core Netfilter Configuration=
 * depends on NET && NETFILTER


 * Option: NETFILTER NETLINK
 * tristate "Netfilter netlink interface"
 * If this option is enabled, the kernel will include support  for the new netfilter netlink interface.


 * Option: NETFILTER NETLINK QUEUE
 * tristate "Netfilter NFQUEUE over NFNETLINK interface"
 * depends on NETFILTER NETLINK
 * If this option isenabled, the kernel will include support for queueing packets via NFNETLINK.


 * Option: NETFILTER NETLINK LOG
 * tristate "Netfilter LOG over NFNETLINK interface"
 * depends on NETFILTER NETLINK
 * If this option is enabled, the kernel will include support for logging packets via NFNETLINK.
 * This obsoletes the existing ipt ULOG and ebg ulog mechanisms, and is also scheduled to replace the old syslog-based ipt LOG and ip6t LOG modules.


 * Option: NF CONNTRACK
 * tristate "Layer 3 Independent Connection tracking (EXPERIMENTAL)"
 * depends on EXPERIMENTAL && IP NF CONNTRACK=n default n
 * Connection tracking keeps a record of what packets have passed through your machine, in order to figure out how they are related into connections.
 * Layer 3 independent connection tracking is experimental scheme which generalize ip conntrack to support other layer 3 protocols.
 * To compile it as a module, choose M here. If unsure, say N.


 * Option: NF CT ACCT
 * bool "Connection tracking flow accounting"
 * depends on NF CONNTRACK
 * If this option is enabled, the connection tracking code will keep per-flow packet and byte counters.
 * Those counters can be used for flow-based accounting or the `connbytes' match.
 * If unsure, say `N'.

bool 'Connection mark tracking support' depends on NF CONNTRACK This option enables support for connection marks, used by the `CONNMARK' target and `connmark' match. Similar to the mark value of packets, but this mark value is kept in the conntrack session instead of the individual packets.
 * Option: NF CONNTRACK MARK


 * Option: NF CONNTRACK EVENTS
 * bool "Connection tracking events (EXPERIMENTAL)"
 * depends on EXPERIMENTAL && NF CONNTRACK
 * If this option is enabled, the connection tracking code will provide a notifier chain that can be used by other kernel code to get notified aboutchanges in the connection tracking state.
 * If unsure, say `N'.


 * Option: NF CT PROTO SCTP
 * tristate 'SCTP protocol on new connection tracking support (EXPERIMENTAL)'
 * depends on EXPERIMENTAL && NF CONNTRACK default n
 * With this option enabled, the layer 3 independent connection tracking code will be able to do state tracking on SCTP connections.
 * If you want to compile it as a module, say M here and read Documentation/modules.txt.
 * If unsure, say `N'.


 * Option: NF CONNTRACK FTP
 * tristate "FTP support on new connection tracking (EXPERIMENTAL)"
 * depends on EXPERIMENTAL && NF CONNTRACK
 * Tracking FTP connections is problematic: special helpers are required for tracking them, and doing masquerading and other forms of Network Address Translation on them.
 * This is FTP support on Layer 3 independent connection tracking. Layer 3 independent connection tracking is experimental scheme which generalize ip conntrack to support other layer 3 protocols.
 * To compile it as a module, choose M here. If unsure, say N.