Config.in.netfilter 22 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676
  1. menu "Netfilter (Firewall/Filtering)"
  2. config ADK_KERNEL_NETFILTER
  3. bool
  4. default n
  5. config ADK_KERNEL_NETFILTER_ADVANCED
  6. bool
  7. default n
  8. config ADK_KERNEL_BRIDGE_NETFILTER
  9. bool
  10. default n
  11. config ADK_KERNEL_NETFILTER_XTABLES
  12. bool
  13. select ADK_KERNEL_NETFILTER
  14. select ADK_KERNEL_NETFILTER_ADVANCED
  15. default n
  16. config ADK_KERNEL_NETFILTER_DEBUG
  17. bool
  18. default n
  19. config ADK_KERNEL_IP_NF_MATCH_LAYER7_DEBUG
  20. bool
  21. default n
  22. config ADK_KERNEL_IP_NF_TARGET_MIRROR
  23. tristate
  24. default n
  25. config ADK_KERNEL_IP_NF_NAT_SNMP_BASIC
  26. tristate
  27. default n
  28. config ADK_KERNEL_IP_NF_TARGET_DSCP
  29. tristate
  30. default n
  31. config ADK_KERNEL_IP_NF_TARGET_MARK
  32. tristate
  33. default n
  34. config ADK_KERNEL_IP_NF_TARGET_CLASSIFY
  35. tristate
  36. default n
  37. config ADK_KERNEL_IP_NF_TARGET_IMQ
  38. tristate
  39. default n
  40. config ADK_KERNEL_IP_NF_TARGET_CONNMARK
  41. tristate
  42. default n
  43. config ADK_KERNEL_IP_NF_ARPTABLES
  44. tristate
  45. default n
  46. config ADK_KERNEL_IP_NF_COMPAT_IPCHAINS
  47. tristate
  48. default n
  49. config ADK_KERNEL_IP_NF_COMPAT_IPFWADM
  50. tristate
  51. default n
  52. config ADK_KERNEL_IP6_NF_QUEUE
  53. tristate
  54. default n
  55. config ADK_KERNEL_IP6_NF_IPTABLES
  56. tristate
  57. default n
  58. config ADK_KERNEL_IP_ROUTE_FWMARK
  59. bool
  60. default n
  61. config ADK_KERNEL_IP_NF_QUEUE
  62. tristate
  63. default n
  64. config ADK_KERNEL_IP_NF_MATCH_TIME
  65. tristate
  66. default n
  67. config ADK_KERNEL_IP_NF_MATCH_CONDITION
  68. tristate
  69. default n
  70. config ADK_KERNEL_IP_NF_MATCH_DSCP
  71. tristate
  72. default n
  73. config ADK_KERNEL_IP_NF_MATCH_AH_ESP
  74. tristate
  75. default n
  76. config ADK_KERNEL_IP_NF_MATCH_LENGTH
  77. tristate
  78. default n
  79. config ADK_KERNEL_IP_NF_MATCH_HELPER
  80. tristate
  81. default n
  82. # cannot be ADK_KERNEL_IP_NF_MATCH_STATE because
  83. # netfilter is built as a module -> this'll always be
  84. # a module, too
  85. config ADK_KPACKAGE_KMOD_IP_NF_MATCH_STATE
  86. tristate
  87. select ADK_KPACKAGE_KMOD_NETFILTER_XT_MATCH_STATE
  88. default n
  89. config ADK_KPACKAGE_KMOD_NETFILTER_XT_MATCH_STATE
  90. tristate
  91. default n
  92. # cannot be ADK_KERNEL_IP_NF_MATCH_CONNTRACK because
  93. # netfilter is built as a module -> this'll always be
  94. # a module, too
  95. config ADK_KPACKAGE_KMOD_IP_NF_MATCH_CONNTRACK
  96. tristate
  97. default n
  98. config ADK_KERNEL_IP_NF_MATCH_CONNMARK
  99. tristate
  100. default n
  101. config ADK_KERNEL_IP_NF_MATCH_UNCLEAN
  102. tristate
  103. default n
  104. config ADK_KERNEL_IP_NF_MATCH_STRING
  105. tristate
  106. default n
  107. menu "Core Netfilter Configuration"
  108. config ADK_KPACKAGE_KMOD_NF_CONNTRACK
  109. tristate 'Netfilter connection tracking support'
  110. select ADK_KERNEL_NETFILTER_XTABLES
  111. help
  112. Connection tracking keeps a record of what packets have passed
  113. through your machine, in order to figure out how they are related
  114. into connections.
  115. Layer 3 independent connection tracking is experimental scheme
  116. which generalize ip_conntrack to support other layer 3 protocols.
  117. config ADK_KPACKAGE_KMOD_NETFILTER_XT_TARGET_CLASSIFY
  118. tristate '"CLASSIFY" target support'
  119. select ADK_KERNEL_NETFILTER_XTABLES
  120. help
  121. This option adds a `CLASSIFY' target, which enables the user to set
  122. the priority of a packet. Some qdiscs can use this value for
  123. classification, among these are:
  124. atm, cbq, dsmark, pfifo_fast, htb, prio
  125. config ADK_KPACKAGE_KMOD_NETFILTER_XT_TARGET_CONNMARK
  126. tristate '"CONNMARK" target support'
  127. select ADK_KERNEL_NETFILTER_XTABLES
  128. select ADK_KPACKAGE_KMOD_NF_CONNTRACK
  129. help
  130. This option adds a `CONNMARK' target, which allows one to manipulate
  131. the connection mark value. Similar to the MARK target, but
  132. affects the connection mark value rather than the packet mark value.
  133. config ADK_KPACKAGE_KMOD_NETFILTER_XT_TARGET_MARK
  134. tristate '"MARK" target support'
  135. select ADK_KERNEL_NETFILTER_XTABLES
  136. help
  137. This option adds a `MARK' target, which allows you to create rules
  138. in the `mangle' table which alter the netfilter mark (nfmark) field
  139. associated with the packet prior to routing. This can change
  140. the routing method (see `Use netfilter MARK value as routing
  141. key') and can also be used by other subsystems to change their
  142. behavior.
  143. config ADK_KPACKAGE_KMOD_NETFILTER_XT_TARGET_NFQUEUE
  144. tristate '"NFQUEUE" target support'
  145. select ADK_KERNEL_NETFILTER_XTABLES
  146. help
  147. This target replaced the old obsolete QUEUE target.
  148. As opposed to QUEUE, it supports 65535 different queues,
  149. not just one.
  150. endmenu
  151. menu "IP: Netfilter Configuration"
  152. config ADK_KPACKAGE_KMOD_NF_CONNTRACK_IPV4
  153. bool 'IPv4 connection tracking support (required for NAT)'
  154. select ADK_KPACKAGE_KMOD_NF_CONNTRACK
  155. help
  156. Connection tracking keeps a record of what packets have passed
  157. through your machine, in order to figure out how they are related
  158. into connections.
  159. config ADK_KPACKAGE_KMOD_IP_NF_CT_ACCT
  160. bool 'Connection tracking flow accounting'
  161. depends on ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK
  162. help
  163. If this option is enabled, the connection tracking code will
  164. keep per-flow packet and byte counters.
  165. Those counters can be used for flow-based accounting or the
  166. `connbytes' match.
  167. config ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK_MARK
  168. bool 'Connection mark tracking support'
  169. depends on ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK
  170. select ADK_KERNEL_IP_NF_MATCH_CONNMARK
  171. help
  172. This option enables support for connection marks, used by the
  173. `CONNMARK' target and `connmark' match. Similar to the mark value
  174. of packets, but this mark value is kept in the conntrack session
  175. instead of the individual packets.
  176. config ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK_SECMARK
  177. bool 'Connection tracking security mark support'
  178. depends on ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK
  179. #FIXME select NETWORK_SECMARK
  180. help
  181. This option enables security markings to be applied to
  182. connections. Typically they are copied to connections from
  183. packets using the CONNSECMARK target and copied back from
  184. connections to packets with the same target, with the packets
  185. being originally labeled via SECMARK.
  186. config ADK_KPACKAGE_KMOD_IP_NF_FTP
  187. tristate 'FTP protocol support'
  188. depends on ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK
  189. help
  190. Tracking FTP connections is problematic: special helpers are
  191. required for tracking them, and doing masquerading and other forms
  192. of Network Address Translation on them.
  193. config ADK_KPACKAGE_KMOD_IP_NF_IRC
  194. tristate 'IRC protocol support'
  195. depends on ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK
  196. help
  197. There is a commonly-used extension to IRC called
  198. Direct Client-to-Client Protocol (DCC). This enables users to send
  199. files to each other, and also chat to each other without the need
  200. of a server. DCC Sending is used anywhere you send files over IRC,
  201. and DCC Chat is most commonly used by Eggdrop bots. If you are
  202. using NAT, this extension will enable you to send files and initiate
  203. chats. Note that you do NOT need this extension to get files or
  204. have others initiate chats, or everything else in IRC.
  205. config ADK_KPACKAGE_KMOD_IP_NF_NETBIOS_NS
  206. tristate 'NetBIOS name service protocol support (EXPERIMENTAL)'
  207. depends on ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK
  208. help
  209. NetBIOS name service requests are sent as broadcast messages from an
  210. unprivileged port and responded to with unicast messages to the
  211. same port. This make them hard to firewall properly because connection
  212. tracking doesn't deal with broadcasts. This helper tracks locally
  213. originating NetBIOS name service requests and the corresponding
  214. responses. It relies on correct IP address configuration, specifically
  215. netmask and broadcast address. When properly configured, the output
  216. of "ip address show" should look similar to this:
  217. $ ip -4 address show eth0
  218. 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
  219. inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
  220. config ADK_KPACKAGE_KMOD_IP_NF_TFTP
  221. tristate 'TFTP protocol support'
  222. depends on ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK
  223. help
  224. TFTP connection tracking helper, this is required depending
  225. on how restrictive your ruleset is.
  226. If you are using a tftp client behind -j SNAT or -j MASQUERADING
  227. you will need this.
  228. config ADK_KPACKAGE_KMOD_IP_NF_AMANDA
  229. tristate 'Amanda backup protocol support'
  230. depends on ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK
  231. #FIXME TEXTSEARCH && TEXTSEARCH_KMP
  232. help
  233. If you are running the Amanda backup package <http://www.amanda.org/>
  234. on this machine or machines that will be MASQUERADED through this
  235. machine, then you may want to enable this feature. This allows the
  236. connection tracking and natting code to allow the sub-channels that
  237. Amanda requires for communication of the backup data, messages and
  238. index.
  239. config ADK_KPACKAGE_KMOD_IP_NF_PPTP
  240. tristate 'PPTP protocol support'
  241. depends on ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK
  242. help
  243. This module adds support for PPTP (Point to Point Tunnelling
  244. Protocol, RFC2637) connection tracking and NAT.
  245. If you are running PPTP sessions over a stateful firewall or NAT
  246. box, you may want to enable this feature.
  247. Please note that not all PPTP modes of operation are supported yet.
  248. For more info, read top of the file
  249. net/ipv4/netfilter/ip_conntrack_pptp.c
  250. config ADK_KPACKAGE_KMOD_IP_NF_H323
  251. tristate 'H.323 protocol support (EXPERIMENTAL)'
  252. depends on ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK
  253. help
  254. H.323 is a VoIP signalling protocol from ITU-T. As one of the most
  255. important VoIP protocols, it is widely used by voice hardware and
  256. software including voice gateways, IP phones, Netmeeting, OpenPhone,
  257. Gnomemeeting, etc.
  258. With this module you can support H.323 on a connection tracking/NAT
  259. firewall.
  260. This module supports RAS, Fast Start, H.245 Tunnelling, Call
  261. Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
  262. whiteboard, file transfer, etc. For more information, please
  263. visit http://nath323.sourceforge.net/.
  264. config ADK_KPACKAGE_KMOD_IP_NF_SIP
  265. tristate 'SIP protocol support (EXPERIMENTAL)'
  266. depends on ADK_KPACKAGE_KMOD_IP_NF_CONNTRACK
  267. help
  268. SIP is an application-layer control protocol that can establish,
  269. modify, and terminate multimedia sessions (conferences) such as
  270. Internet telephony calls. With the ip_conntrack_sip and
  271. the ip_nat_sip modules you can support the protocol on a connection
  272. tracking/NATing firewall.
  273. config ADK_KPACKAGE_KMOD_IP_NF_IPTABLES
  274. tristate 'IP tables support (required for filtering/masq/NAT)'
  275. select ADK_KERNEL_NETFILTER_XTABLES
  276. help
  277. iptables is a general, extensible packet identification framework.
  278. The packet filtering and full NAT (masquerading, port forwarding,
  279. etc) subsystems now use this: say `Y' or `M' here if you want to use
  280. either of those.
  281. config ADK_KPACKAGE_KMOD_IP_NF_FILTER
  282. tristate 'Packet Filtering'
  283. depends on ADK_KPACKAGE_KMOD_IP_NF_IPTABLES
  284. help
  285. Packet filtering defines a table `filter', which has a series of
  286. rules for simple packet filtering at local input, forwarding and
  287. local output. See the man page for iptables(8).
  288. config ADK_KPACKAGE_KMOD_NF_NAT
  289. tristate 'Full NAT'
  290. depends on ADK_KPACKAGE_KMOD_IP_NF_IPTABLES
  291. help
  292. The Full NAT option allows masquerading, port forwarding and other
  293. forms of full Network Address Port Translation. It is controlled by
  294. the `nat' table in iptables: see the man page for iptables(8).
  295. config ADK_KPACKAGE_KMOD_IP_NF_TARGET_MASQUERADE
  296. tristate 'MASQUERADE target support'
  297. depends on ADK_KPACKAGE_KMOD_NF_NAT
  298. help
  299. Masquerading is a special case of NAT: all outgoing connections are
  300. changed to seem to come from a particular interface's address, and
  301. if the interface goes down, those connections are lost. This is
  302. only useful for dialup accounts with dynamic IP address (ie. your IP
  303. address will be different on next dialup).
  304. config ADK_KPACKAGE_KMOD_IP_NF_TARGET_REJECT
  305. tristate 'REJECT target support'
  306. depends on ADK_KPACKAGE_KMOD_IP_NF_FILTER
  307. help
  308. The REJECT target allows a filtering rule to specify that an ICMP
  309. error should be issued in response to an incoming packet, rather
  310. than silently being dropped.
  311. config ADK_KPACKAGE_KMOD_IP_NF_TARGET_LOG
  312. tristate 'LOG target support'
  313. depends on ADK_KPACKAGE_KMOD_IP_NF_FILTER
  314. help
  315. This option adds a `LOG' target, which allows you to create rules in
  316. any iptables table which records the packet header to the syslog.
  317. config ADK_KPACKAGE_KMOD_IP_NF_TARGET_ULOG
  318. tristate 'ULOG target support (ipv4 only)'
  319. depends on ADK_KPACKAGE_KMOD_IP_NF_FILTER
  320. help
  321. This option enables the old IPv4-only "ipt_ULOG" implementation
  322. which has been obsoleted by the new "nfnetlink_log" code (see
  323. CONFIG_NETFILTER_NETLINK_LOG).
  324. This option adds a `ULOG' target, which allows you to create rules in
  325. any iptables table. The packet is passed to a userspace logging
  326. daemon using netlink multicast sockets; unlike the LOG target
  327. which can only be viewed through syslog.
  328. The appropriate userspace logging daemon (ulogd) may be obtained from
  329. <http://www.gnumonks.org/projects/ulogd/>
  330. config ADK_KPACKAGE_KMOD_IP_NF_TARGET_REDIRECT
  331. tristate 'REDIRECT target support'
  332. depends on ADK_KPACKAGE_KMOD_NF_NAT
  333. help
  334. REDIRECT is a special case of NAT: all incoming connections are
  335. mapped onto the incoming interface's address, causing the packets to
  336. come to the local machine instead of passing through. This is
  337. useful for transparent proxies.
  338. config ADK_KPACKAGE_KMOD_IP_NF_TARGET_NETMAP
  339. tristate 'NETMAP target support'
  340. depends on ADK_KPACKAGE_KMOD_NF_NAT
  341. help
  342. NETMAP is an implementation of static 1:1 NAT mapping of network
  343. addresses. It maps the network address part, while keeping the host
  344. address part intact. It is similar to Fast NAT, except that
  345. Netfilter's connection tracking doesn't work well with Fast NAT.
  346. config ADK_KPACKAGE_KMOD_IP_NF_MANGLE
  347. tristate 'Packet mangling'
  348. depends on ADK_KPACKAGE_KMOD_NF_NAT
  349. help
  350. This option adds a `mangle' table to iptables: see the man page for
  351. iptables(8). This table is used for various packet alterations
  352. which can effect how the packet is routed.
  353. config ADK_KPACKAGE_KMOD_IP_NF_TARGET_ECN
  354. tristate 'ECN target support'
  355. depends on ADK_KPACKAGE_KMOD_IP_NF_MANGLE
  356. help
  357. This option adds a `ECN' target, which can be used in the iptables mangle
  358. table.
  359. You can use this target to remove the ECN bits from the IPv4 header of
  360. an IP packet. This is particularly useful, if you need to work around
  361. existing ECN blackholes on the internet, but don't want to disable
  362. ECN support in general.
  363. endmenu
  364. menu "Ethernet bridge firewalling"
  365. config ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  366. tristate 'Ethernet Bridge tables (ebtables) support'
  367. select ADK_KERNEL_BRIDGE_NETFILTER
  368. help
  369. ebtables is a general, extensible frame/packet identification
  370. framework. Say 'Y' or 'M' here if you want to do Ethernet
  371. filtering/NAT/brouting on the Ethernet bridge.
  372. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_BROUTE
  373. tristate "ebt: broute table support"
  374. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  375. help
  376. The ebtables broute table is used to define rules that decide between
  377. bridging and routing frames, giving Linux the functionality of a
  378. brouter. See the man page for ebtables(8) and examples on the ebtables
  379. website.
  380. To compile it as a module, choose M here. If unsure, say N.
  381. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_T_FILTER
  382. tristate "ebt: filter table support"
  383. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  384. help
  385. The ebtables filter table is used to define frame filtering rules at
  386. local input, forwarding and local output. See the man page for
  387. ebtables(8).
  388. To compile it as a module, choose M here. If unsure, say N.
  389. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_T_NAT
  390. tristate "ebt: nat table support"
  391. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  392. help
  393. The ebtables nat table is used to define rules that alter the MAC
  394. source address (MAC SNAT) or the MAC destination address (MAC DNAT).
  395. See the man page for ebtables(8).
  396. To compile it as a module, choose M here. If unsure, say N.
  397. #
  398. # matches
  399. #
  400. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_802_3
  401. tristate "ebt: 802.3 filter support"
  402. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  403. help
  404. This option adds matching support for 802.3 Ethernet frames.
  405. To compile it as a module, choose M here. If unsure, say N.
  406. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_AMONG
  407. tristate "ebt: among filter support"
  408. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  409. help
  410. This option adds the among match, which allows matching the MAC source
  411. and/or destination address on a list of addresses. Optionally,
  412. MAC/IP address pairs can be matched, f.e. for anti-spoofing rules.
  413. To compile it as a module, choose M here. If unsure, say N.
  414. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_ARP
  415. tristate "ebt: ARP filter support"
  416. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  417. help
  418. This option adds the ARP match, which allows ARP and RARP header field
  419. filtering.
  420. To compile it as a module, choose M here. If unsure, say N.
  421. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_IP
  422. tristate "ebt: IP filter support"
  423. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  424. help
  425. This option adds the IP match, which allows basic IP header field
  426. filtering.
  427. To compile it as a module, choose M here. If unsure, say N.
  428. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_IP6
  429. tristate "ebt: IP6 filter support"
  430. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES && ADK_KPACKAGE_KMOD_IPV6
  431. help
  432. This option adds the IP6 match, which allows basic IPV6 header field
  433. filtering.
  434. To compile it as a module, choose M here. If unsure, say N.
  435. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_LIMIT
  436. tristate "ebt: limit match support"
  437. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  438. help
  439. This option adds the limit match, which allows you to control
  440. the rate at which a rule can be matched. This match is the
  441. equivalent of the iptables limit match.
  442. If you want to compile it as a module, say M here and read
  443. <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
  444. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_MARK
  445. tristate "ebt: mark filter support"
  446. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  447. help
  448. This option adds the mark match, which allows matching frames based on
  449. the 'nfmark' value in the frame. This can be set by the mark target.
  450. This value is the same as the one used in the iptables mark match and
  451. target.
  452. To compile it as a module, choose M here. If unsure, say N.
  453. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_PKTTYPE
  454. tristate "ebt: packet type filter support"
  455. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  456. help
  457. This option adds the packet type match, which allows matching on the
  458. type of packet based on its Ethernet "class" (as determined by
  459. the generic networking code): broadcast, multicast,
  460. for this host alone or for another host.
  461. To compile it as a module, choose M here. If unsure, say N.
  462. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_STP
  463. tristate "ebt: STP filter support"
  464. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  465. help
  466. This option adds the Spanning Tree Protocol match, which
  467. allows STP header field filtering.
  468. To compile it as a module, choose M here. If unsure, say N.
  469. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_VLAN
  470. tristate "ebt: 802.1Q VLAN filter support"
  471. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  472. help
  473. This option adds the 802.1Q vlan match, which allows the filtering of
  474. 802.1Q vlan fields.
  475. To compile it as a module, choose M here. If unsure, say N.
  476. #
  477. # targets
  478. #
  479. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_ARPREPLY
  480. tristate "ebt: arp reply target support"
  481. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  482. help
  483. This option adds the arp reply target, which allows
  484. automatically sending arp replies to arp requests.
  485. To compile it as a module, choose M here. If unsure, say N.
  486. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_DNAT
  487. tristate "ebt: dnat target support"
  488. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  489. help
  490. This option adds the MAC DNAT target, which allows altering the MAC
  491. destination address of frames.
  492. To compile it as a module, choose M here. If unsure, say N.
  493. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_MARK_T
  494. tristate "ebt: mark target support"
  495. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  496. help
  497. This option adds the mark target, which allows marking frames by
  498. setting the 'nfmark' value in the frame.
  499. This value is the same as the one used in the iptables mark match and
  500. target.
  501. To compile it as a module, choose M here. If unsure, say N.
  502. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_REDIRECT
  503. tristate "ebt: redirect target support"
  504. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  505. help
  506. This option adds the MAC redirect target, which allows altering the MAC
  507. destination address of a frame to that of the device it arrived on.
  508. To compile it as a module, choose M here. If unsure, say N.
  509. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_SNAT
  510. tristate "ebt: snat target support"
  511. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  512. help
  513. This option adds the MAC SNAT target, which allows altering the MAC
  514. source address of frames.
  515. To compile it as a module, choose M here. If unsure, say N.
  516. #
  517. # watchers
  518. #
  519. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_LOG
  520. tristate "ebt: log support"
  521. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  522. help
  523. This option adds the log watcher, that you can use in any rule
  524. in any ebtables table. It records info about the frame header
  525. to the syslog.
  526. To compile it as a module, choose M here. If unsure, say N.
  527. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_ULOG
  528. tristate "ebt: ulog support (OBSOLETE)"
  529. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  530. help
  531. This option enables the old bridge-specific "ebt_ulog" implementation
  532. which has been obsoleted by the new "nfnetlink_log" code (see
  533. CONFIG_NETFILTER_NETLINK_LOG).
  534. This option adds the ulog watcher, that you can use in any rule
  535. in any ebtables table. The packet is passed to a userspace
  536. logging daemon using netlink multicast sockets. This differs
  537. from the log watcher in the sense that the complete packet is
  538. sent to userspace instead of a descriptive text and that
  539. netlink multicast sockets are used instead of the syslog.
  540. To compile it as a module, choose M here. If unsure, say N.
  541. config ADK_KPACKAGE_KMOD_BRIDGE_EBT_NFLOG
  542. tristate "ebt: nflog support"
  543. depends on ADK_KPACKAGE_KMOD_BRIDGE_NF_EBTABLES
  544. help
  545. This option enables the nflog watcher, which allows to LOG
  546. messages through the netfilter logging API, which can use
  547. either the old LOG target, the old ULOG target or nfnetlink_log
  548. as backend.
  549. This option adds the nflog watcher, that you can use in any rule
  550. in any ebtables table.
  551. To compile it as a module, choose M here. If unsure, say N.
  552. endmenu
  553. endmenu