One QoS at a time Method is same - measure after each adjustment.
openwrt wired
https://www.waveform.com/tools/bufferbloat?test-id=1d72998e-b4d5-45b7-a8d4-1f2d5b2261d3
having some problems with waveform taking long to start give me a bit
ingress on 0 egress 72192
https://www.waveform.com/tools/bufferbloat?test-id=0dfcdd7b-a6e5-46fb-9805-117b2e2fe346
ingress 0 egress 135360
https://www.waveform.com/tools/bufferbloat?test-id=2bc305cf-5593-4258-b2fb-a1f0236c2b21
You can find a customized fork of Elan's script in my GitHub repository. I made some adjustments to it a while back based on requests from a few forum members, so it now works with ctinfo. Feel free to try it out, but if you run into issues, youâll need to solve them yourself, as I don't actively support this fork.
As @moeller0 already mentioned, you can use qosmate. Additionally, for some time now, the UI has featured a new "custom rules" option, allowing you to manually enter additional nftables rules directly in the UI. You could take Elan's rules, modify them, and use them with qosmate. @choppyc has already done some preliminary work by incorporating some of these rules, which you should be able to find in the qosmate thread.
One quick note (and this isn't meant to be harsh): Elan's script uses a lot of marking based on packet lengths or rate limits, which can be right in some cases but not in others. Personally, I'm not a huge fan of such heuristic rules. They might work today but not necessarily tomorrow.
For example: If your gaming packets are always under 500 bytes today, and you set up a rule that prioritizes packets smaller than 500 bytes into the highest class, it might work for now. However, if the game developers decide tomorrow to pack more information into a single packet and increase the size, your rules will break. Prioritizing a gaming port/IP/protocol combination is much more robust and future-proof, even if it doesnât look as flashy as prioritizing based on arbitrary packet sizes.
i tried everthing but elanscript..i play call of duty only and trying to optimize my connection as best as possible.. at times i have to pump so much bullets in a player to get a kill my hit detection is off ...i love qosmate because its so easy to use but not getting the results probably i need to set it up correctly for my connection..any help will be much appreciated
A living nightmare, surely.
What kind of connection do you have?
fiber 150 up 150 down
Device Information
On this page, you can view basic device information.
Basic Information
Device Type: HG8145X6-10
Description: OptiXstar HG8145X6-10 GPON Terminal (CLASS B+/PRODUCT ID:2150086468QUQ2001459)
SN: 48575443DF1B17AE (HWTCDF1B17AE)
Hardware Version: 2C6D.A
Software Version: V5R022C00S115
Manufacture Info: 2150086468QUQ2001459.C402
ONT Registration Status: O5(Operation state)
ONT ID: 6
CPU Usage: 9%
Memory Usage: 47%
Custom Info: TSTT
System Time: 2024-10-08 17:12:30-04:00
You could also give DSCP Classify a try if you haven't done so yet. I'm currently using it myself but I'll try to switch to qosmate the next days as DSCP Classify hasn't seen any updates for a while.
tried it switched back to qosmate and just fiddling with some configurations
Im runing dscpclassify and i play cod and destiny 2 and for cod i have good and bad plays .
Some times i get Packet Burst,
i have one question for @Hudra the script from @ldir have any "marking based on packet lengths or rate limits"
waweform test shows 200ms latency spike likely out of your control, was 500ms.
You can add dscp via firewall based on packet size etc
This is for my question!!
If you need help setting up qosmate, feel free to ask any questions. Looking at your bufferbloat test results, I would definitely recommend limiting your upload and download bandwidth to around 135000 kbps.
Is this the question?
Yes, i dont know if the dscpclassify have any marking on packet or rate limits,?
I love to try with only dscp marks on ip ports and proto
Why not have a look at the readme?
Yes it the Dynamic classification, can be removed