Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # Traffic control configuration. | |
3 | # | |
6a2e9b73 | 4 | |
85ef3e5c | 5 | menuconfig NET_SCHED |
6a2e9b73 | 6 | bool "QoS and/or fair queueing" |
3c62f75a | 7 | select NET_SCH_FIFO |
6a2e9b73 SR |
8 | ---help--- |
9 | When the kernel has several packets to send out over a network | |
10 | device, it has to decide which ones to send first, which ones to | |
52ab4ac2 TG |
11 | delay, and which ones to drop. This is the job of the queueing |
12 | disciplines, several different algorithms for how to do this | |
6a2e9b73 SR |
13 | "fairly" have been proposed. |
14 | ||
15 | If you say N here, you will get the standard packet scheduler, which | |
16 | is a FIFO (first come, first served). If you say Y here, you will be | |
17 | able to choose from among several alternative algorithms which can | |
18 | then be attached to different network devices. This is useful for | |
19 | example if some of your network devices are real time devices that | |
20 | need a certain minimum data flow rate, or if you need to limit the | |
21 | maximum data flow rate for traffic which matches specified criteria. | |
22 | This code is considered to be experimental. | |
23 | ||
24 | To administer these schedulers, you'll need the user-level utilities | |
5d330cdd AS |
25 | from the package iproute2+tc at |
26 | <https://www.kernel.org/pub/linux/utils/net/iproute2/>. That package | |
27 | also contains some documentation; for more, check out | |
c996d8b9 | 28 | <http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2>. |
6a2e9b73 SR |
29 | |
30 | This Quality of Service (QoS) support will enable you to use | |
31 | Differentiated Services (diffserv) and Resource Reservation Protocol | |
52ab4ac2 TG |
32 | (RSVP) on your Linux router if you also say Y to the corresponding |
33 | classifiers below. Documentation and software is at | |
34 | <http://diffserv.sourceforge.net/>. | |
6a2e9b73 SR |
35 | |
36 | If you say Y here and to "/proc file system" below, you will be able | |
37 | to read status information about packet schedulers from the file | |
38 | /proc/net/psched. | |
39 | ||
40 | The available schedulers are listed in the following questions; you | |
41 | can say Y to as many as you like. If unsure, say N now. | |
42 | ||
05b8b0fa RZ |
43 | if NET_SCHED |
44 | ||
52ab4ac2 | 45 | comment "Queueing/Scheduling" |
52ab4ac2 | 46 | |
1da177e4 | 47 | config NET_SCH_CBQ |
52ab4ac2 | 48 | tristate "Class Based Queueing (CBQ)" |
1da177e4 LT |
49 | ---help--- |
50 | Say Y here if you want to use the Class-Based Queueing (CBQ) packet | |
52ab4ac2 TG |
51 | scheduling algorithm. This algorithm classifies the waiting packets |
52 | into a tree-like hierarchy of classes; the leaves of this tree are | |
53 | in turn scheduled by separate algorithms. | |
1da177e4 | 54 | |
52ab4ac2 | 55 | See the top of <file:net/sched/sch_cbq.c> for more details. |
1da177e4 LT |
56 | |
57 | CBQ is a commonly used scheduler, so if you're unsure, you should | |
58 | say Y here. Then say Y to all the queueing algorithms below that you | |
52ab4ac2 | 59 | want to use as leaf disciplines. |
1da177e4 LT |
60 | |
61 | To compile this code as a module, choose M here: the | |
62 | module will be called sch_cbq. | |
63 | ||
64 | config NET_SCH_HTB | |
52ab4ac2 | 65 | tristate "Hierarchical Token Bucket (HTB)" |
1da177e4 LT |
66 | ---help--- |
67 | Say Y here if you want to use the Hierarchical Token Buckets (HTB) | |
52ab4ac2 | 68 | packet scheduling algorithm. See |
1da177e4 LT |
69 | <http://luxik.cdi.cz/~devik/qos/htb/> for complete manual and |
70 | in-depth articles. | |
71 | ||
52ab4ac2 | 72 | HTB is very similar to CBQ regarding its goals however is has |
1da177e4 LT |
73 | different properties and different algorithm. |
74 | ||
75 | To compile this code as a module, choose M here: the | |
76 | module will be called sch_htb. | |
77 | ||
78 | config NET_SCH_HFSC | |
52ab4ac2 | 79 | tristate "Hierarchical Fair Service Curve (HFSC)" |
1da177e4 LT |
80 | ---help--- |
81 | Say Y here if you want to use the Hierarchical Fair Service Curve | |
52ab4ac2 | 82 | (HFSC) packet scheduling algorithm. |
1da177e4 LT |
83 | |
84 | To compile this code as a module, choose M here: the | |
85 | module will be called sch_hfsc. | |
86 | ||
1da177e4 | 87 | config NET_SCH_ATM |
52ab4ac2 | 88 | tristate "ATM Virtual Circuits (ATM)" |
05b8b0fa | 89 | depends on ATM |
1da177e4 LT |
90 | ---help--- |
91 | Say Y here if you want to use the ATM pseudo-scheduler. This | |
52ab4ac2 TG |
92 | provides a framework for invoking classifiers, which in turn |
93 | select classes of this queuing discipline. Each class maps | |
94 | the flow(s) it is handling to a given virtual circuit. | |
95 | ||
99acaeb9 | 96 | See the top of <file:net/sched/sch_atm.c> for more details. |
1da177e4 LT |
97 | |
98 | To compile this code as a module, choose M here: the | |
99 | module will be called sch_atm. | |
100 | ||
101 | config NET_SCH_PRIO | |
52ab4ac2 | 102 | tristate "Multi Band Priority Queueing (PRIO)" |
52ab4ac2 | 103 | ---help--- |
1da177e4 | 104 | Say Y here if you want to use an n-band priority queue packet |
52ab4ac2 | 105 | scheduler. |
1da177e4 LT |
106 | |
107 | To compile this code as a module, choose M here: the | |
108 | module will be called sch_prio. | |
109 | ||
92651940 AD |
110 | config NET_SCH_MULTIQ |
111 | tristate "Hardware Multiqueue-aware Multi Band Queuing (MULTIQ)" | |
112 | ---help--- | |
113 | Say Y here if you want to use an n-band queue packet scheduler | |
114 | to support devices that have multiple hardware transmit queues. | |
115 | ||
116 | To compile this code as a module, choose M here: the | |
117 | module will be called sch_multiq. | |
118 | ||
1da177e4 | 119 | config NET_SCH_RED |
52ab4ac2 | 120 | tristate "Random Early Detection (RED)" |
52ab4ac2 | 121 | ---help--- |
1da177e4 | 122 | Say Y here if you want to use the Random Early Detection (RED) |
52ab4ac2 TG |
123 | packet scheduling algorithm. |
124 | ||
125 | See the top of <file:net/sched/sch_red.c> for more details. | |
1da177e4 LT |
126 | |
127 | To compile this code as a module, choose M here: the | |
128 | module will be called sch_red. | |
129 | ||
e13e02a3 ED |
130 | config NET_SCH_SFB |
131 | tristate "Stochastic Fair Blue (SFB)" | |
132 | ---help--- | |
133 | Say Y here if you want to use the Stochastic Fair Blue (SFB) | |
134 | packet scheduling algorithm. | |
135 | ||
136 | See the top of <file:net/sched/sch_sfb.c> for more details. | |
137 | ||
138 | To compile this code as a module, choose M here: the | |
139 | module will be called sch_sfb. | |
140 | ||
1da177e4 | 141 | config NET_SCH_SFQ |
52ab4ac2 | 142 | tristate "Stochastic Fairness Queueing (SFQ)" |
1da177e4 LT |
143 | ---help--- |
144 | Say Y here if you want to use the Stochastic Fairness Queueing (SFQ) | |
99acaeb9 | 145 | packet scheduling algorithm. |
52ab4ac2 TG |
146 | |
147 | See the top of <file:net/sched/sch_sfq.c> for more details. | |
1da177e4 LT |
148 | |
149 | To compile this code as a module, choose M here: the | |
150 | module will be called sch_sfq. | |
151 | ||
152 | config NET_SCH_TEQL | |
52ab4ac2 | 153 | tristate "True Link Equalizer (TEQL)" |
1da177e4 LT |
154 | ---help--- |
155 | Say Y here if you want to use the True Link Equalizer (TLE) packet | |
52ab4ac2 TG |
156 | scheduling algorithm. This queueing discipline allows the combination |
157 | of several physical devices into one virtual device. | |
158 | ||
159 | See the top of <file:net/sched/sch_teql.c> for more details. | |
1da177e4 LT |
160 | |
161 | To compile this code as a module, choose M here: the | |
162 | module will be called sch_teql. | |
163 | ||
164 | config NET_SCH_TBF | |
52ab4ac2 | 165 | tristate "Token Bucket Filter (TBF)" |
52ab4ac2 TG |
166 | ---help--- |
167 | Say Y here if you want to use the Token Bucket Filter (TBF) packet | |
168 | scheduling algorithm. | |
169 | ||
170 | See the top of <file:net/sched/sch_tbf.c> for more details. | |
1da177e4 LT |
171 | |
172 | To compile this code as a module, choose M here: the | |
173 | module will be called sch_tbf. | |
174 | ||
175 | config NET_SCH_GRED | |
52ab4ac2 | 176 | tristate "Generic Random Early Detection (GRED)" |
52ab4ac2 | 177 | ---help--- |
1da177e4 | 178 | Say Y here if you want to use the Generic Random Early Detection |
20cc6bef | 179 | (GRED) packet scheduling algorithm for some of your network devices |
1da177e4 LT |
180 | (see the top of <file:net/sched/sch_red.c> for details and |
181 | references about the algorithm). | |
182 | ||
183 | To compile this code as a module, choose M here: the | |
184 | module will be called sch_gred. | |
185 | ||
186 | config NET_SCH_DSMARK | |
52ab4ac2 | 187 | tristate "Differentiated Services marker (DSMARK)" |
52ab4ac2 | 188 | ---help--- |
1da177e4 LT |
189 | Say Y if you want to schedule packets according to the |
190 | Differentiated Services architecture proposed in RFC 2475. | |
191 | Technical information on this method, with pointers to associated | |
192 | RFCs, is available at <http://www.gta.ufrj.br/diffserv/>. | |
193 | ||
194 | To compile this code as a module, choose M here: the | |
195 | module will be called sch_dsmark. | |
196 | ||
197 | config NET_SCH_NETEM | |
52ab4ac2 | 198 | tristate "Network emulator (NETEM)" |
52ab4ac2 | 199 | ---help--- |
1da177e4 LT |
200 | Say Y if you want to emulate network delay, loss, and packet |
201 | re-ordering. This is often useful to simulate networks when | |
202 | testing applications or protocols. | |
203 | ||
204 | To compile this driver as a module, choose M here: the module | |
205 | will be called sch_netem. | |
206 | ||
207 | If unsure, say N. | |
208 | ||
13d2a1d2 PM |
209 | config NET_SCH_DRR |
210 | tristate "Deficit Round Robin scheduler (DRR)" | |
211 | help | |
212 | Say Y here if you want to use the Deficit Round Robin (DRR) packet | |
213 | scheduling algorithm. | |
214 | ||
215 | To compile this driver as a module, choose M here: the module | |
216 | will be called sch_drr. | |
217 | ||
218 | If unsure, say N. | |
219 | ||
b8970f0b JF |
220 | config NET_SCH_MQPRIO |
221 | tristate "Multi-queue priority scheduler (MQPRIO)" | |
222 | help | |
223 | Say Y here if you want to use the Multi-queue Priority scheduler. | |
224 | This scheduler allows QOS to be offloaded on NICs that have support | |
225 | for offloading QOS schedulers. | |
226 | ||
227 | To compile this driver as a module, choose M here: the module will | |
228 | be called sch_mqprio. | |
229 | ||
230 | If unsure, say N. | |
231 | ||
45e14433 | 232 | config NET_SCH_CHOKE |
233 | tristate "CHOose and Keep responsive flow scheduler (CHOKE)" | |
234 | help | |
235 | Say Y here if you want to use the CHOKe packet scheduler (CHOose | |
236 | and Keep for responsive flows, CHOose and Kill for unresponsive | |
237 | flows). This is a variation of RED which trys to penalize flows | |
238 | that monopolize the queue. | |
239 | ||
240 | To compile this code as a module, choose M here: the | |
241 | module will be called sch_choke. | |
242 | ||
0545a303 | 243 | config NET_SCH_QFQ |
244 | tristate "Quick Fair Queueing scheduler (QFQ)" | |
245 | help | |
246 | Say Y here if you want to use the Quick Fair Queueing Scheduler (QFQ) | |
247 | packet scheduling algorithm. | |
248 | ||
249 | To compile this driver as a module, choose M here: the module | |
250 | will be called sch_qfq. | |
251 | ||
252 | If unsure, say N. | |
253 | ||
76e3cc12 ED |
254 | config NET_SCH_CODEL |
255 | tristate "Controlled Delay AQM (CODEL)" | |
256 | help | |
257 | Say Y here if you want to use the Controlled Delay (CODEL) | |
258 | packet scheduling algorithm. | |
259 | ||
260 | To compile this driver as a module, choose M here: the module | |
261 | will be called sch_codel. | |
262 | ||
263 | If unsure, say N. | |
264 | ||
4b549a2e ED |
265 | config NET_SCH_FQ_CODEL |
266 | tristate "Fair Queue Controlled Delay AQM (FQ_CODEL)" | |
267 | help | |
268 | Say Y here if you want to use the FQ Controlled Delay (FQ_CODEL) | |
269 | packet scheduling algorithm. | |
270 | ||
271 | To compile this driver as a module, choose M here: the module | |
272 | will be called sch_fq_codel. | |
273 | ||
274 | If unsure, say N. | |
275 | ||
afe4fd06 ED |
276 | config NET_SCH_FQ |
277 | tristate "Fair Queue" | |
278 | help | |
279 | Say Y here if you want to use the FQ packet scheduling algorithm. | |
280 | ||
281 | FQ does flow separation, and is able to respect pacing requirements | |
282 | set by TCP stack into sk->sk_pacing_rate (for localy generated | |
283 | traffic) | |
284 | ||
285 | To compile this driver as a module, choose M here: the module | |
286 | will be called sch_fq. | |
287 | ||
288 | If unsure, say N. | |
289 | ||
10239edf TL |
290 | config NET_SCH_HHF |
291 | tristate "Heavy-Hitter Filter (HHF)" | |
292 | help | |
293 | Say Y here if you want to use the Heavy-Hitter Filter (HHF) | |
294 | packet scheduling algorithm. | |
295 | ||
296 | To compile this driver as a module, choose M here: the module | |
297 | will be called sch_hhf. | |
298 | ||
d4b36210 VS |
299 | config NET_SCH_PIE |
300 | tristate "Proportional Integral controller Enhanced (PIE) scheduler" | |
301 | help | |
302 | Say Y here if you want to use the Proportional Integral controller | |
303 | Enhanced scheduler packet scheduling algorithm. | |
304 | For more information, please see | |
305 | http://tools.ietf.org/html/draft-pan-tsvwg-pie-00 | |
306 | ||
307 | To compile this driver as a module, choose M here: the module | |
308 | will be called sch_pie. | |
309 | ||
310 | If unsure, say N. | |
311 | ||
1da177e4 LT |
312 | config NET_SCH_INGRESS |
313 | tristate "Ingress Qdisc" | |
72eb7bd2 | 314 | depends on NET_CLS_ACT |
1cf51900 | 315 | select NET_INGRESS |
52ab4ac2 TG |
316 | ---help--- |
317 | Say Y here if you want to use classifiers for incoming packets. | |
1da177e4 LT |
318 | If unsure, say Y. |
319 | ||
320 | To compile this code as a module, choose M here: the | |
321 | module will be called sch_ingress. | |
322 | ||
c3059be1 SR |
323 | config NET_SCH_PLUG |
324 | tristate "Plug network traffic until release (PLUG)" | |
325 | ---help--- | |
326 | ||
327 | This queuing discipline allows userspace to plug/unplug a network | |
328 | output queue, using the netlink interface. When it receives an | |
329 | enqueue command it inserts a plug into the outbound queue that | |
330 | causes following packets to enqueue until a dequeue command arrives | |
331 | over netlink, causing the plug to be removed and resuming the normal | |
332 | packet flow. | |
333 | ||
334 | This module also provides a generic "network output buffering" | |
335 | functionality (aka output commit), wherein upon arrival of a dequeue | |
336 | command, only packets up to the first plug are released for delivery. | |
337 | The Remus HA project uses this module to enable speculative execution | |
338 | of virtual machines by allowing the generated network output to be rolled | |
339 | back if needed. | |
340 | ||
5d330cdd | 341 | For more information, please refer to <http://wiki.xenproject.org/wiki/Remus> |
c3059be1 SR |
342 | |
343 | Say Y here if you are using this kernel for Xen dom0 and | |
344 | want to protect Xen guests with Remus. | |
345 | ||
346 | To compile this code as a module, choose M here: the | |
347 | module will be called sch_plug. | |
348 | ||
52ab4ac2 | 349 | comment "Classification" |
1da177e4 LT |
350 | |
351 | config NET_CLS | |
6341e62b | 352 | bool |
1da177e4 LT |
353 | |
354 | config NET_CLS_BASIC | |
52ab4ac2 | 355 | tristate "Elementary classification (BASIC)" |
52ab4ac2 | 356 | select NET_CLS |
1da177e4 LT |
357 | ---help--- |
358 | Say Y here if you want to be able to classify packets using | |
359 | only extended matches and actions. | |
360 | ||
361 | To compile this code as a module, choose M here: the | |
362 | module will be called cls_basic. | |
363 | ||
364 | config NET_CLS_TCINDEX | |
52ab4ac2 | 365 | tristate "Traffic-Control Index (TCINDEX)" |
52ab4ac2 TG |
366 | select NET_CLS |
367 | ---help--- | |
368 | Say Y here if you want to be able to classify packets based on | |
369 | traffic control indices. You will want this feature if you want | |
370 | to implement Differentiated Services together with DSMARK. | |
1da177e4 LT |
371 | |
372 | To compile this code as a module, choose M here: the | |
373 | module will be called cls_tcindex. | |
374 | ||
375 | config NET_CLS_ROUTE4 | |
52ab4ac2 | 376 | tristate "Routing decision (ROUTE)" |
034cfe48 | 377 | depends on INET |
c7066f70 | 378 | select IP_ROUTE_CLASSID |
52ab4ac2 TG |
379 | select NET_CLS |
380 | ---help--- | |
381 | If you say Y here, you will be able to classify packets | |
382 | according to the route table entry they matched. | |
1da177e4 LT |
383 | |
384 | To compile this code as a module, choose M here: the | |
385 | module will be called cls_route. | |
386 | ||
1da177e4 | 387 | config NET_CLS_FW |
52ab4ac2 | 388 | tristate "Netfilter mark (FW)" |
52ab4ac2 TG |
389 | select NET_CLS |
390 | ---help--- | |
391 | If you say Y here, you will be able to classify packets | |
392 | according to netfilter/firewall marks. | |
1da177e4 LT |
393 | |
394 | To compile this code as a module, choose M here: the | |
395 | module will be called cls_fw. | |
396 | ||
397 | config NET_CLS_U32 | |
52ab4ac2 | 398 | tristate "Universal 32bit comparisons w/ hashing (U32)" |
52ab4ac2 TG |
399 | select NET_CLS |
400 | ---help--- | |
3539c272 | 401 | Say Y here to be able to classify packets using a universal |
52ab4ac2 | 402 | 32bit pieces based comparison scheme. |
1da177e4 LT |
403 | |
404 | To compile this code as a module, choose M here: the | |
405 | module will be called cls_u32. | |
406 | ||
407 | config CLS_U32_PERF | |
52ab4ac2 | 408 | bool "Performance counters support" |
1da177e4 | 409 | depends on NET_CLS_U32 |
52ab4ac2 TG |
410 | ---help--- |
411 | Say Y here to make u32 gather additional statistics useful for | |
412 | fine tuning u32 classifiers. | |
1da177e4 LT |
413 | |
414 | config CLS_U32_MARK | |
52ab4ac2 | 415 | bool "Netfilter marks support" |
82e91ffe | 416 | depends on NET_CLS_U32 |
52ab4ac2 TG |
417 | ---help--- |
418 | Say Y here to be able to use netfilter marks as u32 key. | |
1da177e4 LT |
419 | |
420 | config NET_CLS_RSVP | |
52ab4ac2 | 421 | tristate "IPv4 Resource Reservation Protocol (RSVP)" |
52ab4ac2 | 422 | select NET_CLS |
1da177e4 LT |
423 | ---help--- |
424 | The Resource Reservation Protocol (RSVP) permits end systems to | |
425 | request a minimum and maximum data flow rate for a connection; this | |
426 | is important for real time data such as streaming sound or video. | |
427 | ||
428 | Say Y here if you want to be able to classify outgoing packets based | |
429 | on their RSVP requests. | |
430 | ||
431 | To compile this code as a module, choose M here: the | |
432 | module will be called cls_rsvp. | |
433 | ||
434 | config NET_CLS_RSVP6 | |
52ab4ac2 | 435 | tristate "IPv6 Resource Reservation Protocol (RSVP6)" |
52ab4ac2 | 436 | select NET_CLS |
1da177e4 LT |
437 | ---help--- |
438 | The Resource Reservation Protocol (RSVP) permits end systems to | |
439 | request a minimum and maximum data flow rate for a connection; this | |
440 | is important for real time data such as streaming sound or video. | |
441 | ||
442 | Say Y here if you want to be able to classify outgoing packets based | |
99acaeb9 | 443 | on their RSVP requests and you are using the IPv6 protocol. |
1da177e4 LT |
444 | |
445 | To compile this code as a module, choose M here: the | |
446 | module will be called cls_rsvp6. | |
447 | ||
e5dfb815 PM |
448 | config NET_CLS_FLOW |
449 | tristate "Flow classifier" | |
450 | select NET_CLS | |
451 | ---help--- | |
452 | If you say Y here, you will be able to classify packets based on | |
453 | a configurable combination of packet keys. This is mostly useful | |
454 | in combination with SFQ. | |
455 | ||
456 | To compile this code as a module, choose M here: the | |
457 | module will be called cls_flow. | |
458 | ||
f4009237 | 459 | config NET_CLS_CGROUP |
8e039d84 | 460 | tristate "Control Group Classifier" |
f4009237 | 461 | select NET_CLS |
fe1217c4 | 462 | select CGROUP_NET_CLASSID |
f4009237 TG |
463 | depends on CGROUPS |
464 | ---help--- | |
465 | Say Y here if you want to classify packets based on the control | |
466 | cgroup of their process. | |
467 | ||
8e039d84 BB |
468 | To compile this code as a module, choose M here: the |
469 | module will be called cls_cgroup. | |
470 | ||
7d1d65cb DB |
471 | config NET_CLS_BPF |
472 | tristate "BPF-based classifier" | |
473 | select NET_CLS | |
474 | ---help--- | |
475 | If you say Y here, you will be able to classify packets based on | |
476 | programmable BPF (JIT'ed) filters as an alternative to ematches. | |
477 | ||
478 | To compile this code as a module, choose M here: the module will | |
479 | be called cls_bpf. | |
480 | ||
77b9900e JP |
481 | config NET_CLS_FLOWER |
482 | tristate "Flower classifier" | |
483 | select NET_CLS | |
484 | ---help--- | |
485 | If you say Y here, you will be able to classify packets based on | |
486 | a configurable combination of packet keys and masks. | |
487 | ||
488 | To compile this code as a module, choose M here: the module will | |
489 | be called cls_flower. | |
490 | ||
1da177e4 LT |
491 | config NET_EMATCH |
492 | bool "Extended Matches" | |
52ab4ac2 | 493 | select NET_CLS |
1da177e4 LT |
494 | ---help--- |
495 | Say Y here if you want to use extended matches on top of classifiers | |
496 | and select the extended matches below. | |
497 | ||
498 | Extended matches are small classification helpers not worth writing | |
52ab4ac2 | 499 | a separate classifier for. |
1da177e4 | 500 | |
52ab4ac2 | 501 | A recent version of the iproute2 package is required to use |
1da177e4 LT |
502 | extended matches. |
503 | ||
504 | config NET_EMATCH_STACK | |
505 | int "Stack size" | |
506 | depends on NET_EMATCH | |
507 | default "32" | |
508 | ---help--- | |
509 | Size of the local stack variable used while evaluating the tree of | |
510 | ematches. Limits the depth of the tree, i.e. the number of | |
b824979a | 511 | encapsulated precedences. Every level requires 4 bytes of additional |
1da177e4 LT |
512 | stack space. |
513 | ||
514 | config NET_EMATCH_CMP | |
515 | tristate "Simple packet data comparison" | |
516 | depends on NET_EMATCH | |
517 | ---help--- | |
518 | Say Y here if you want to be able to classify packets based on | |
519 | simple packet data comparisons for 8, 16, and 32bit values. | |
520 | ||
521 | To compile this code as a module, choose M here: the | |
522 | module will be called em_cmp. | |
523 | ||
524 | config NET_EMATCH_NBYTE | |
525 | tristate "Multi byte comparison" | |
526 | depends on NET_EMATCH | |
527 | ---help--- | |
528 | Say Y here if you want to be able to classify packets based on | |
529 | multiple byte comparisons mainly useful for IPv6 address comparisons. | |
530 | ||
531 | To compile this code as a module, choose M here: the | |
532 | module will be called em_nbyte. | |
533 | ||
534 | config NET_EMATCH_U32 | |
52ab4ac2 | 535 | tristate "U32 key" |
1da177e4 LT |
536 | depends on NET_EMATCH |
537 | ---help--- | |
538 | Say Y here if you want to be able to classify packets using | |
539 | the famous u32 key in combination with logic relations. | |
540 | ||
541 | To compile this code as a module, choose M here: the | |
542 | module will be called em_u32. | |
543 | ||
544 | config NET_EMATCH_META | |
545 | tristate "Metadata" | |
546 | depends on NET_EMATCH | |
547 | ---help--- | |
bb7e8c5a | 548 | Say Y here if you want to be able to classify packets based on |
1da177e4 LT |
549 | metadata such as load average, netfilter attributes, socket |
550 | attributes and routing decisions. | |
551 | ||
552 | To compile this code as a module, choose M here: the | |
553 | module will be called em_meta. | |
554 | ||
d675c989 TG |
555 | config NET_EMATCH_TEXT |
556 | tristate "Textsearch" | |
557 | depends on NET_EMATCH | |
f2d368fa | 558 | select TEXTSEARCH |
f7704347 | 559 | select TEXTSEARCH_KMP |
29cb9f9c | 560 | select TEXTSEARCH_BM |
f7704347 | 561 | select TEXTSEARCH_FSM |
d675c989 | 562 | ---help--- |
52ab4ac2 | 563 | Say Y here if you want to be able to classify packets based on |
f7704347 | 564 | textsearch comparisons. |
d675c989 TG |
565 | |
566 | To compile this code as a module, choose M here: the | |
567 | module will be called em_text. | |
568 | ||
f057bbb6 RL |
569 | config NET_EMATCH_CANID |
570 | tristate "CAN Identifier" | |
a303fbf3 | 571 | depends on NET_EMATCH && (CAN=y || CAN=m) |
f057bbb6 RL |
572 | ---help--- |
573 | Say Y here if you want to be able to classify CAN frames based | |
574 | on CAN Identifier. | |
575 | ||
576 | To compile this code as a module, choose M here: the | |
577 | module will be called em_canid. | |
578 | ||
6d4fa852 FW |
579 | config NET_EMATCH_IPSET |
580 | tristate "IPset" | |
581 | depends on NET_EMATCH && IP_SET | |
582 | ---help--- | |
583 | Say Y here if you want to be able to classify packets based on | |
584 | ipset membership. | |
585 | ||
586 | To compile this code as a module, choose M here: the | |
587 | module will be called em_ipset. | |
588 | ||
1da177e4 | 589 | config NET_CLS_ACT |
52ab4ac2 | 590 | bool "Actions" |
1da177e4 | 591 | ---help--- |
52ab4ac2 TG |
592 | Say Y here if you want to use traffic control actions. Actions |
593 | get attached to classifiers and are invoked after a successful | |
594 | classification. They are used to overwrite the classification | |
595 | result, instantly drop or redirect packets, etc. | |
596 | ||
597 | A recent version of the iproute2 package is required to use | |
598 | extended matches. | |
1da177e4 LT |
599 | |
600 | config NET_ACT_POLICE | |
52ab4ac2 | 601 | tristate "Traffic Policing" |
1da177e4 LT |
602 | depends on NET_CLS_ACT |
603 | ---help--- | |
52ab4ac2 TG |
604 | Say Y here if you want to do traffic policing, i.e. strict |
605 | bandwidth limiting. This action replaces the existing policing | |
606 | module. | |
607 | ||
608 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 609 | module will be called act_police. |
1da177e4 LT |
610 | |
611 | config NET_ACT_GACT | |
52ab4ac2 | 612 | tristate "Generic actions" |
1da177e4 LT |
613 | depends on NET_CLS_ACT |
614 | ---help--- | |
52ab4ac2 TG |
615 | Say Y here to take generic actions such as dropping and |
616 | accepting packets. | |
617 | ||
618 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 619 | module will be called act_gact. |
1da177e4 LT |
620 | |
621 | config GACT_PROB | |
52ab4ac2 | 622 | bool "Probability support" |
1da177e4 LT |
623 | depends on NET_ACT_GACT |
624 | ---help--- | |
52ab4ac2 | 625 | Say Y here to use the generic action randomly or deterministically. |
1da177e4 LT |
626 | |
627 | config NET_ACT_MIRRED | |
52ab4ac2 | 628 | tristate "Redirecting and Mirroring" |
1da177e4 LT |
629 | depends on NET_CLS_ACT |
630 | ---help--- | |
52ab4ac2 TG |
631 | Say Y here to allow packets to be mirrored or redirected to |
632 | other devices. | |
633 | ||
634 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 635 | module will be called act_mirred. |
1da177e4 LT |
636 | |
637 | config NET_ACT_IPT | |
52ab4ac2 | 638 | tristate "IPtables targets" |
1da177e4 LT |
639 | depends on NET_CLS_ACT && NETFILTER && IP_NF_IPTABLES |
640 | ---help--- | |
3539c272 | 641 | Say Y here to be able to invoke iptables targets after successful |
52ab4ac2 TG |
642 | classification. |
643 | ||
644 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 645 | module will be called act_ipt. |
1da177e4 | 646 | |
b4219952 HX |
647 | config NET_ACT_NAT |
648 | tristate "Stateless NAT" | |
649 | depends on NET_CLS_ACT | |
b4219952 HX |
650 | ---help--- |
651 | Say Y here to do stateless NAT on IPv4 packets. You should use | |
652 | netfilter for NAT unless you know what you are doing. | |
653 | ||
654 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 655 | module will be called act_nat. |
b4219952 | 656 | |
1da177e4 | 657 | config NET_ACT_PEDIT |
52ab4ac2 | 658 | tristate "Packet Editing" |
1da177e4 LT |
659 | depends on NET_CLS_ACT |
660 | ---help--- | |
52ab4ac2 | 661 | Say Y here if you want to mangle the content of packets. |
1da177e4 | 662 | |
52ab4ac2 | 663 | To compile this code as a module, choose M here: the |
d4ae20b3 | 664 | module will be called act_pedit. |
1da177e4 | 665 | |
db753079 | 666 | config NET_ACT_SIMP |
52ab4ac2 | 667 | tristate "Simple Example (Debug)" |
db753079 JHS |
668 | depends on NET_CLS_ACT |
669 | ---help--- | |
52ab4ac2 TG |
670 | Say Y here to add a simple action for demonstration purposes. |
671 | It is meant as an example and for debugging purposes. It will | |
672 | print a configured policy string followed by the packet count | |
673 | to the console for every packet that passes by. | |
674 | ||
675 | If unsure, say N. | |
676 | ||
677 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 678 | module will be called act_simple. |
52ab4ac2 | 679 | |
ca9b0e27 AD |
680 | config NET_ACT_SKBEDIT |
681 | tristate "SKB Editing" | |
682 | depends on NET_CLS_ACT | |
683 | ---help--- | |
684 | Say Y here to change skb priority or queue_mapping settings. | |
685 | ||
686 | If unsure, say N. | |
687 | ||
688 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 689 | module will be called act_skbedit. |
ca9b0e27 | 690 | |
eb4d4065 GB |
691 | config NET_ACT_CSUM |
692 | tristate "Checksum Updating" | |
7abac686 | 693 | depends on NET_CLS_ACT && INET |
eb4d4065 GB |
694 | ---help--- |
695 | Say Y here to update some common checksum after some direct | |
696 | packet alterations. | |
697 | ||
698 | To compile this code as a module, choose M here: the | |
699 | module will be called act_csum. | |
700 | ||
c7e2b968 JP |
701 | config NET_ACT_VLAN |
702 | tristate "Vlan manipulation" | |
703 | depends on NET_CLS_ACT | |
704 | ---help--- | |
705 | Say Y here to push or pop vlan headers. | |
706 | ||
707 | If unsure, say N. | |
708 | ||
709 | To compile this code as a module, choose M here: the | |
710 | module will be called act_vlan. | |
711 | ||
d23b8ad8 JP |
712 | config NET_ACT_BPF |
713 | tristate "BPF based action" | |
714 | depends on NET_CLS_ACT | |
715 | ---help--- | |
716 | Say Y here to execute BPF code on packets. The BPF code will decide | |
717 | if the packet should be dropped or not. | |
718 | ||
719 | If unsure, say N. | |
720 | ||
721 | To compile this code as a module, choose M here: the | |
722 | module will be called act_bpf. | |
723 | ||
22a5dc0e FF |
724 | config NET_ACT_CONNMARK |
725 | tristate "Netfilter Connection Mark Retriever" | |
726 | depends on NET_CLS_ACT && NETFILTER && IP_NF_IPTABLES | |
2dbce096 | 727 | depends on NF_CONNTRACK && NF_CONNTRACK_MARK |
22a5dc0e FF |
728 | ---help--- |
729 | Say Y here to allow retrieving of conn mark | |
730 | ||
731 | If unsure, say N. | |
732 | ||
733 | To compile this code as a module, choose M here: the | |
734 | module will be called act_connmark. | |
735 | ||
52ab4ac2 TG |
736 | config NET_CLS_IND |
737 | bool "Incoming device classification" | |
05b8b0fa | 738 | depends on NET_CLS_U32 || NET_CLS_FW |
52ab4ac2 TG |
739 | ---help--- |
740 | Say Y here to extend the u32 and fw classifier to support | |
741 | classification based on the incoming device. This option is | |
742 | likely to disappear in favour of the metadata ematch. | |
743 | ||
05b8b0fa RZ |
744 | endif # NET_SCHED |
745 | ||
85ef3e5c RD |
746 | config NET_SCH_FIFO |
747 | bool |