when you do QoS do you have by any chance any acceleration enabled...like SFE and the others..
try to turn them off..or disabled...
That seems plausible, and I was kinda expecting to that work,
r52054 - I had never touched the SFE setting before, but I just disabled it as you suggested, setup QoS, and instantly soft-bricked again. Rebooting the router does not help. Only option was to downgrade firmware via recovery as usual.
(If it had worked, I was gonna say, I've been using dd-wrt for years and whenever a certain version soft-bricked the router, it was always fixed in a future release. So this would've been a first, but, not to be.)
Posted: Mon Mar 20, 2023 14:43 Post subject: Re: ASUS RT-AC68U & 2 x Linksys E2000
mwchang wrote:
wabe wrote:
Had issues with this build on Asus RT-AC68U, no wan access after updating. Had to revert to 52020.
Did you wait long enough for the firmware to be upgraded?
Did you turn off then turn on the router after firmware upgrade?
I sure did! Will try again when I have time and do a full reset. Haven't done that in a good while on that particular router. _________________ Netgear R7000 on Build 55109
Asus AC-AC68U rev. C1 (AP) on Build 55109
Asus AC-68U rev. A1 on Build 54604
Asus AC-68U rev. A1 on Build 53339
Joined: 26 Mar 2013 Posts: 1855 Location: Hung Hom, Hong Kong
Posted: Tue Mar 21, 2023 7:49 Post subject: Quality of Service (QoS) in DD-WRT
Alozaros wrote:
when you do QoS do you have by any chance any acceleration enabled...like SFE and the others..
try to turn them off..or disabled...
When I tried `service qos start`, SFE was affected:
Code:
~# service qos start
[sfe] : shortcut forwarding engine successfully started
~# tail /var/log/messages
...
Mar 21 15:41:33 DD-WRT user.info : [sfe] : shortcut forwarding engine successfully started
~#
According to the QoS guide in https://wiki.dd-wrt.com/wiki/index.php/Quality_of_Service ,
there should be svqos and wshaper. I found svqos to be a script as /usr/sbin/svqos,
while service wshaper was missing. I suspect service name "wshaper" might
have become "qos". I dunno for sure as I don't use QoS. The guide might have been too
outdated.
Code:
~# service list | grep -iE 'shape|qos'
qos [start] [stop] [restart] (emulated)
~# which svqos
/usr/sbin/svqos
~# which qos
~# which wshaper
~#
# nvram show | grep -i shape
wshaper_enable=0
wshaper_downlink=0
wshaper_uplink=0
wshaper_nopriohostsrc=
wshaper_nopriohostdst=
wshaper_noprioportsrc=
wshaper_dev=WAN
wshaper_noprioportdst=
~#
~# nvram show | grep -i qos
qos_done=0
svqos_port2bw=FULL
svqos_port4prio=10
svqos_port2prio=10
svqos_port1bw=FULL
qos_type=0
svqos_macs=
svqos_port4bw=FULL
svqos_svcs=
svqos_port3prio=10
svqos_ips=
svqos_port1prio=10
svqos_port3bw=FULL
svqos_aqd=sfq
~#
The script /usr/sbin/svqos calls /usr/sbin/tc, where "tc" means "traffic control". There is nothing about tc command in DD-WRT's wiki:
I suspect you can use your own script calling tc to do QoS, without relying on the WEBUI of DD-WRT. But you might need to mangle with the firewall script.
It also seems that tc might just be a command of Busybox? If so, you might wonder about the version of Busybox in use...
BTW, I wonder: could it be interface naming issue again? As some routers don't have wl0 but eth0. There is also no interface named "wan" as indicated by variable "wshaper_dev" above! Also you need to take into account br0, vlan1 and vlan2.
Anyway, I think volunteers might be needed to really test QoS in various routers. Relevant documentation needs an update, too. Well... _________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!