table of contents
- Tumbleweed 3.1.8-1.1
- Leap-15.6
| fireqos-params(5) | 3.1.8 | fireqos-params(5) |
NAME¶
fireqos-params - shared class/match parameters
SYNOPSIS¶
prio
priority
DESCRIPTION¶
Some optional parameter names are the same for both class and match. This page exists as a placeholder to help you find the appropriate documentation.
If you are searching for FireQOS parameters in general, see both fireqos-params-class(5) and/or fireqos-params-match(5) depending upon your need.
- prio
- For the class version, see fireqos-params-class(5).
For the match version, see fireqos-params-match(5).
- priority
- For the class version, see fireqos-params-match(5).
For the match version, see fireqos-params-class(5).
SEE ALSO¶
- •
- fireqos-params-class(5) - QOS class parameters
- •
- fireqos-params-match(5) - QOS match parameters
- •
- FireHOL Website (http://firehol.org/)
- •
- FireQOS Online PDF Manual (http://firehol.org/fireqos-manual.pdf)
- •
- FireQOS Online Documentation (http://firehol.org/documentation/) ve the same prio.
Note
match rules are attached to the parent of the class they appear in. Within the configuration they are written under a class, but in reality they are attached to their class parent, so that they classify the parent’s traffic that they match, into the class.
It is also possible to group all match statements together below the classes. This allows them to be arranged in preferred order, without the need for any explicit prio parameters. In this case however, each match statement must specify to which class it classifies the packets it matches, using the class parameter. See fireqos-params-match(5) and the examples below.
You can also write client and server statements, much like FireHOL allows, with the same service definitions. For FireQOS however, the client ports are ignored. server statements match the server ports on this linux side, while client statements match the server ports on the remote side.
Example:
-
server_myrtp_ports="10000:10100"
interface eth0 lan bidirectional rate 1Gbit
class voip
server sip
client sip
server myrtp
class dns
server dns
class mail
server smtp
PARAMETERS¶
- optional-match-params
- The set of optional parameters which describe this match. See fireqos-params-match(5).
EXAMPLES¶
Match traffic within classes:
-
interface eth0 lan output rate 1Gbit
class voip
match udp ports 5060,10000:10100
class dns
match udp port 53
class mail
match tcp port 25
Matches split out and explicitly assigning traffic to classes (N.B. without the class parameters, all traffic would be classified into `mail'):
-
interface eth0 lan output rate 1Gbit
class voip
class dns
class mail
match udp ports 5060,10000:10100 class voip
match tcp port 25 class mail
match tcp port 80 class web
SEE ALSO¶
- •
- fireqos-params-match(5) - QOS match parameters
- •
- fireqos(1) - FireQOS program
- •
- fireqos.conf(5) - FireQOS configuration file
- •
- fireqos-interface(5) - QOS interface definition
- •
- fireqos-class(5) - QOS class definition
- •
- FireHOL Website (http://firehol.org/)
- •
- FireQOS Online PDF Manual (http://firehol.org/fireqos-manual.pdf)
- •
- FireQOS Online Documentation (http://firehol.org/documentation/)
- •
- tc(8) (http://lartc.org/manpages/tc.html) - show / manipulate traffic control settings
AUTHORS¶
FireHOL Team.
| Built 15 Mar 2025 | FireQOS Reference |