DSL, PPPoE
Running these commands after logging into router via SSH produces no output.
Try this one:
Code:
tc -s class show dev ppp0
DSL, PPPoE
Running these commands after logging into router via SSH produces no output.
tc -s class show dev ppp0
As I am am thinking about it, the decision of which wan interface to use should be a little more complex, these 2 nvram variables should help:
wan0_gw_ifname=ppp0
wan0_pppoe_ifname=ppp0
Those are set in my system as you see.
Already saw it, building a test version already.I just implemented the same way Asus does when it builds up the QoS script, just to be sure that I do get the exact same interface as used when building the QoS rules:
https://github.com/RMerl/asuswrt-merlin/commit/8aeb81cf7d1b2f61d7f6b0e4f8e09bd26af3fb29
Test build flashed, working normally now, I see a pie chart.I just implemented the same way Asus does when it builds up the QoS script, just to be sure that I do get the exact same interface as used when building the QoS rules:
https://github.com/RMerl/asuswrt-merlin/commit/8aeb81cf7d1b2f61d7f6b0e4f8e09bd26af3fb29
My IPv6 HE tunnel works fine here, also tested with a firewall opening to confirm that firewall is also working as intended.
Test build flashed, working normally now, I see a pie chart.
Seems ok to me, all 5 classes show up.Cool. Are all your classes showing correctly?
tc -s class show dev ppp0
class htb 1:10 parent 1:1 leaf 10: prio 1 rate 174Kbit ceil 348Kbit burst 1599b cburst 1599b
Thanks. That confirms what I thought. I patched this issue last night, PPPoE users will now be able to get their QoS statistics to show up properly.
one problem i noticed. Not sure if it is specific for this beta.
The icons to identify the clients used in Show status seems to scale wrong or the wrong icon is chosen.
Wish I could help test but cant afford to at the moment, looks like things are going well, any timeframe on release, are we near do you think ?
Time, if we only had more time... I take advantage of the fact that I have ssh access to my linux box from work and usually build firmwares etc from there, then test them when I go home.The code looks good, however I need to find the time to issue a release. This is something that takes a couple of hours to do, and I have limited time these days.
Time, if we only had more time... I take advantage of the fact that I have ssh access to my linux box from work and usually build firmwares etc from there, then test them when I go home.
Urgh, ok you convinced me! And usually after work most of us don't feel like doing things that look like chores.Building is just a small part of the equation, it takes 1h30 to build all models and it can be done while I do something else. It's going through the latest feedback, finalizing the changelog, preparing the archives, uploading to two different sites, updating the website, writing the release notes, posting the announcements Twitter, SNBForums and the website, and monitoring the early feedback to ensure there's no major issue. It's generally a good 2-4 hours of work (so, basically one evening).
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!