Killer Prioritization Engine in LEDE

mrmidnight · December 18, 2017, 9:57pm

--EDIT--
Since this thread has mostly turned into how to port this feature from the 32X, if you are a beginner to OpenWRT/LEDE I would not test any of these posts unless you truly know what you are doing. As I stated below I am not a developer, however I am a Data Analytics student. This does not make me an expert at all in any part of this, but I am researching into whether or not this can me utilized across the board for OpenWRT/LEDE and possibly in DD-WRT or Gargoyle. I'm also looking into if this can be used with other architectures other than mvebu. I would like to call onto developers that I have followed in the past to see if it is even worth the time to look into this @davidc502 @hnyman

Thanks
--END EDIT--

No I am not a developer, and no, I'm not asking a question on whether it can be ported, because I found something in the WRT32X source code. Looking in the folders I came across the folder "rivet" this folder contains the engine, which has been stated before is nothing more than a set of QoS rules. Looking in the readme for this, I found that this "engine" was made for the WRT1900ACS, on Chaos Calmer 15.05.1

I kind of fibbed a little on the question part, but I am wondering if something build for 15.05 can be used on 17.04?

The text of the readme is below:

Blockquote
Killer prioritization router installation instructions1.
Install OpenWRT on the router
Download OpenWRT for the 1900ACS, (REDACTED) (--edit--This is the correct link per @JW0914 https://wiki.openwrt.org/toh/linksys/wrt_ac_series).
Under OpenWrt Branches on said page you'll find the system image for the WRT1900ACS -- use the chaos calmer 15.05.1 download
You can install OpenWrt by flashing the system image onto the router by manually upgrading the routers
firmware on the routers site2. SSH into the router with OpenWRT once OpenWRT is installed
Copy the included scripts onto the router.
Make sure they are marked as execuable.
Install TC onto the router:
opkg update
opkg install tc iptables-mod-ipopt
To turn the prioritization routing you'll need to ./qdiscbr-lanscript.sh ./iptablesscript.sh and
./qdisceth0_on.sh 3. How to verify in SSH
ensure you have enabled the necessary scripts and establish connections with dscp markings via killer
control center
to check in putty to verify traffic is being directed properly use the commands
tc -s class show dev br-lan
-- detects which qdisc class traffic is flowing through on ingress
tc -s class show dev eth0
-- detects which qdisc class traffic is flowing through on egress
cat /proc/net/nf_conntrack | grep -v "mark=0"
-- displays the marked connections on the network
iptables -t mangle -L FORWARD -v
-- displays the packets marked by dscp

JW0914 · December 18, 2017, 10:49pm

I see no immediate reasoning why it can't be... it's not relying on anything but advanced QOS rules implemented via tc [traffic control) and other basic packages available to all WRT AC Series routers.

mrmidnight · December 19, 2017, 4:50pm

Maybe someone can help me here will working with this. I'm not 100% sure if I need to compile the things in this folder (there is a makefile). or if I just copy the contents of the folder to the router, then perform the above.

This brings me to another issue, either way, I cannot find the scripts that are listed above.

I am running @davidc502's build on a WRT3200acm

If someone is able to help, thanks!

JW0914 · December 20, 2017, 1:41pm

All you need to do is follow exactly what they tell you do, installing LEDE 17.01.4 in lieu of CC 15.05.1, to determine if it will function properly.

mrmidnight · December 20, 2017, 3:47pm

I was wondering if that was the case, I'll take a look at CC today to see if I can find those scripts in there.

JW0914 · December 20, 2017, 3:49pm

DO NOT UTILIZE CC!

I stated to utilize LEDE for a reason... please refer to the WRT AC Series Wiki for explanation.

There is not going to be anything from Killer in the CC firmware image... It's not clear from the documentation you quoted as to where those scripts and files come from, but it's not from OpenWrt or LEDE: "Copy the included scripts onto the router"

mrmidnight · December 20, 2017, 4:26pm

I wasn't going to use CC, I was merely stating that I would inspect a caiman img to see if those scripts that it stated in the readme are there.

I just got done looking at that, and the answer is no, so I am guessing that they had named the scripts wrong in the readme. After looking into the stock FW for the 32x, I may have found where everything is supposed to go and what order to execute the scripts in. I will compile a fresh FW for my router and then place the files where they should go and report back.

JW0914 · December 20, 2017, 4:30pm

The script names in the ReadMe are accurate, as again, there are no Killer related scripts in ANY firmware from OpenWrt/LEDE. Most likely, scripts and files required can either be downloaded from Killer's website or Linksys', and if not readily available, I'd email both to discern where you can download the scripts from.

Again, referring to the ReadMe you quoted, it states: "Copy the included scripts onto the router”
- i.e. these files come from an external source repository, not from OpenWrt/LEDE

mrmidnight · December 20, 2017, 5:13pm

The scripts are on Linksys' GPL page, I have the included scripts, but the scripts that I couldn't find are the scripts that are listed in the readme, which is why I am wondering if they named the wrong scripts, or if they renamed the scripts after writing the readme file, which is possible. The scripts that I did find do have entries which seem to be consistent with the names of the listed scripts. I'll shoot Linksys an email and see what they say. While I know that these qos scripts do nothing for my PCs, they will do something for my Xbox gaming environments, as these scripts have Xbox and PS4 listed in the qos settings all over the place.

--EDIT--

I was not able to find an email address for them, and Linksys stated that they do not provide any technical support for anything on the GPL site, so I posted on their forum, if anyone would like to follow over there the thread that I made is located here Link to Linksys Thread considering KPE

JW0914 · December 20, 2017, 5:39pm

I'd also recommend emailing Killer directly, as these are all Killer customized QOS scripts & settings.

Please keep us updated on your progress, as I believe from the wording in the ReadMe, you should be able to use the Killer Control Center on PCs (unless they built a Control Center interface for OpenWrt) to monitor and tweak settings.

mrmidnight · December 20, 2017, 5:45pm

Killer's Knowledge Base says to contact Linksys about the engine on the router. The same KB entry also says that consoles can't utilize the engine; which I find odd since the scripts directly name the Xbox One, Xbox 360, and the PS4 in their entries.

mrmidnight · December 21, 2017, 9:00pm

So forget getting help from any of them as far as I'm considered. I did get it to work!

So I copied everything over to the router, made everything executable, and restarted the router, then I went into the startup area in LuCI and enabled krouter-scripts, restarted again and everything loaded. The only thing that I have noticed is that if the router gets rebooted, you have to go into LuCI and accept the change of krouter.firewall=include. While for me that is not very tedious, since I usually reboot my router using SSH if I can, for others it may be. The router picked everything up as it should and started the scripts correctly. Results were a drop in ping to the Xbox Live service, and a more stable connection while gaming. As I stated above, apparently this works with both Xbox and PS4 even though Killer's webpage stays that it won't work on consoles, despite consoles being in the scripts.

moeller0 · December 21, 2017, 9:32pm

So could yu post the output of:
tc -d qdisc
tc -s qdisc
please? I wonder what they use under the hood...

Best Regards

mrmidnight · December 21, 2017, 11:13pm

Not a problem, here ya go.

tc -d qdisc

qdisc noqueue 0: dev lo root refcnt 2
qdisc mq 0: dev eth1 root
qdisc fq_codel 0: dev eth1 parent :8 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth1 parent :7 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth1 parent :6 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth1 parent :5 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth1 parent :4 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth1 parent :3 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth1 parent :2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth1 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc mq 0: dev eth0 root
qdisc fq_codel 0: dev eth0 parent :8 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth0 parent :7 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth0 parent :6 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth0 parent :5 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth0 parent :4 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth0 parent :3 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth0 parent :2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth0 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc hfsc 1: dev ifb0 root refcnt 2 default 30
qdisc fq_codel 400: dev ifb0 parent 1:40 limit 800p flows 1024 quantum 300 target 5.0ms interval 100.0ms memory_limit 4Mb
qdisc fq_codel 100: dev ifb0 parent 1:10 limit 800p flows 1024 quantum 300 target 5.0ms interval 100.0ms memory_limit 4Mb
qdisc fq_codel 200: dev ifb0 parent 1:20 limit 800p flows 1024 quantum 300 target 5.0ms interval 100.0ms memory_limit 4Mb
qdisc fq_codel 300: dev ifb0 parent 1:30 limit 800p flows 1024 quantum 300 target 5.0ms interval 100.0ms memory_limit 4Mb
qdisc noqueue 0: dev br-lan root refcnt 2
qdisc noqueue 0: dev eth0.1 root refcnt 2
qdisc hfsc 1: dev eth1.2 root refcnt 2 default 30
qdisc fq_codel 400: dev eth1.2 parent 1:40 limit 800p flows 1024 quantum 300 target 5.0ms interval 100.0ms memory_limit 4Mb
qdisc fq_codel 100: dev eth1.2 parent 1:10 limit 800p flows 1024 quantum 300 target 5.0ms interval 100.0ms memory_limit 4Mb
qdisc fq_codel 200: dev eth1.2 parent 1:20 limit 800p flows 1024 quantum 300 target 5.0ms interval 100.0ms memory_limit 4Mb
qdisc fq_codel 300: dev eth1.2 parent 1:30 limit 800p flows 1024 quantum 300 target 5.0ms interval 100.0ms memory_limit 4Mb
qdisc ingress ffff: dev eth1.2 parent ffff:fff1 ----------------
qdisc mq 0: dev wlan0 root
qdisc fq_codel 0: dev wlan0 parent :4 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev wlan0 parent :3 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev wlan0 parent :2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev wlan0 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc mq 0: dev wlan1 root
qdisc fq_codel 0: dev wlan1 parent :4 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev wlan1 parent :3 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev wlan1 parent :2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev wlan1 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn

tc -s qdisc

qdisc noqueue 0: dev lo root refcnt 2
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
qdisc mq 0: dev eth1 root
 Sent 73652178 bytes 287481 pkt (dropped 0, overlimits 0 requeues 2)
 backlog 0b 0p requeues 2
qdisc fq_codel 0: dev eth1 parent :8 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth1 parent :7 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth1 parent :6 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth1 parent :5 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth1 parent :4 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth1 parent :3 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth1 parent :2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth1 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 73652178 bytes 287481 pkt (dropped 0, overlimits 0 requeues 2)
 backlog 0b 0p requeues 2
  maxpacket 3063 drop_overlimit 0 new_flow_count 37 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc mq 0: dev eth0 root
 Sent 494212021 bytes 470885 pkt (dropped 0, overlimits 0 requeues 3)
 backlog 0b 0p requeues 3
qdisc fq_codel 0: dev eth0 parent :8 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :7 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :6 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :5 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :4 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :3 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 494212021 bytes 470885 pkt (dropped 0, overlimits 0 requeues 3)
 backlog 0b 0p requeues 3
  maxpacket 7570 drop_overlimit 0 new_flow_count 79 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc hfsc 1: dev ifb0 root refcnt 2 default 30
 Sent 659191177 bytes 545760 pkt (dropped 1, overlimits 76493 requeues 0)
 backlog 0b 0p requeues 0
qdisc fq_codel 400: dev ifb0 parent 1:40 limit 800p flows 1024 quantum 300 target 5.0ms interval 100.0ms memory_limit 4Mb
 Sent 111818351 bytes 126268 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 7410 drop_overlimit 0 new_flow_count 7107 ecn_mark 0
  new_flows_len 0 old_flows_len 1
qdisc fq_codel 100: dev ifb0 parent 1:10 limit 800p flows 1024 quantum 300 target 5.0ms interval 100.0ms memory_limit 4Mb
 Sent 961847 bytes 6129 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 427 drop_overlimit 0 new_flow_count 4641 ecn_mark 0
  new_flows_len 1 old_flows_len 19
qdisc fq_codel 200: dev ifb0 parent 1:20 limit 800p flows 1024 quantum 300 target 5.0ms interval 100.0ms memory_limit 4Mb
 Sent 13590 bytes 151 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 90 drop_overlimit 0 new_flow_count 150 ecn_mark 0
  new_flows_len 1 old_flows_len 0
qdisc fq_codel 300: dev ifb0 parent 1:30 limit 800p flows 1024 quantum 300 target 5.0ms interval 100.0ms memory_limit 4Mb
 Sent 546397389 bytes 413212 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 16204 drop_overlimit 0 new_flow_count 23600 ecn_mark 0
  new_flows_len 0 old_flows_len 1
qdisc noqueue 0: dev br-lan root refcnt 2
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
qdisc noqueue 0: dev eth0.1 root refcnt 2
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
qdisc hfsc 1: dev eth1.2 root refcnt 2 default 30
 Sent 72984877 bytes 284363 pkt (dropped 0, overlimits 56970 requeues 0)
 backlog 0b 0p requeues 0
qdisc fq_codel 400: dev eth1.2 parent 1:40 limit 800p flows 1024 quantum 300 target 5.0ms interval 100.0ms memory_limit 4Mb
 Sent 34838735 bytes 133877 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 5718 drop_overlimit 0 new_flow_count 14859 ecn_mark 0
  new_flows_len 0 old_flows_len 1
qdisc fq_codel 100: dev eth1.2 parent 1:10 limit 800p flows 1024 quantum 300 target 5.0ms interval 100.0ms memory_limit 4Mb
 Sent 695754 bytes 7037 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 392 drop_overlimit 0 new_flow_count 5249 ecn_mark 0
  new_flows_len 1 old_flows_len 12
qdisc fq_codel 200: dev eth1.2 parent 1:20 limit 800p flows 1024 quantum 300 target 5.0ms interval 100.0ms memory_limit 4Mb
 Sent 26124 bytes 227 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 168 drop_overlimit 0 new_flow_count 183 ecn_mark 0
  new_flows_len 0 old_flows_len 1
qdisc fq_codel 300: dev eth1.2 parent 1:30 limit 800p flows 1024 quantum 300 target 5.0ms interval 100.0ms memory_limit 4Mb
 Sent 37424264 bytes 143222 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 14280 drop_overlimit 0 new_flow_count 21123 ecn_mark 0
  new_flows_len 0 old_flows_len 1
qdisc ingress ffff: dev eth1.2 parent ffff:fff1 ----------------
 Sent 649839737 bytes 545761 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
qdisc mq 0: dev wlan0 root
 Sent 226958022 bytes 271846 pkt (dropped 1004, overlimits 0 requeues 3)
 backlog 0b 0p requeues 3
qdisc fq_codel 0: dev wlan0 parent :4 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev wlan0 parent :3 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 226924349 bytes 271664 pkt (dropped 1004, overlimits 0 requeues 3)
 backlog 0b 0p requeues 3
  maxpacket 6817 drop_overlimit 0 new_flow_count 302 ecn_mark 0
  new_flows_len 1 old_flows_len 0
qdisc fq_codel 0: dev wlan0 parent :2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev wlan0 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 33673 bytes 182 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc mq 0: dev wlan1 root
 Sent 83872554 bytes 233832 pkt (dropped 7769, overlimits 0 requeues 10)
 backlog 0b 0p requeues 10
qdisc fq_codel 0: dev wlan1 parent :4 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev wlan1 parent :3 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 83853491 bytes 233755 pkt (dropped 7769, overlimits 0 requeues 10)
 backlog 0b 0p requeues 10
  maxpacket 1514 drop_overlimit 2624 new_flow_count 3187 ecn_mark 0 drop_overmemory 2624
  new_flows_len 1 old_flows_len 18
qdisc fq_codel 0: dev wlan1 parent :2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev wlan1 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
 Sent 19063 bytes 77 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 459 drop_overlimit 0 new_flow_count 1 ecn_mark 0
  new_flows_len 0 old_flows_len 0

mrmidnight · December 22, 2017, 5:55am

--edit--

Never mind, had I followed the instructions I posted above it would have worked right lol

hnyman · December 22, 2017, 7:18am

Looks like several "normal" fq_codel qdiscs plus apprently also hfsc (that has caused crashes with some kernel versions). To me it looks like an extended version of SQM simple.qos queing, 8 buckets instead of 3 ? And applied to all interfaces?

moeller0 · December 22, 2017, 8:43am

Looking at the output it seems like hfsc with 4 different priority tiers; honestly at that level all multi-tier shaper set-ups will look similar, its in the yet un-exploreed tc-filter and/or iptables rules where the "magic" most likely hides.
But overall the shaper configuration seems rather bare-bone...

Could you also post the output of:
ip6tables -t mangle -L -v
iptables -t mangle -L -v
which might reveal a bit more* about the iptables tricks played...

*) I say a bit morer as my iptables skills are rusty so this might or might not show the appropriate level of detail...

mrmidnight · December 22, 2017, 1:56pm

Yes I can, give me a bit, I had a separate router issue last night so I'm recompiling with the latest master, and I have KPE in the build as well.

JW0914 · December 22, 2017, 1:56pm

Just an FYI: I'm almost positive the Killer Control Center is needed for one to garnish the full benefit of these SQM rules.

mrmidnight · December 22, 2017, 2:02pm

I don't think so, looking through the executables I cannot find anything that calls to a program outside the router. It does look for and identify different clients so it knows where to forward everything, but other than that, no. I think the Killer Control Center is just a simple way for someone to enable these rules in their router without having to login to their router.