1168 lines · 39.5 KB · Text
RawDownload
menu "Core Netfilter Configuration"	depends on NET && INET && NETFILTER config NETFILTER_NETLINK	tristate config NETFILTER_NETLINK_ACCTtristate "Netfilter NFACCT over NFNETLINK interface"	depends on NETFILTER_ADVANCED	select NETFILTER_NETLINK	help	  If this option is enabled, the kernel will include support	  for extended accounting via NFNETLINK. config NETFILTER_NETLINK_QUEUE	tristate "Netfilter NFQUEUE over NFNETLINK interface"	depends on NETFILTER_ADVANCED	select NETFILTER_NETLINK	help	  If this option is enabled, the kernel will include support	  for queueing packets via NFNETLINK.	  config NETFILTER_NETLINK_LOG	tristate "Netfilter LOG over NFNETLINK interface"	default m if NETFILTER_ADVANCED=n	select NETFILTER_NETLINK	help	  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. config NF_CONNTRACK	tristate "Netfilter connection tracking support"	default m if NETFILTER_ADVANCED=n	help	  Connection tracking keeps a record of what packets have passed	  through your machine, in order to figure out how they are related	  into connections. 	  This is required to do Masquerading or other kinds of Network	  Address Translation.  It can also be used to enhance packet	  filtering (see `Connection state match support' below). 	  To compile it as a module, choose M here.  If unsure, say N. if NF_CONNTRACK config NF_CONNTRACK_MARK	bool  'Connection mark tracking support'	depends on NETFILTER_ADVANCED	help	  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. config NF_CONNTRACK_SECMARK	bool  'Connection tracking security mark support'	depends on NETWORK_SECMARK	default m if NETFILTER_ADVANCED=n	help	  This option enables security markings to be applied to	  connections.  Typically they are copied to connections from	  packets using the CONNSECMARK target and copied back from	  connections to packets with the same target, with the packets	  being originally labeled via SECMARK. 	  If unsure, say 'N'. config NF_CONNTRACK_ZONES	bool  'Connection tracking zones'	depends on NETFILTER_ADVANCED	depends on NETFILTER_XT_TARGET_CT	help	  This option enables support for connection tracking zones.	  Normally, each connection needs to have a unique system wide	  identity. Connection tracking zones allow to have multiple	  connections using the same identity, as long as they are	  contained in different zones. 	  If unsure, say `N'. config NF_CONNTRACK_PROCFS	bool "Supply CT list in procfs (OBSOLETE)"	default y	depends on PROC_FS	---help---	This option enables for the list of known conntrack entries	to be shown in procfs under net/netfilter/nf_conntrack. This	is considered obsolete in favor of using the conntrack(8)	tool which uses Netlink. config NF_CONNTRACK_EVENTS	bool "Connection tracking events"	depends on NETFILTER_ADVANCED	help	  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 about changes in the connection tracking state. 	  If unsure, say `N'. config NF_CONNTRACK_TIMEOUT	bool  'Connection tracking timeout'	depends on NETFILTER_ADVANCED	help	  This option enables support for connection tracking timeout	  extension. This allows you to attach timeout policies to flow	  via the CT target. 	  If unsure, say `N'. config NF_CONNTRACK_TIMESTAMP	bool  'Connection tracking timestamping'	depends on NETFILTER_ADVANCED	help	  This option enables support for connection tracking timestamping.	  This allows you to store the flow start-time and to obtain	  the flow-stop time (once it has been destroyed) via Connection	  tracking events. 	  If unsure, say `N'. config NF_CT_PROTO_DCCP	tristate 'DCCP protocol connection tracking support (EXPERIMENTAL)'	depends on EXPERIMENTAL	depends on NETFILTER_ADVANCED	default IP_DCCP	help	  With this option enabled, the layer 3 independent connection	  tracking code will be able to do state tracking on DCCP connections. 	  If unsure, say 'N'. config NF_CT_PROTO_GRE	tristate config NF_CT_PROTO_SCTP	tristate 'SCTP protocol connection tracking support (EXPERIMENTAL)'	depends on EXPERIMENTAL	depends on NETFILTER_ADVANCED	default IP_SCTP	help	  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	  <file:Documentation/kbuild/modules.txt>.  If unsure, say `N'. config NF_CT_PROTO_UDPLITE	tristate 'UDP-Lite protocol connection tracking support'	depends on NETFILTER_ADVANCED	help	  With this option enabled, the layer 3 independent connection	  tracking code will be able to do state tracking on UDP-Lite	  connections. 	  To compile it as a module, choose M here.  If unsure, say N. config NF_CONNTRACK_AMANDA	tristate "Amanda backup protocol support"	depends on NETFILTER_ADVANCED	select TEXTSEARCH	select TEXTSEARCH_KMP	help	  If you are running the Amanda backup package <http://www.amanda.org/>	  on this machine or machines that will be MASQUERADED through this	  machine, then you may want to enable this feature.  This allows the	  connection tracking and natting code to allow the sub-channels that	  Amanda requires for communication of the backup data, messages and	  index. 	  To compile it as a module, choose M here.  If unsure, say N. config NF_CONNTRACK_FTP	tristate "FTP protocol support"	default m if NETFILTER_ADVANCED=n	help	  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. config NF_CONNTRACK_H323	tristate "H.323 protocol support"	depends on (IPV6 || IPV6=n)	depends on NETFILTER_ADVANCED	help	  H.323 is a VoIP signalling protocol from ITU-T. As one of the most	  important VoIP protocols, it is widely used by voice hardware and	  software including voice gateways, IP phones, Netmeeting, OpenPhone,	  Gnomemeeting, etc. 	  With this module you can support H.323 on a connection tracking/NAT	  firewall. 	  This module supports RAS, Fast Start, H.245 Tunnelling, Call	  Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,	  whiteboard, file transfer, etc. For more information, please	  visit http://nath323.sourceforge.net/. 	  To compile it as a module, choose M here.  If unsure, say N. config NF_CONNTRACK_IRC	tristate "IRC protocol support"	default m if NETFILTER_ADVANCED=n	help	  There is a commonly-used extension to IRC called	  Direct Client-to-Client Protocol (DCC).  This enables users to send	  files to each other, and also chat to each other without the need	  of a server.  DCC Sending is used anywhere you send files over IRC,	  and DCC Chat is most commonly used by Eggdrop bots.  If you are	  using NAT, this extension will enable you to send files and initiate	  chats.  Note that you do NOT need this extension to get files or	  have others initiate chats, or everything else in IRC. 	  To compile it as a module, choose M here.  If unsure, say N. config NF_CONNTRACK_BROADCAST	tristate config NF_CONNTRACK_NETBIOS_NS	tristate "NetBIOS name service protocol support"	select NF_CONNTRACK_BROADCAST	help	  NetBIOS name service requests are sent as broadcast messages from an	  unprivileged port and responded to with unicast messages to the	  same port. This make them hard to firewall properly because connection	  tracking doesn't deal with broadcasts. This helper tracks locally	  originating NetBIOS name service requests and the corresponding	  responses. It relies on correct IP address configuration, specifically	  netmask and broadcast address. When properly configured, the output	  of "ip address show" should look similar to this: 	  $ ip -4 address show eth0	  4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000	      inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0 	  To compile it as a module, choose M here.  If unsure, say N. config NF_CONNTRACK_SNMP	tristate "SNMP service protocol support"	depends on NETFILTER_ADVANCED	select NF_CONNTRACK_BROADCAST	help	  SNMP service requests are sent as broadcast messages from an	  unprivileged port and responded to with unicast messages to the	  same port. This make them hard to firewall properly because connection	  tracking doesn't deal with broadcasts. This helper tracks locally	  originating SNMP service requests and the corresponding	  responses. It relies on correct IP address configuration, specifically	  netmask and broadcast address. 	  To compile it as a module, choose M here.  If unsure, say N. config NF_CONNTRACK_PPTP	tristate "PPtP protocol support"	depends on NETFILTER_ADVANCED	select NF_CT_PROTO_GRE	help	  This module adds support for PPTP (Point to Point Tunnelling	  Protocol, RFC2637) connection tracking and NAT. 	  If you are running PPTP sessions over a stateful firewall or NAT	  box, you may want to enable this feature. 	  Please note that not all PPTP modes of operation are supported yet.	  Specifically these limitations exist:	    - Blindly assumes that control connections are always established	      in PNS->PAC direction. This is a violation of RFC2637.	    - Only supports a single call within each session 	  To compile it as a module, choose M here.  If unsure, say N. config NF_CONNTRACK_SANE	tristate "SANE protocol support (EXPERIMENTAL)"	depends on EXPERIMENTAL	depends on NETFILTER_ADVANCED	help	  SANE is a protocol for remote access to scanners as implemented	  by the 'saned' daemon. Like FTP, it uses separate control and	  data connections. 	  With this module you can support SANE on a connection tracking	  firewall. 	  To compile it as a module, choose M here.  If unsure, say N. config NF_CONNTRACK_SIP	tristate "SIP protocol support"	default m if NETFILTER_ADVANCED=n	help	  SIP is an application-layer control protocol that can establish,	  modify, and terminate multimedia sessions (conferences) such as	  Internet telephony calls. With the ip_conntrack_sip and	  the nf_nat_sip modules you can support the protocol on a connection	  tracking/NATing firewall. 	  To compile it as a module, choose M here.  If unsure, say N. config NF_CONNTRACK_TFTP	tristate "TFTP protocol support"	depends on NETFILTER_ADVANCED	help	  TFTP connection tracking helper, this is required depending	  on how restrictive your ruleset is.	  If you are using a tftp client behind -j SNAT or -j MASQUERADING	  you will need this. 	  To compile it as a module, choose M here.  If unsure, say N. config NF_CT_NETLINK	tristate 'Connection tracking netlink interface'	select NETFILTER_NETLINK	default m if NETFILTER_ADVANCED=n	help	  This option enables support for a netlink-based userspace interface config NF_CT_NETLINK_TIMEOUT	tristate  'Connection tracking timeout tuning via Netlink'	select NETFILTER_NETLINK	depends on NETFILTER_ADVANCED	help	  This option enables support for connection tracking timeout	  fine-grain tuning. This allows you to attach specific timeout	  policies to flows, instead of using the global timeout policy. 	  If unsure, say `N'. endif # NF_CONNTRACK # transparent proxy supportconfig NETFILTER_TPROXY	tristate "Transparent proxying support (EXPERIMENTAL)"	depends on EXPERIMENTAL	depends on IP_NF_MANGLE	depends on NETFILTER_ADVANCED	help	  This option enables transparent proxying support, that is,	  support for handling non-locally bound IPv4 TCP and UDP sockets.	  For it to work you will have to configure certain iptables rules	  and use policy routing. For more information on how to set it up	  see Documentation/networking/tproxy.txt. 	  To compile it as a module, choose M here.  If unsure, say N. config NETFILTER_XTABLES	tristate "Netfilter Xtables support (required for ip_tables)"	default m if NETFILTER_ADVANCED=n	help	  This is required if you intend to use any of ip_tables,	  ip6_tables or arp_tables. if NETFILTER_XTABLES comment "Xtables combined modules" config NETFILTER_XT_MARK	tristate 'nfmark target and match support'	default m if NETFILTER_ADVANCED=n	---help---	This option adds the "MARK" target and "mark" match. 	Netfilter mark matching allows you to match packets based on the	"nfmark" value in the packet.	The target allows you to create rules in the "mangle" table which alter	the netfilter mark (nfmark) field associated with the packet. 	Prior to routing, the nfmark can influence the routing method (see	"Use netfilter MARK value as routing key") and can also be used by	other subsystems to change their behavior. config NETFILTER_XT_CONNMARK	tristate 'ctmark target and match support'	depends on NF_CONNTRACK	depends on NETFILTER_ADVANCED	select NF_CONNTRACK_MARK	---help---	This option adds the "CONNMARK" target and "connmark" match. 	Netfilter allows you to store a mark value per connection (a.k.a.	ctmark), similarly to the packet mark (nfmark). Using this	target and match, you can set and match on this mark. config NETFILTER_XT_SET	tristate 'set target and match support'	depends on IP_SET	depends on NETFILTER_ADVANCED	help	  This option adds the "SET" target and "set" match. 	  Using this target and match, you can add/delete and match	  elements in the sets created by ipset(8). 	  To compile it as a module, choose M here.  If unsure, say N. # alphabetically ordered list of targets comment "Xtables targets" config NETFILTER_XT_TARGET_AUDIT	tristate "AUDIT target support"	depends on AUDIT	depends on NETFILTER_ADVANCED	---help---	  This option adds a 'AUDIT' target, which can be used to create	  audit records for packets dropped/accepted. 	  To compileit as a module, choose M here. If unsure, say N. config NETFILTER_XT_TARGET_CHECKSUM	tristate "CHECKSUM target support"	depends on IP_NF_MANGLE || IP6_NF_MANGLE	depends on NETFILTER_ADVANCED	---help---	  This option adds a `CHECKSUM' target, which can be used in the iptables mangle	  table. 	  You can use this target to compute and fill in the checksum in	  a packet that lacks a checksum.  This is particularly useful,	  if you need to work around old applications such as dhcp clients,	  that do not work well with checksum offloads, but don't want to disable	  checksum offload in your device. 	  To compile it as a module, choose M here.  If unsure, say N. config NETFILTER_XT_TARGET_CLASSIFY	tristate '"CLASSIFY" target support'	depends on NETFILTER_ADVANCED	help	  This option adds a `CLASSIFY' target, which enables the user to set	  the priority of a packet. Some qdiscs can use this value for	  classification, among these are:   	  atm, cbq, dsmark, pfifo_fast, htb, prio 	  To compile it as a module, choose M here.  If unsure, say N. config NETFILTER_XT_TARGET_CONNMARK	tristate  '"CONNMARK" target support'	depends on NF_CONNTRACK	depends on NETFILTER_ADVANCED	select NETFILTER_XT_CONNMARK	---help---	This is a backwards-compat option for the user's convenience	(e.g. when running oldconfig). It selects	CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module). config NETFILTER_XT_TARGET_CONNSECMARK	tristate '"CONNSECMARK" target support'	depends on NF_CONNTRACK && NF_CONNTRACK_SECMARK	default m if NETFILTER_ADVANCED=n	help	  The CONNSECMARK target copies security markings from packets	  to connections, and restores security markings from connections	  to packets (if the packets are not already marked).  This would	  normally be used in conjunction with the SECMARK target. 	  To compile it as a module, choose M here.  If unsure, say N. config NETFILTER_XT_TARGET_CT	tristate '"CT" target support'	depends on NF_CONNTRACK	depends on IP_NF_RAW || IP6_NF_RAW	depends on NETFILTER_ADVANCED	help	  This options adds a `CT' target, which allows to specify initial	  connection tracking parameters like events to be delivered and	  the helper to be used. 	  To compile it as a module, choose M here.  If unsure, say N. config NETFILTER_XT_TARGET_DSCP	tristate '"DSCP" and "TOS" target support'	depends on IP_NF_MANGLE || IP6_NF_MANGLE	depends on NETFILTER_ADVANCED	help	  This option adds a `DSCP' target, which allows you to manipulate	  the IPv4/IPv6 header DSCP field (differentiated services codepoint). 	  The DSCP field can have any value between 0x0 and 0x3f inclusive. 	  It also adds the "TOS" target, which allows you to create rules in	  the "mangle" table which alter the Type Of Service field of an IPv4	  or the Priority field of an IPv6 packet, prior to routing. 	  To compile it as a module, choose M here.  If unsure, say N. config NETFILTER_XT_TARGET_HL	tristate '"HL" hoplimit target support'	depends on IP_NF_MANGLE || IP6_NF_MANGLE	depends on NETFILTER_ADVANCED

Lines 1–500 of 1168.

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t