# SPDX-License-Identifier: GPL-2.0-only
#
# Traffic control configuration.
#
menuconfig [31mCONFIG_NET_SCHED[0m
bool "QoS and/or fair queueing"
select [31mCONFIG_NET_SCH_FIFO[0m
---help---
When the kernel has several packets to send out over a network
device, it has to decide which ones to send first, which ones to
delay, and which ones to drop. This is the job of the queueing
disciplines, several different algorithms for how to do this
"fairly" have been proposed.
If you say N here, you will get the standard packet scheduler, which
is a FIFO (first come, first served). If you say Y here, you will be
able to choose from among several alternative algorithms which can
then be attached to different network devices. This is useful for
example if some of your network devices are real time devices that
need a certain minimum data flow rate, or if you need to limit the
maximum data flow rate for traffic which matches specified criteria.
This code is considered to be experimental.
To administer these schedulers, you'll need the user-level utilities
from the package iproute2+tc at
<https://www.kernel.org/pub/linux/utils/net/iproute2/>. That package
also contains some documentation; for more, check out
<http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2>.
This Quality of Service (QoS) support will enable you to use
Differentiated Services (diffserv) and Resource Reservation Protocol
(RSVP) on your Linux router if you also say Y to the corresponding
classifiers below. Documentation and software is at
<http://diffserv.sourceforge.net/>.
If you say Y here and to "/proc file system" below, you will be able
to read status information about packet schedulers from the file
/proc/net/psched.
The available schedulers are listed in the following questions; you
can say Y to as many as you like. If unsure, say N now.
if [31mCONFIG_NET_SCHED[0m
comment "Queueing/Scheduling"
config [31mCONFIG_NET_SCH_CBQ[0m
tristate "Class Based Queueing (CBQ)"
---help---
Say Y here if you want to use the Class-Based Queueing (CBQ) packet
scheduling algorithm. This algorithm classifies the waiting packets
into a tree-like hierarchy of classes; the leaves of this tree are
in turn scheduled by separate algorithms.
See the top of <file:net/sched/sch_cbq.c> for more details.
CBQ is a commonly used scheduler, so if you're unsure, you should
say Y here. Then say Y to all the queueing algorithms below that you
want to use as leaf disciplines.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called sch_cbq.
config [31mCONFIG_NET_SCH_HTB[0m
tristate "Hierarchical Token Bucket (HTB)"
---help---
Say Y here if you want to use the Hierarchical Token Buckets (HTB)
packet scheduling algorithm. See
<http://luxik.cdi.cz/~devik/qos/htb/> for complete manual and
in-depth articles.
HTB is very similar to CBQ regarding its goals however is has
different properties and different algorithm.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called sch_htb.
config [31mCONFIG_NET_SCH_HFSC[0m
tristate "Hierarchical Fair Service Curve (HFSC)"
---help---
Say Y here if you want to use the Hierarchical Fair Service Curve
(HFSC) packet scheduling algorithm.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called sch_hfsc.
config [31mCONFIG_NET_SCH_ATM[0m
tristate "ATM Virtual Circuits (ATM)"
depends on [31mCONFIG_ATM[0m
---help---
Say Y here if you want to use the [31mCONFIG_ATM[0m pseudo-scheduler. This
provides a framework for invoking classifiers, which in turn
select classes of this queuing discipline. Each class maps
the flow(s) it is handling to a given virtual circuit.
See the top of <file:net/sched/sch_atm.c> for more details.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called sch_atm.
config [31mCONFIG_NET_SCH_PRIO[0m
tristate "Multi Band Priority Queueing (PRIO)"
---help---
Say Y here if you want to use an n-band priority queue packet
scheduler.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called sch_prio.
config [31mCONFIG_NET_SCH_MULTIQ[0m
tristate "Hardware Multiqueue-aware Multi Band Queuing (MULTIQ)"
---help---
Say Y here if you want to use an n-band queue packet scheduler
to support devices that have multiple hardware transmit queues.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called sch_multiq.
config [31mCONFIG_NET_SCH_RED[0m
tristate "Random Early Detection (RED)"
---help---
Say Y here if you want to use the Random Early Detection (RED)
packet scheduling algorithm.
See the top of <file:net/sched/sch_red.c> for more details.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called sch_red.
config [31mCONFIG_NET_SCH_SFB[0m
tristate "Stochastic Fair Blue (SFB)"
---help---
Say Y here if you want to use the Stochastic Fair Blue (SFB)
packet scheduling algorithm.
See the top of <file:net/sched/sch_sfb.c> for more details.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called sch_sfb.
config [31mCONFIG_NET_SCH_SFQ[0m
tristate "Stochastic Fairness Queueing (SFQ)"
---help---
Say Y here if you want to use the Stochastic Fairness Queueing (SFQ)
packet scheduling algorithm.
See the top of <file:net/sched/sch_sfq.c> for more details.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called sch_sfq.
config [31mCONFIG_NET_SCH_TEQL[0m
tristate "True Link Equalizer (TEQL)"
---help---
Say Y here if you want to use the True Link Equalizer (TLE) packet
scheduling algorithm. This queueing discipline allows the combination
of several physical devices into one virtual device.
See the top of <file:net/sched/sch_teql.c> for more details.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called sch_teql.
config [31mCONFIG_NET_SCH_TBF[0m
tristate "Token Bucket Filter (TBF)"
---help---
Say Y here if you want to use the Token Bucket Filter (TBF) packet
scheduling algorithm.
See the top of <file:net/sched/sch_tbf.c> for more details.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called sch_tbf.
config [31mCONFIG_NET_SCH_CBS[0m
tristate "Credit Based Shaper (CBS)"
---help---
Say Y here if you want to use the Credit Based Shaper (CBS) packet
scheduling algorithm.
See the top of <file:net/sched/sch_cbs.c> for more details.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called sch_cbs.
config [31mCONFIG_NET_SCH_ETF[0m
tristate "Earliest TxTime First (ETF)"
help
Say Y here if you want to use the Earliest TxTime First (ETF) packet
scheduling algorithm.
See the top of <file:net/sched/sch_etf.c> for more details.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called sch_etf.
config [31mCONFIG_NET_SCH_TAPRIO[0m
tristate "Time Aware Priority (taprio) Scheduler"
help
Say Y here if you want to use the Time Aware Priority (taprio) packet
scheduling algorithm.
See the top of <file:net/sched/sch_taprio.c> for more details.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called sch_taprio.
config [31mCONFIG_NET_SCH_GRED[0m
tristate "Generic Random Early Detection (GRED)"
---help---
Say Y here if you want to use the Generic Random Early Detection
(GRED) packet scheduling algorithm for some of your network devices
(see the top of <file:net/sched/sch_red.c> for details and
references about the algorithm).
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called sch_gred.
config [31mCONFIG_NET_SCH_DSMARK[0m
tristate "Differentiated Services marker (DSMARK)"
---help---
Say Y if you want to schedule packets according to the
Differentiated Services architecture proposed in RFC 2475.
Technical information on this method, with pointers to associated
RFCs, is available at <http://www.gta.ufrj.br/diffserv/>.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called sch_dsmark.
config [31mCONFIG_NET_SCH_NETEM[0m
tristate "Network emulator (NETEM)"
---help---
Say Y if you want to emulate network delay, loss, and packet
re-ordering. This is often useful to simulate networks when
testing applications or protocols.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called sch_netem.
If unsure, say N.
config [31mCONFIG_NET_SCH_DRR[0m
tristate "Deficit Round Robin scheduler (DRR)"
help
Say Y here if you want to use the Deficit Round Robin (DRR) packet
scheduling algorithm.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called sch_drr.
If unsure, say N.
config [31mCONFIG_NET_SCH_MQPRIO[0m
tristate "Multi-queue priority scheduler (MQPRIO)"
help
Say Y here if you want to use the Multi-queue Priority scheduler.
This scheduler allows QOS to be offloaded on NICs that have support
for offloading QOS schedulers.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will
be called sch_mqprio.
If unsure, say N.
config [31mCONFIG_NET_SCH_SKBPRIO[0m
tristate "SKB priority queue scheduler (SKBPRIO)"
help
Say Y here if you want to use the SKB priority queue
scheduler. This schedules packets according to skb->priority,
which is useful for request packets in DoS mitigation systems such
as Gatekeeper.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will
be called sch_skbprio.
If unsure, say N.
config [31mCONFIG_NET_SCH_CHOKE[0m
tristate "CHOose and Keep responsive flow scheduler (CHOKE)"
help
Say Y here if you want to use the CHOKe packet scheduler (CHOose
and Keep for responsive flows, CHOose and Kill for unresponsive
flows). This is a variation of RED which trys to penalize flows
that monopolize the queue.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called sch_choke.
config [31mCONFIG_NET_SCH_QFQ[0m
tristate "Quick Fair Queueing scheduler (QFQ)"
help
Say Y here if you want to use the Quick Fair Queueing Scheduler (QFQ)
packet scheduling algorithm.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called sch_qfq.
If unsure, say N.
config [31mCONFIG_NET_SCH_CODEL[0m
tristate "Controlled Delay AQM (CODEL)"
help
Say Y here if you want to use the Controlled Delay (CODEL)
packet scheduling algorithm.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called sch_codel.
If unsure, say N.
config [31mCONFIG_NET_SCH_FQ_CODEL[0m
tristate "Fair Queue Controlled Delay AQM (FQ_CODEL)"
help
Say Y here if you want to use the FQ Controlled Delay (FQ_CODEL)
packet scheduling algorithm.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called sch_fq_codel.
If unsure, say N.
config [31mCONFIG_NET_SCH_CAKE[0m
tristate "Common Applications Kept Enhanced (CAKE)"
help
Say Y here if you want to use the Common Applications Kept Enhanced
(CAKE) queue management algorithm.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called sch_cake.
If unsure, say N.
config [31mCONFIG_NET_SCH_FQ[0m
tristate "Fair Queue"
help
Say Y here if you want to use the FQ packet scheduling algorithm.
FQ does flow separation, and is able to respect pacing requirements
set by TCP stack into sk->sk_pacing_rate (for localy generated
traffic)
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called sch_fq.
If unsure, say N.
config [31mCONFIG_NET_SCH_HHF[0m
tristate "Heavy-Hitter Filter (HHF)"
help
Say Y here if you want to use the Heavy-Hitter Filter (HHF)
packet scheduling algorithm.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called sch_hhf.
config [31mCONFIG_NET_SCH_PIE[0m
tristate "Proportional Integral controller Enhanced (PIE) scheduler"
help
Say Y here if you want to use the Proportional Integral controller
Enhanced scheduler packet scheduling algorithm.
For more information, please see https://tools.ietf.org/html/rfc8033
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called sch_pie.
If unsure, say N.
config [31mCONFIG_NET_SCH_INGRESS[0m
tristate "Ingress/classifier-action Qdisc"
depends on [31mCONFIG_NET_CLS_ACT[0m
select [31mCONFIG_NET_INGRESS[0m
select [31mCONFIG_NET_EGRESS[0m
---help---
Say Y here if you want to use classifiers for incoming and/or outgoing
packets. This qdisc doesn't do anything else besides running classifiers,
which can also have actions attached to them. In case of outgoing packets,
classifiers that this qdisc holds are executed in the transmit path
before real enqueuing to an egress qdisc happens.
If unsure, say Y.
To compile this code as a module, choose [31mCONFIG_M[0m here: the module will be
called sch_ingress with alias of sch_clsact.
config [31mCONFIG_NET_SCH_PLUG[0m
tristate "Plug network traffic until release (PLUG)"
---help---
This queuing discipline allows userspace to plug/unplug a network
output queue, using the netlink interface. When it receives an
enqueue command it inserts a plug into the outbound queue that
causes following packets to enqueue until a dequeue command arrives
over netlink, causing the plug to be removed and resuming the normal
packet flow.
This module also provides a generic "network output buffering"
functionality (aka output commit), wherein upon arrival of a dequeue
command, only packets up to the first plug are released for delivery.
The Remus HA project uses this module to enable speculative execution
of virtual machines by allowing the generated network output to be rolled
back if needed.
For more information, please refer to <http://wiki.xenproject.org/wiki/Remus>
Say Y here if you are using this kernel for Xen dom0 and
want to protect Xen guests with Remus.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called sch_plug.
menuconfig [31mCONFIG_NET_SCH_DEFAULT[0m
bool "Allow override default queue discipline"
---help---
Support for selection of default queuing discipline.
Nearly all users can safely say no here, and the default
of pfifo_fast will be used. Many distributions already set
the default value via /proc/sys/net/core/default_qdisc.
If unsure, say N.
if [31mCONFIG_NET_SCH_DEFAULT[0m
choice
prompt "Default queuing discipline"
default [31mCONFIG_DEFAULT_PFIFO_FAST[0m
help
Select the queueing discipline that will be used by default
for all network devices.
config [31mCONFIG_DEFAULT_FQ[0m
bool "Fair Queue" if [31mCONFIG_NET_SCH_FQ[0m
config [31mCONFIG_DEFAULT_CODEL[0m
bool "Controlled Delay" if [31mCONFIG_NET_SCH_CODEL[0m
config [31mCONFIG_DEFAULT_FQ_CODEL[0m
bool "Fair Queue Controlled Delay" if [31mCONFIG_NET_SCH_FQ_CODEL[0m
config [31mCONFIG_DEFAULT_SFQ[0m
bool "Stochastic Fair Queue" if [31mCONFIG_NET_SCH_SFQ[0m
config [31mCONFIG_DEFAULT_PFIFO_FAST[0m
bool "Priority FIFO Fast"
endchoice
config [31mCONFIG_DEFAULT_NET_SCH[0m
string
default "pfifo_fast" if [31mCONFIG_DEFAULT_PFIFO_FAST[0m
default "fq" if [31mCONFIG_DEFAULT_FQ[0m
default "fq_codel" if [31mCONFIG_DEFAULT_FQ_CODEL[0m
default "sfq" if [31mCONFIG_DEFAULT_SFQ[0m
default "pfifo_fast"
endif
comment "Classification"
config [31mCONFIG_NET_CLS[0m
bool
config [31mCONFIG_NET_CLS_BASIC[0m
tristate "Elementary classification (BASIC)"
select [31mCONFIG_NET_CLS[0m
---help---
Say Y here if you want to be able to classify packets using
only extended matches and actions.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called cls_basic.
config [31mCONFIG_NET_CLS_TCINDEX[0m
tristate "Traffic-Control Index (TCINDEX)"
select [31mCONFIG_NET_CLS[0m
---help---
Say Y here if you want to be able to classify packets based on
traffic control indices. You will want this feature if you want
to implement Differentiated Services together with DSMARK.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called cls_tcindex.
config [31mCONFIG_NET_CLS_ROUTE4[0m
tristate "Routing decision (ROUTE)"
depends on [31mCONFIG_INET[0m
select [31mCONFIG_IP_ROUTE_CLASSID[0m
select [31mCONFIG_NET_CLS[0m
---help---
If you say Y here, you will be able to classify packets
according to the route table entry they matched.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called cls_route.
config [31mCONFIG_NET_CLS_FW[0m
tristate "Netfilter mark (FW)"
select [31mCONFIG_NET_CLS[0m
---help---
If you say Y here, you will be able to classify packets
according to netfilter/firewall marks.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called cls_fw.
config [31mCONFIG_NET_CLS_U32[0m
tristate "Universal 32bit comparisons w/ hashing (U32)"
select [31mCONFIG_NET_CLS[0m
---help---
Say Y here to be able to classify packets using a universal
32bit pieces based comparison scheme.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called cls_u32.
config [31mCONFIG_CLS_U32_PERF[0m
bool "Performance counters support"
depends on [31mCONFIG_NET_CLS_U32[0m
---help---
Say Y here to make u32 gather additional statistics useful for
fine tuning u32 classifiers.
config [31mCONFIG_CLS_U32_MARK[0m
bool "Netfilter marks support"
depends on [31mCONFIG_NET_CLS_U32[0m
---help---
Say Y here to be able to use netfilter marks as u32 key.
config [31mCONFIG_NET_CLS_RSVP[0m
tristate "IPv4 Resource Reservation Protocol (RSVP)"
select [31mCONFIG_NET_CLS[0m
---help---
The Resource Reservation Protocol (RSVP) permits end systems to
request a minimum and maximum data flow rate for a connection; this
is important for real time data such as streaming sound or video.
Say Y here if you want to be able to classify outgoing packets based
on their RSVP requests.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called cls_rsvp.
config [31mCONFIG_NET_CLS_RSVP6[0m
tristate "IPv6 Resource Reservation Protocol (RSVP6)"
select [31mCONFIG_NET_CLS[0m
---help---
The Resource Reservation Protocol (RSVP) permits end systems to
request a minimum and maximum data flow rate for a connection; this
is important for real time data such as streaming sound or video.
Say Y here if you want to be able to classify outgoing packets based
on their RSVP requests and you are using the IPv6 protocol.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called cls_rsvp6.
config [31mCONFIG_NET_CLS_FLOW[0m
tristate "Flow classifier"
select [31mCONFIG_NET_CLS[0m
---help---
If you say Y here, you will be able to classify packets based on
a configurable combination of packet keys. This is mostly useful
in combination with SFQ.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called cls_flow.
config [31mCONFIG_NET_CLS_CGROUP[0m
tristate "Control Group Classifier"
select [31mCONFIG_NET_CLS[0m
select [31mCONFIG_CGROUP_NET_CLASSID[0m
depends on [31mCONFIG_CGROUPS[0m
---help---
Say Y here if you want to classify packets based on the control
cgroup of their process.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called cls_cgroup.
config [31mCONFIG_NET_CLS_BPF[0m
tristate "BPF-based classifier"
select [31mCONFIG_NET_CLS[0m
---help---
If you say Y here, you will be able to classify packets based on
programmable [31mCONFIG_BPF[0m (JIT'ed) filters as an alternative to ematches.
To compile this code as a module, choose [31mCONFIG_M[0m here: the module will
be called cls_bpf.
config [31mCONFIG_NET_CLS_FLOWER[0m
tristate "Flower classifier"
select [31mCONFIG_NET_CLS[0m
---help---
If you say Y here, you will be able to classify packets based on
a configurable combination of packet keys and masks.
To compile this code as a module, choose [31mCONFIG_M[0m here: the module will
be called cls_flower.
config [31mCONFIG_NET_CLS_MATCHALL[0m
tristate "Match-all classifier"
select [31mCONFIG_NET_CLS[0m
---help---
If you say Y here, you will be able to classify packets based on
nothing. Every packet will match.
To compile this code as a module, choose [31mCONFIG_M[0m here: the module will
be called cls_matchall.
config [31mCONFIG_NET_EMATCH[0m
bool "Extended Matches"
select [31mCONFIG_NET_CLS[0m
---help---
Say Y here if you want to use extended matches on top of classifiers
and select the extended matches below.
Extended matches are small classification helpers not worth writing
a separate classifier for.
[31mCONFIG_A[0m recent version of the iproute2 package is required to use
extended matches.
config [31mCONFIG_NET_EMATCH_STACK[0m
int "Stack size"
depends on [31mCONFIG_NET_EMATCH[0m
default "32"
---help---
Size of the local stack variable used while evaluating the tree of
ematches. Limits the depth of the tree, i.e. the number of
encapsulated precedences. Every level requires 4 bytes of additional
stack space.
config [31mCONFIG_NET_EMATCH_CMP[0m
tristate "Simple packet data comparison"
depends on [31mCONFIG_NET_EMATCH[0m
---help---
Say Y here if you want to be able to classify packets based on
simple packet data comparisons for 8, 16, and 32bit values.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called em_cmp.
config [31mCONFIG_NET_EMATCH_NBYTE[0m
tristate "Multi byte comparison"
depends on [31mCONFIG_NET_EMATCH[0m
---help---
Say Y here if you want to be able to classify packets based on
multiple byte comparisons mainly useful for IPv6 address comparisons.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called em_nbyte.
config [31mCONFIG_NET_EMATCH_U32[0m
tristate "U32 key"
depends on [31mCONFIG_NET_EMATCH[0m
---help---
Say Y here if you want to be able to classify packets using
the famous u32 key in combination with logic relations.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called em_u32.
config [31mCONFIG_NET_EMATCH_META[0m
tristate "Metadata"
depends on [31mCONFIG_NET_EMATCH[0m
---help---
Say Y here if you want to be able to classify packets based on
metadata such as load average, netfilter attributes, socket
attributes and routing decisions.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called em_meta.
config [31mCONFIG_NET_EMATCH_TEXT[0m
tristate "Textsearch"
depends on [31mCONFIG_NET_EMATCH[0m
select [31mCONFIG_TEXTSEARCH[0m
select [31mCONFIG_TEXTSEARCH_KMP[0m
select [31mCONFIG_TEXTSEARCH_BM[0m
select [31mCONFIG_TEXTSEARCH_FSM[0m
---help---
Say Y here if you want to be able to classify packets based on
textsearch comparisons.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called em_text.
config [31mCONFIG_NET_EMATCH_CANID[0m
tristate "CAN Identifier"
depends on [31mCONFIG_NET_EMATCH[0m && ([31mCONFIG_CAN[0m=y || [31mCONFIG_CAN[0m=m)
---help---
Say Y here if you want to be able to classify [31mCONFIG_CAN[0m frames based
on [31mCONFIG_CAN[0m Identifier.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called em_canid.
config [31mCONFIG_NET_EMATCH_IPSET[0m
tristate "IPset"
depends on [31mCONFIG_NET_EMATCH[0m && [31mCONFIG_IP_SET[0m
---help---
Say Y here if you want to be able to classify packets based on
ipset membership.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called em_ipset.
config [31mCONFIG_NET_EMATCH_IPT[0m
tristate "IPtables Matches"
depends on [31mCONFIG_NET_EMATCH[0m && [31mCONFIG_NETFILTER[0m && [31mCONFIG_NETFILTER_XTABLES[0m
---help---
Say Y here to be able to classify packets based on iptables
matches.
Current supported match is "policy" which allows packet classification
based on IPsec policy that was used during decapsulation
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called em_ipt.
config [31mCONFIG_NET_CLS_ACT[0m
bool "Actions"
select [31mCONFIG_NET_CLS[0m
---help---
Say Y here if you want to use traffic control actions. Actions
get attached to classifiers and are invoked after a successful
classification. They are used to overwrite the classification
result, instantly drop or redirect packets, etc.
[31mCONFIG_A[0m recent version of the iproute2 package is required to use
extended matches.
config [31mCONFIG_NET_ACT_POLICE[0m
tristate "Traffic Policing"
depends on [31mCONFIG_NET_CLS_ACT[0m
---help---
Say Y here if you want to do traffic policing, i.e. strict
bandwidth limiting. This action replaces the existing policing
module.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called act_police.
config [31mCONFIG_NET_ACT_GACT[0m
tristate "Generic actions"
depends on [31mCONFIG_NET_CLS_ACT[0m
---help---
Say Y here to take generic actions such as dropping and
accepting packets.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called act_gact.
config [31mCONFIG_GACT_PROB[0m
bool "Probability support"
depends on [31mCONFIG_NET_ACT_GACT[0m
---help---
Say Y here to use the generic action randomly or deterministically.
config [31mCONFIG_NET_ACT_MIRRED[0m
tristate "Redirecting and Mirroring"
depends on [31mCONFIG_NET_CLS_ACT[0m
---help---
Say Y here to allow packets to be mirrored or redirected to
other devices.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called act_mirred.
config [31mCONFIG_NET_ACT_SAMPLE[0m
tristate "Traffic Sampling"
depends on [31mCONFIG_NET_CLS_ACT[0m
select [31mCONFIG_PSAMPLE[0m
---help---
Say Y here to allow packet sampling tc action. The packet sample
action consists of statistically choosing packets and sampling
them using the psample module.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called act_sample.
config [31mCONFIG_NET_ACT_IPT[0m
tristate "IPtables targets"
depends on [31mCONFIG_NET_CLS_ACT[0m && [31mCONFIG_NETFILTER[0m && [31mCONFIG_IP_NF_IPTABLES[0m
---help---
Say Y here to be able to invoke iptables targets after successful
classification.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called act_ipt.
config [31mCONFIG_NET_ACT_NAT[0m
tristate "Stateless NAT"
depends on [31mCONFIG_NET_CLS_ACT[0m
---help---
Say Y here to do stateless NAT on IPv4 packets. You should use
netfilter for NAT unless you know what you are doing.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called act_nat.
config [31mCONFIG_NET_ACT_PEDIT[0m
tristate "Packet Editing"
depends on [31mCONFIG_NET_CLS_ACT[0m
---help---
Say Y here if you want to mangle the content of packets.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called act_pedit.
config [31mCONFIG_NET_ACT_SIMP[0m
tristate "Simple Example (Debug)"
depends on [31mCONFIG_NET_CLS_ACT[0m
---help---
Say Y here to add a simple action for demonstration purposes.
It is meant as an example and for debugging purposes. It will
print a configured policy string followed by the packet count
to the console for every packet that passes by.
If unsure, say N.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called act_simple.
config [31mCONFIG_NET_ACT_SKBEDIT[0m
tristate "SKB Editing"
depends on [31mCONFIG_NET_CLS_ACT[0m
---help---
Say Y here to change skb priority or queue_mapping settings.
If unsure, say N.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called act_skbedit.
config [31mCONFIG_NET_ACT_CSUM[0m
tristate "Checksum Updating"
depends on [31mCONFIG_NET_CLS_ACT[0m && [31mCONFIG_INET[0m
select [31mCONFIG_LIBCRC32C[0m
---help---
Say Y here to update some common checksum after some direct
packet alterations.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called act_csum.
config [31mCONFIG_NET_ACT_MPLS[0m
tristate "MPLS manipulation"
depends on [31mCONFIG_NET_CLS_ACT[0m
help
Say Y here to push or pop [31mCONFIG_MPLS[0m headers.
If unsure, say N.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called act_mpls.
config [31mCONFIG_NET_ACT_VLAN[0m
tristate "Vlan manipulation"
depends on [31mCONFIG_NET_CLS_ACT[0m
---help---
Say Y here to push or pop vlan headers.
If unsure, say N.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called act_vlan.
config [31mCONFIG_NET_ACT_BPF[0m
tristate "BPF based action"
depends on [31mCONFIG_NET_CLS_ACT[0m
---help---
Say Y here to execute [31mCONFIG_BPF[0m code on packets. The [31mCONFIG_BPF[0m code will decide
if the packet should be dropped or not.
If unsure, say N.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called act_bpf.
config [31mCONFIG_NET_ACT_CONNMARK[0m
tristate "Netfilter Connection Mark Retriever"
depends on [31mCONFIG_NET_CLS_ACT[0m && [31mCONFIG_NETFILTER[0m && [31mCONFIG_IP_NF_IPTABLES[0m
depends on [31mCONFIG_NF_CONNTRACK[0m && [31mCONFIG_NF_CONNTRACK_MARK[0m
---help---
Say Y here to allow retrieving of conn mark
If unsure, say N.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called act_connmark.
config [31mCONFIG_NET_ACT_CTINFO[0m
tristate "Netfilter Connection Mark Actions"
depends on [31mCONFIG_NET_CLS_ACT[0m && [31mCONFIG_NETFILTER[0m && [31mCONFIG_IP_NF_IPTABLES[0m
depends on [31mCONFIG_NF_CONNTRACK[0m && [31mCONFIG_NF_CONNTRACK_MARK[0m
help
Say Y here to allow transfer of a connmark stored information.
Current actions transfer connmark stored DSCP into
ipv4/v6 diffserv and/or to transfer connmark to packet
mark. Both are useful for restoring egress based marks
back onto ingress connections for qdisc priority mapping
purposes.
If unsure, say N.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called act_ctinfo.
config [31mCONFIG_NET_ACT_SKBMOD[0m
tristate "skb data modification action"
depends on [31mCONFIG_NET_CLS_ACT[0m
---help---
Say Y here to allow modification of skb data
If unsure, say N.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called act_skbmod.
config [31mCONFIG_NET_ACT_IFE[0m
tristate "Inter-FE action based on IETF ForCES InterFE LFB"
depends on [31mCONFIG_NET_CLS_ACT[0m
select [31mCONFIG_NET_IFE[0m
---help---
Say Y here to allow for sourcing and terminating metadata
For details refer to netdev01 paper:
"Distributing Linux Traffic Control Classifier-Action Subsystem"
Authors: Jamal Hadi Salim and Damascene [31mCONFIG_M[0m. Joachimpillai
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called act_ife.
config [31mCONFIG_NET_ACT_TUNNEL_KEY[0m
tristate "IP tunnel metadata manipulation"
depends on [31mCONFIG_NET_CLS_ACT[0m
---help---
Say Y here to set/release ip tunnel metadata.
If unsure, say N.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called act_tunnel_key.
config [31mCONFIG_NET_ACT_CT[0m
tristate "connection tracking tc action"
depends on [31mCONFIG_NET_CLS_ACT[0m && [31mCONFIG_NF_CONNTRACK[0m && [31mCONFIG_NF_NAT[0m
help
Say Y here to allow sending the packets to conntrack module.
If unsure, say N.
To compile this code as a module, choose [31mCONFIG_M[0m here: the
module will be called act_ct.
config [31mCONFIG_NET_IFE_SKBMARK[0m
tristate "Support to encoding decoding skb mark on IFE action"
depends on [31mCONFIG_NET_ACT_IFE[0m
config [31mCONFIG_NET_IFE_SKBPRIO[0m
tristate "Support to encoding decoding skb prio on IFE action"
depends on [31mCONFIG_NET_ACT_IFE[0m
config [31mCONFIG_NET_IFE_SKBTCINDEX[0m
tristate "Support to encoding decoding skb tcindex on IFE action"
depends on [31mCONFIG_NET_ACT_IFE[0m
config [31mCONFIG_NET_TC_SKB_EXT[0m
bool "TC recirculation support"
depends on [31mCONFIG_NET_CLS_ACT[0m
select [31mCONFIG_SKB_EXTENSIONS[0m
help
Say Y here to allow tc chain misses to continue in OvS datapath in
the correct recirc_id, and hardware chain misses to continue in
the correct chain in tc software datapath.
Say N here if you won't be using tc<->ovs offload or tc chains offload.
endif # [31mCONFIG_NET_SCHED[0m
config [31mCONFIG_NET_SCH_FIFO[0m
bool