fireqos-match(5)

💖 fireqos-match — QOS traffic match 💖

okay bestie, welcome to the fireqos-match(5) page, part of the FireQOS Reference — this is where you learn how to tell FireQOS which packets belong to which class. it's giving traffic cop, but make it cute. let's go 🚦✨

---

✨ SYNOPSIS ✨

{match|match4|match6|match46} optional-match-params

---

🌸 DESCRIPTION 🌸

so here's the tea ☕ — writing plain match means it inherits its IPv4/IPv6 version from whatever class it's sitting inside. (peep fireqos-class(5) if you need the deets on that.)

• match4 — only IPv4 traffic gets included in the match, no cap.
• match6 — only IPv6 traffic, periodt.
• match46 — both IPv4 and IPv6, the whole buffet 💅

you can add as many match statements as your heart desires to a FireQOS config. they assign traffic to a class, and by default that class is the one right after where they're declared. iconic behaviour.

the order the matches appear in the config = their priority. first match gets a prio of 10, then 10 gets added for every match after it (10, 20, 30, ...). so like, first come first served, literally.

but wait, you can also set priority yourself explicitly with the prio parameter — see fireqos-params-match(5) for that.

and if one single match statement generates multiple tc(8) filter statements? every filter from that same match statement gets the same prio. they're a package deal bestie 🫶

Note 📌 match rules are attached to the parent of the class they appear in. like, in the config you write them under a class, but irl they're attached to their class parent — so they classify the parent's traffic that they match, into the class. sneaky but that's how it works 🙈

you can also group all your match statements together below the classes. this lets you arrange them in whatever order you prefer, no explicit prio parameters needed. but there's a catch (there's always a catch 😭): in this case every match statement must say which class it classifies packets into, using the class parameter. check fireqos-params-match(5) and the examples below for the full picture.

you can also write client and server statements, much like FireHOL lets you, with the same service definitions. for FireQOS tho, 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. iykyk 💅

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 that describe this match. go read fireqos-params-match(5) for the full menu, bestie 📋

---

🌈 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 (imagine 😭):

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
• FireQOS Online PDF Manual
• FireQOS Online Documentation
• tc(8) — show / manipulate traffic control settings

---

💜 AUTHORS 💜

FireHOL Team. (the icons who made all this possible, fr fr 👑)

---

and that's the whole page bestie!! this was the fireqos-match(5) manual from the FireQOS Reference, built 13 Apr 2025 — go forth and classify those packets, you absolute main character 🌟🦋 no cap, you're gonna slay this 💅✨