!!..PD..!!
Occasional Visitor
Hello, It has been obsrved that the CAKE-QoS is not working on the Asus RT-AX58U_v2. Also, in the Hardware Acceleration, only Flow Cache gets Disabled and "ARCHER" stays ON when CAKE is turned ON.
This issue was there in the latest stable build 3004.388.9_2-gnuton2 and is being carried forward to the alpha build 3004.388.10_0-gnuton0_alpha3.
Right now I am on the alpha 3 build and have already mentioned the same on the feedback but I'd like some help on finding out where the issue lies in order to get this fixed.
I did find an existing post on this forum through which I reached gnuton's github solved issues page: https://github.com/gnuton/asuswrt-merlin.ng/issues/615
I ran some tests but It is not something which I can understand by troubleshooting so I am sharing the outputs here which were asked of OP from the solved issue#615 and I am hoping you will be able to point me in the right direction.
In the above code, do /dev/null silencers mean that CAKE has been removed in the recent firmwares?
At the end of issue#615, the problem appeared to be RT-AX58U V2 requiring RTCONFIG_HND_ROUTER_AX_6756 which I believe is the CPU of this model but i am not sure how to verify if this is the same issue which has reappeared or something else has gone wrong.
Your time and insights are highly appreciated.
This issue was there in the latest stable build 3004.388.9_2-gnuton2 and is being carried forward to the alpha build 3004.388.10_0-gnuton0_alpha3.
Right now I am on the alpha 3 build and have already mentioned the same on the feedback but I'd like some help on finding out where the issue lies in order to get this fixed.
I did find an existing post on this forum through which I reached gnuton's github solved issues page: https://github.com/gnuton/asuswrt-merlin.ng/issues/615
I ran some tests but It is not something which I can understand by troubleshooting so I am sharing the outputs here which were asked of OP from the solved issue#615 and I am hoping you will be able to point me in the right direction.
Code:
/tmp/home/root# cat /tmp/qos
#!/bin/sh
source /etc/cake-qos.conf
case "$1" in
start)
# Upload
tc qdisc add dev $ULIF root cake $ULPRIOQUEUE $ULBW $OVERHEAD $FRAMING $ULOPTIONS 2>/dev/null
# Download
ip link add name $MIF type ifb 2>/dev/null
tc qdisc add dev $DLIF handle ffff: ingress 2>/dev/null
tc qdisc add dev $MIF root cake $DLPRIOQUEUE $DLBW $OVERHEAD $FRAMING $DLOPTIONS 2>/dev/null
ip link set $MIF up 2>/dev/null
tc filter add dev $DLIF parent ffff: prio 10 matchall action mirred egress redirect dev $MIF 2>/dev/null
;;
stop)
tc qdisc del dev $ULIF root 2>/dev/null
tc qdisc del dev $DLIF ingress 2>/dev/null
tc qdisc del dev $MIF root 2>/dev/null
ip link set $MIF down 2>/dev/null
ip link del dev $MIF 2>/dev/null
;;
*)
esacIn the above code, do /dev/null silencers mean that CAKE has been removed in the recent firmwares?
Code:
/tmp/home/root# sh -x /tmp/qos stop
+ source /etc/cake-qos.conf
+ ULIF=ppp0
+ DLIF=ppp0
+ MIF=ifb4ppp0
+ ULBW=bandwidth 102400kbit
+ DLBW=bandwidth 102400kbit
+ OVERHEAD=overhead 42 mpu 84
+ FRAMING=
+ ULPRIOQUEUE=diffserv3
+ DLPRIOQUEUE=besteffort
+ ULOPTIONS=nat dual-srchost
+ DLOPTIONS=nat wash dual-dsthost ingress
+ tc qdisc del dev ppp0 root
+ tc qdisc del dev ppp0 ingress
+ tc qdisc del dev ifb4ppp0 root
+ ip link set ifb4ppp0 down
+ ip link del dev ifb4ppp0
Code:
/tmp/home/root# sh -x /tmp/qos start
+ source /etc/cake-qos.conf
+ ULIF=ppp0
+ DLIF=ppp0
+ MIF=ifb4ppp0
+ ULBW=bandwidth 102400kbit
+ DLBW=bandwidth 102400kbit
+ OVERHEAD=overhead 42 mpu 84
+ FRAMING=
+ ULPRIOQUEUE=diffserv3
+ DLPRIOQUEUE=besteffort
+ ULOPTIONS=nat dual-srchost
+ DLOPTIONS=nat wash dual-dsthost ingress
+ tc qdisc add dev ppp0 root cake diffserv3 bandwidth 102400kbit overhead 42 mpu 84 nat dual-srchost
+ ip link add name ifb4ppp0 type ifb
+ tc qdisc add dev ppp0 handle ffff: ingress
+ tc qdisc add dev ifb4ppp0 root cake besteffort bandwidth 102400kbit overhead 42 mpu 84 nat wash dual-dsthost ingress
+ ip link set ifb4ppp0 up
+ tc filter add dev ppp0 parent ffff: prio 10 matchall action mirred egress redirect dev ifb4ppp0
Code:
/tmp/home/root# tc qdisc
qdisc noqueue 0: dev lo root refcnt 2
qdisc noqueue 0: dev archer root refcnt 2
qdisc pfifo_fast 0: dev eth0 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc pfifo_fast 0: dev eth1 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc pfifo_fast 0: dev spu_us_dummy root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc pfifo_fast 0: dev spu_ds_dummy root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc pfifo_fast 0: dev eth2 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc pfifo_fast 0: dev eth3 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc noqueue 0: dev br0 root refcnt 2
qdisc pfifo_fast 0: dev wl0.3 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc pfifo_fast 0: dev wl1.3 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc pfifo_fast 0: dev ppp0 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc ingress ffff: dev ppp0 parent ffff:fff1 ----------------
qdisc noqueue 0: dev wgs1 root refcnt 2
qdisc pfifo_fast 0: dev ifb4ppp0 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1At the end of issue#615, the problem appeared to be RT-AX58U V2 requiring RTCONFIG_HND_ROUTER_AX_6756 which I believe is the CPU of this model but i am not sure how to verify if this is the same issue which has reappeared or something else has gone wrong.
Your time and insights are highly appreciated.
Attachments
Last edited:
