M
M@rco
Guest
Finally gotten around to upload 384.4_2 (coming from 384.3) onto my RT-AC68U.
First try gave all sorts of USB errors (on a new thumb drive), but after repartitioning it on the router itself, things got better on the second try. Started completely fresh, power cycle included. Now it runs smoothly, so apparently the USB drive gave issues I never experienced before after following @skeal 's steps. However, QoS still doesn't work for me (it stopped working when I updated to the now obsolete 382 branch and hasn't worked since). QoS is switched on, manual bandwidth settings (360/36 - < 90% of actual available bandwidth), fq_codel, streaming media profile. The bandwidth gauges on the QoS Bandwith Monitor page work, however QoS statistics and Web History remain empty. Tried toggling, restarting, waited several minutes but even after a nights sleep, there's no evidence of QoS actually working.
I think it's a shame that. despite @RMerlin's continuous (and much appreciated) efforts, issues like these can't be properly debugged and resolved as it's apparently all closed source now, where the issues are. I'm not a novice user, tried even on a completely virgin install, with no other settings configured then WPA and administrator credentials, but QoS just doesn't work anymore for me, even though it does for several other RT-AC68U users (which annoys me beyond comprehension).
It's moments like these I'm considering whether I should downgrade (again) to the 380 branch when everything (and I truly mean everything) worked fine, and patiently wait for 380.70 stable but my biggest fear is that scripts like AB-Solution by @thelonelycoder, Skynet by @Adamm and dnscrypt installer by @bigeyes0x0 will at some point no longer be supported on builds in the 380 branch. These scripts have become so crucial to me, that I fear that at some point I'll have no other choice then to follow the majority running the 384(+) branch, if I want to keep using the scripts mentioned before, but can completely forget about QoS, which is definitely a huge loss of functionality for me. To me personally, I feel the 382 branch and later, despite the new developments, and having several unsolvable issues, in no way justify the fact that they (Asus) have left Eric with his hands bound tightly because of the increasing amount of closed source binaries, which is a shame as Asus probably would have done a much better job at hiring him, rewarding him for his incredible work and make him lead developer on Asuswrt... It probably sounds somewhat dramatic but Asus' recent decisions seem to announce the end of an era, which makes me sad.
Having said that: my QoS still doesn't work. Sigh. So it's probably back to 380.6x (again), once I can work up the courage to reconfigure it again.
First try gave all sorts of USB errors (on a new thumb drive), but after repartitioning it on the router itself, things got better on the second try. Started completely fresh, power cycle included. Now it runs smoothly, so apparently the USB drive gave issues I never experienced before after following @skeal 's steps. However, QoS still doesn't work for me (it stopped working when I updated to the now obsolete 382 branch and hasn't worked since). QoS is switched on, manual bandwidth settings (360/36 - < 90% of actual available bandwidth), fq_codel, streaming media profile. The bandwidth gauges on the QoS Bandwith Monitor page work, however QoS statistics and Web History remain empty. Tried toggling, restarting, waited several minutes but even after a nights sleep, there's no evidence of QoS actually working.
I think it's a shame that. despite @RMerlin's continuous (and much appreciated) efforts, issues like these can't be properly debugged and resolved as it's apparently all closed source now, where the issues are. I'm not a novice user, tried even on a completely virgin install, with no other settings configured then WPA and administrator credentials, but QoS just doesn't work anymore for me, even though it does for several other RT-AC68U users (which annoys me beyond comprehension).
It's moments like these I'm considering whether I should downgrade (again) to the 380 branch when everything (and I truly mean everything) worked fine, and patiently wait for 380.70 stable but my biggest fear is that scripts like AB-Solution by @thelonelycoder, Skynet by @Adamm and dnscrypt installer by @bigeyes0x0 will at some point no longer be supported on builds in the 380 branch. These scripts have become so crucial to me, that I fear that at some point I'll have no other choice then to follow the majority running the 384(+) branch, if I want to keep using the scripts mentioned before, but can completely forget about QoS, which is definitely a huge loss of functionality for me. To me personally, I feel the 382 branch and later, despite the new developments, and having several unsolvable issues, in no way justify the fact that they (Asus) have left Eric with his hands bound tightly because of the increasing amount of closed source binaries, which is a shame as Asus probably would have done a much better job at hiring him, rewarding him for his incredible work and make him lead developer on Asuswrt... It probably sounds somewhat dramatic but Asus' recent decisions seem to announce the end of an era, which makes me sad.
Having said that: my QoS still doesn't work. Sigh. So it's probably back to 380.6x (again), once I can work up the courage to reconfigure it again.
