Really? I thought that 56U and 68U were still working properly (at least with 380.59 as you said) so I assumed that's still the case.Traditional QoS is known to be broken on the RT-AC68U, so that could be why.
Last edited:
Really? I thought that 56U and 68U were still working properly (at least with 380.59 as you said) so I assumed that's still the case.Traditional QoS is known to be broken on the RT-AC68U, so that could be why.
Just figured this out while working on something on my fork. At least on the fork, eth0 is used when CTF is inactive....If CTF is enabled, it shows up as VLAN2.
Really? I thought that 56U and 68U were still working properly (at least with 380.59 as you said) so I assumed that's still the case.
Post the result from these commands then, so we can check all potential interfaces:
Code:tc -s class show dev eth0 tc -s class show dev br0 nvram get wan0_ifname nvram get lan_ifname
Do you use any VLAN for your Internet connection?
Any Javascript error in your web browser console?
I ran some tests using dslreports speedtest with traditional QoS enabled: A/A/A (avg. 35ms up) and with QoS disabled: B/C/A (avg. 269ms up) so I'd say that traditional QoS is working on 68U.
It seems as if it's the same "display problem" as with this 56U, maybe the combination of traditional QoS with PPPoE?
Pls, check the attachment:
https://drive.google.com/file/d/0B14-MriqKuXOaV9SOWptVFhwN0E/view?usp=sharing
no VLAN on my internet connection
BTW only commit that was made is 8aeb81c in between the time. As I am coming straight from latest beta. So maybe the problem that upload chart for QOS is not shown lies into here. Just a wild guess...
I know that a speedtest is quite useless to check the classifications but at least it shows that something gets queued and prioritized.
However, if you tell me how to check for proper classification and if I could help you investigate with commands and outputs please tell me (here or with PN) and I will try to support as good as possible.
ps w | grep qosd
Those with QoS stats issues using Adaptive QoS (@matthew_eli and others), please post the output of the following command:
Code:ps w | grep qosd
It should hopefully tell me what WAN interface is used, as I see it's passed as an argument to that daemon. That could be a starting point to see what kind of interfaces everyone is using on their specific setup.
14461 Chriscom 696 S qosd -i /dev/idpfw -f /tmp/bwdpi/qosd.conf -w eth0 -l br0 -u 253 -b
31228 Chriscom 1380 R grep qosd
Those with QoS stats issues using Adaptive QoS (@matthew_eli and others), please post the output of the following command:
Code:ps w | grep qosd
It should hopefully tell me what WAN interface is used, as I see it's passed as an argument to that daemon. That could be a starting point to see what kind of interfaces everyone is using on their specific setup.
2231 admin 696 S qosd -i /dev/idpfw -f /tmp/bwdpi/qosd.conf -w eth0 -l br0 -u 253 -b
No, sorry. That's for use in postconf scripts to delete a line from the router generated conf files.NEW: Added pc_delete() to the helper script (patch by john95287)
Does this mean what I think it does? can we really delete client now by click the x next to offline clients?
1063 admin 700 S qosd -i /dev/idpfw -f /tmp/bwdpi/qosd.conf -w eth0 -l br0 -u 253 -b
4192 admin 1380 D grep qosd
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!