Yes, should be fine i have FTTP and use same.
1 Like
thank you, yesterday I gave it a try while gaming, I think I actually felt a difference, I will test it more
Hi
I added a class in the quick add config, which is shown to choose in the Classification Rule Tab and is shown in the available classes to which I can add ports to it, BUT in the Status TAB is not showing my new class
@Christoph34 Could you provide screen shots? The Status Tab is a output of qosify status , what exactly are you expecting to see?
@Christoph34 - ive pushed an update 2.4.1, there was a bug with the config and classification panels not refreshing.
ok then, I added a class, no problems there, I can add whatever port to the class I just created , no problem
and I was expecting to see that class shown in this tab
The problem with adding a TCP port to the priority set the way it's shown there: no port number is specified, so nothing actually gets added. Because nothing is written to 00-default.conf, the rule doesn't exist as far as qosify is concerned — you'd see something like tcp:53 priority in the Classification window (which would send TCP 53 traffic into the Voice tin), but if you haven't committed it, you haven't set anything.
To do it properly, add the priority rule in config:
-
Go to Classification.
-
Select your port — e.g. UDP 3074.
-
Pick the priority/class from the dropdown.
-
Press Add.
The rule then appears in 00-default.conf below. Now when you fire up Call of Duty, traffic on UDP 3074 lands in the Voice tin as expected.
This is just default qosify behaviour. The quick-add doesn't change what qosify actually does under the hood — it's only there to help drop in rules on the fly when you need them.
1 Like
that is exactly what I'm doing, I was showing you where, wasn't a detailed "how to"
I added port UDP 10200 to my premade class, then it shown correctly along with udp:80 and others
I not saying is wrong or anything bad, but could be useful to see traffic going through the rules we make
qosify doesn't expose per-connection DSCP state.
Hello! I want to give your app a try but I already have luci-app-sqm installed for to limit the guest network can I keep sqm running or I need to delete it and can the same functionally be on qosify?
No, don't run SQM and qosify on the same interface at the same time.
You can keep SQM installed, but disable it before enabling qosify on that interface.
1 Like
Can you guide me with how to set my bandwidth in this it says mbit? I have 25mbps internet package and have a router connected to a fiber modem which is in bridge mode so the only pppoe credentials are in the openwrt router would appreciate it 
Great initiative. But if it's going to be useful, a QoS frontend should simplify and solve the main problem with configuration, it's still alphabet soup for most users. This is a solution meant to democratize quality connectivity, yet little simplification is actually achieved. I've been observing this issue since the Tomato project's QoS (15 years ago or more). The approach that simplified things the most was the adoption of nDPI in Tomato64. I hope we follow that example.
2 Likes
You’re absolutely right — luci‑app‑qosify still exposes users to the same alphabet‑soup problem that Tomato, OpenWrt SQM, and every other QoS system has struggled with for 15+ years. Without automatic traffic identification (nDPI‑style), the burden stays on the user to understand ports, protocols, DSCPs, classes, and priorities. That’s the opposite of “democratising quality connectivity.”
1 Like
Yeah I was very confused at first still am how things works got a slight idea for now will test more to see
Look on the bright side, we can move forward with this solution by simplifying the code, keeping the "alphabet soup" in the backend, and offering the frontend with preset options and advanced settings. I don't like suggesting things without being able to contribute myself; I have limited knowledge in the packet queuing.
qosify itself is a pure backend tool — no GUI, no LuCI pages, no wizards. luci-app-qosify is a community LuCI frontend that tries to make qosify easier to use by exposing presets, editable lists, and import/export, while keeping the complex “alphabet soup” hidden in the backend. qosify was designed as a lightweight, low‑overhead classifier for OpenWrt, The LuCI app is basically a bridge between:
-
qosify’s raw config files
-
the user’s need for a friendly interface
It provides:
-
Preset class lists
-
Editable rule tables
-
Import/export of config files
-
Status view (reads qosify’s runtime state)
-
Buttons for restart/reload
It doesn’t replace qosify — it just makes it easier to interact with.
3 Likes
Yes, it’s a very nice initiative, which originally came from Dopamyth, a YouTuber who used to be active on the forum and created the interface. I follow him on YouTube; his gameplay is incredible. He told me that he also created GeoIP-Shell with an interface, as well as a geofilter and a gaming script.
He sent me his screenshots privately.
I think he doesn’t use QoSify for several reasons, and he told me that Elan was his friend during COVID, about five years ago.