Setup
hEXr3 on 6.38rc52
WAN interface is named E1WAN
LAN interface is named E2 WAN
The IP address for my PC is 192.186.88.250 Issue
I want to queue all PC traffic with a priority of 1, and all other traffic with a priority of 8.
Steps I have taken:
1.) assigned a new mangle rule with:
Chain:Forward Src address:192.168.88.250 Action: mark connection New Connection Mark: PC_Connection Passthrough: yes
2.) assigned a new mangle rule with:
Chain:Forward Dst address:192.168.88.250 Action: mark connection New Connection Mark: PC_Connection Passthrough: yes
Looks like this in winbox:
3.) assigned a new mangle rule with:
Chain:Forward Connection Mark: PC_Connection Action: mark packet New Packet Mark: PC_PACK Passthrough: yes
looks like this:
4.) I assigned a new simple queue (for pc traffic) with:
Name: PC_QoS Packet Marks: PC_PACK Target Upload Priority: 1 Target Download Priority: 1
looks like this:
5.) I assigned a new simple queue (for NON-PC traffic) with:
Name: NOT_PC_QoS Packet Marks: no-mark Target Upload Priority: 8 Target Download Priority: 8
looks like this:
My Mangle page looks like this, so I can tell it is marking packets right:
My queue list looks like this:
But if I go under the traffic tab for each simple queue I don’t see any traffic for either of them:
Is this is a known bug? Did I do something wrong? Is it really working? If so how can I tell?
Thanks for any help in this matter!
sorry for the pics not working, they were on my end but it is a DNS issue with my website being fixed. Hopefully in the next day, you can see the issue more clearly (since the pics will be working)
Thanks for the general replies. I will continue to work on this on my own, and eventually figure it out. Yes pe1chi, que tree works I tried that as well, but I am trying to learn the simple que, and simple que should work as well. Also I posted pictures, in case someone who doesn’t use CLI for everything (AKA this “Beginner Basics” forum) has the same issue. Most of the help on this forum is very outdated CLI examples (if your lucky, and lucky if they still work, and even luckier if they are formatted and written right) or more often than not just vague generalities. So, once I figure it out, I will post even more pictures and the relevant export of how a simple (not even limiting speed) two part que works, and maybe it will help someone in the future when they are stuck and come here. Thanks.
Teamer, if they are fast tracked, would the packets still be processed ahead of nonmarked packets? Or do all fast tracked packets skip all ques?
I guess I just have a gross conceptual error on how this queuing thing works. I was under the impression I could mark all packets going to (and coming from) the PC, set them with a priority of 1, set everything else at 8, and then all the packets for the PC would go to the head of the line.
So, I guess that grand experiment is over. All I really wanted to do was prioritize PC traffic over everything else, so when everyone else is streaming, the PC would still be capable of gaming without lag going through the roof. I have a 300/20 connection wanted to make sure other devices always had at least 50/4 (and more when the PC wasnt downloading). So I guess I wanted to limit the PC to 250/16 as well.
Wanted to get back with this, I disabled fastrack in my firewall rules, and the way I set it up in the original post works. It works extremely well actually. Thanks for the tip about turning off fasttrack,
Oh and turning off fasttrack doesn’t cripple a 350Mbs connection btw. I thought it would, so I was hesitant to turn it off, but even with it maxed out the hEX r3 topped out at 45% CPU usage with 2 simple ques and 11 firewall rules. Big difference coming from a ERL where turning off hw offload maxed me out at 60Mbs, glad I made the switch to the hex. My bufferbloat went from a C to an A as well.
