1 # This file is part of the OpenADK project. OpenADK is copyrighted
2 # material, please see the LICENCE file in the top-level directory.
4 config ADK_WALDUX_KERNEL_NF_CONNTRACK
5 tristate 'Netfilter connection tracking support'
6 select ADK_WALDUX_KERNEL_NETFILTER_XTABLES
9 Connection tracking keeps a record of what packets have passed
10 through your machine, in order to figure out how they are related
13 Layer 3 independent connection tracking is experimental scheme
14 which generalize ip_conntrack to support other layer 3 protocols.
16 menu "Netfilter connection tracking support for special protocols"
17 depends on ADK_WALDUX_KERNEL_NF_CONNTRACK
19 config ADK_WALDUX_KERNEL_NF_CONNTRACK_MARK
20 bool 'Connection mark tracking support'
21 depends on ADK_WALDUX_KERNEL_NF_CONNTRACK
22 select ADK_WALDUX_KERNEL_IP_NF_MATCH_CONNMARK
24 This option enables support for connection marks, used by the
25 `CONNMARK' target and `connmark' match. Similar to the mark value
26 of packets, but this mark value is kept in the conntrack session
27 instead of the individual packets.
29 config ADK_WALDUX_KERNEL_NF_CONNTRACK_SECMARK
30 bool 'Connection tracking security mark support'
31 depends on ADK_WALDUX_KERNEL_NF_CONNTRACK
32 #FIXME select NETWORK_SECMARK
34 This option enables security markings to be applied to
35 connections. Typically they are copied to connections from
36 packets using the CONNSECMARK target and copied back from
37 connections to packets with the same target, with the packets
38 being originally labeled via SECMARK.
40 config ADK_WALDUX_KERNEL_NF_CONNTRACK_FTP
41 tristate 'FTP protocol support'
42 depends on ADK_WALDUX_KERNEL_NF_CONNTRACK
44 Tracking FTP connections is problematic: special helpers are
45 required for tracking them, and doing masquerading and other forms
46 of Network Address Translation on them.
48 config ADK_WALDUX_KERNEL_NF_CONNTRACK_IRC
49 tristate 'IRC protocol support'
50 depends on ADK_WALDUX_KERNEL_NF_CONNTRACK
52 There is a commonly-used extension to IRC called
53 Direct Client-to-Client Protocol (DCC). This enables users to send
54 files to each other, and also chat to each other without the need
55 of a server. DCC Sending is used anywhere you send files over IRC,
56 and DCC Chat is most commonly used by Eggdrop bots. If you are
57 using NAT, this extension will enable you to send files and initiate
58 chats. Note that you do NOT need this extension to get files or
59 have others initiate chats, or everything else in IRC.
61 config ADK_WALDUX_KERNEL_NF_CONNTRACK_NETBIOS_NS
62 tristate 'NetBIOS name service protocol support'
63 depends on ADK_WALDUX_KERNEL_NF_CONNTRACK
65 NetBIOS name service requests are sent as broadcast messages from an
66 unprivileged port and responded to with unicast messages to the
67 same port. This make them hard to firewall properly because connection
68 tracking doesn't deal with broadcasts. This helper tracks locally
69 originating NetBIOS name service requests and the corresponding
70 responses. It relies on correct IP address configuration, specifically
71 netmask and broadcast address. When properly configured, the output
72 of "ip address show" should look similar to this:
74 $ ip -4 address show eth0
75 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
76 inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
78 config ADK_WALDUX_KERNEL_NF_CONNTRACK_TFTP
79 tristate 'TFTP protocol support'
80 depends on ADK_WALDUX_KERNEL_NF_CONNTRACK
82 TFTP connection tracking helper, this is required depending
83 on how restrictive your ruleset is.
84 If you are using a tftp client behind -j SNAT or -j MASQUERADING
87 config ADK_WALDUX_KERNEL_NF_CONNTRACK_PPTP
88 tristate 'PPTP protocol support'
89 depends on ADK_WALDUX_KERNEL_NF_CONNTRACK
91 This module adds support for PPTP (Point to Point Tunnelling
92 Protocol, RFC2637) connection tracking and NAT.
94 If you are running PPTP sessions over a stateful firewall or NAT
95 box, you may want to enable this feature.
97 Please note that not all PPTP modes of operation are supported yet.
98 For more info, read top of the file
99 net/ipv4/netfilter/ip_conntrack_pptp.c
101 config ADK_WALDUX_KERNEL_NF_CONNTRACK_H323
102 tristate 'H.323 protocol support'
103 depends on ADK_WALDUX_KERNEL_NF_CONNTRACK
105 H.323 is a VoIP signalling protocol from ITU-T. As one of the most
106 important VoIP protocols, it is widely used by voice hardware and
107 software including voice gateways, IP phones, Netmeeting, OpenPhone,
110 With this module you can support H.323 on a connection tracking/NAT
113 This module supports RAS, Fast Start, H.245 Tunnelling, Call
114 Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
115 whiteboard, file transfer, etc. For more information, please
116 visit http://nath323.sourceforge.net/.
118 config ADK_WALDUX_KERNEL_NF_CONNTRACK_SIP
119 tristate 'SIP protocol support'
120 depends on ADK_WALDUX_KERNEL_NF_CONNTRACK
122 SIP is an application-layer control protocol that can establish,
123 modify, and terminate multimedia sessions (conferences) such as
124 Internet telephony calls. With the ip_conntrack_sip and
125 the ip_nat_sip modules you can support the protocol on a connection
126 tracking/NATing firewall.
130 config ADK_WALDUX_KERNEL_NETFILTER_NETLINK_LOG
131 tristate 'Netfilter LOG over NFNETLINK interface'
133 If this option is enabled, the kernel will include support
134 for logging packets via NFNETLINK.
136 menu "Netfilter target support"
138 config ADK_WALDUX_KERNEL_NETFILTER_XT_TARGET_CHECKSUM
139 tristate '"CHECKSUM" target support'
140 select ADK_WALDUX_KERNEL_IP_NF_IPTABLES
141 select ADK_WALDUX_KERNEL_NETFILTER_XTABLES
142 select ADK_WALDUX_KERNEL_IP_NF_MANGLE
143 select ADK_WALDUX_KERNEL_NETFILTER_ADVANCED
145 config ADK_WALDUX_KERNEL_NETFILTER_XT_TARGET_CLASSIFY
146 tristate '"CLASSIFY" target support'
147 select ADK_WALDUX_KERNEL_NETFILTER_XTABLES
149 This option adds a `CLASSIFY' target, which enables the user to set
150 the priority of a packet. Some qdiscs can use this value for
151 classification, among these are:
153 atm, cbq, dsmark, pfifo_fast, htb, prio
155 config ADK_WALDUX_KERNEL_NETFILTER_XT_TARGET_CONNMARK
156 tristate '"CONNMARK" target support'
157 select ADK_WALDUX_KERNEL_NETFILTER_XTABLES
158 select ADK_WALDUX_KERNEL_NF_CONNTRACK
160 This option adds a `CONNMARK' target, which allows one to manipulate
161 the connection mark value. Similar to the MARK target, but
162 affects the connection mark value rather than the packet mark value.
164 config ADK_WALDUX_KERNEL_NETFILTER_XT_TARGET_MARK
165 tristate '"MARK" target support'
166 select ADK_WALDUX_KERNEL_NETFILTER_XTABLES
168 This option adds a `MARK' target, which allows you to create rules
169 in the `mangle' table which alter the netfilter mark (nfmark) field
170 associated with the packet prior to routing. This can change
171 the routing method (see `Use netfilter MARK value as routing
172 key') and can also be used by other subsystems to change their
175 config ADK_WALDUX_KERNEL_NETFILTER_XT_TARGET_NFQUEUE
176 tristate '"NFQUEUE" target support'
177 select ADK_WALDUX_KERNEL_NETFILTER_XTABLES
179 This target replaced the old obsolete QUEUE target.
181 As opposed to QUEUE, it supports 65535 different queues,
184 config ADK_WALDUX_KERNEL_NETFILTER_XT_TARGET_LOG
185 tristate '"LOG" target support'
186 depends on ADK_WALDUX_KERNEL_IP_NF_FILTER
188 This option adds a `LOG' target, which allows you to create rules in
189 any iptables table which records the packet header to the syslog.
191 config ADK_WALDUX_KERNEL_NETFILTER_XT_TARGET_TCPMSS
192 tristate '"TCPMSS" target support'
193 select ADK_WALDUX_KERNEL_NETFILTER_XTABLES