A peek under the hood

[RMerlin]

Nice ! Is this the only improvement your releasing with the next update or have you been tinkering with anything else ? Just curious.

I don't have anything else planned or under way at the moment. Did some research/experimentation with another idea that had been on my list for a long time, but decided to shelve it for now following those initial results.

I'm waiting for the GPL 382 codebase to drop. I don't want to make too many changes beyond that coming merge, as I expect it will be a difficult merge, and will most likely involve regressions and not be compatible with all the current router models.

 

[Kim Puleston]

I don't have anything else planned or under way at the moment. Did some research/experimentation with another idea that had been on my list for a long time, but decided to shelve it for now following those initial results.

I'm waiting for the GPL 382 codebase to drop. I don't want to make too many changes beyond that coming merge, as I expect it will be a difficult merge, and will most likely involve regressions and not be compatible with all the current router models.

Yeah that is fair enough, hopefully the new code wont be too much of a pain to work with. I look forward to your release of this latest firmware with the QOS update though

 

[RMerlin]

I can now tell for certain that Adaptive QoS is properly classifying most (but not all) torrent traffic under "File Transferring", as I'm seeing it happen on the new stats page

I look forward to your release of this latest firmware with the QOS update though

I will probably post some preview alpha builds in the future like I did with the past few release cycles.

 

[ChriscomIT]

I will probably post some preview alpha builds in the future like I did with the past few release cycles.

Great to hear, cant wait to get my hands on it. Looks very promising!

 

[BMWDude49120]

Looking forward to the new build and QOS charting! Very nice, Merlin!

 

[RMerlin]

The addition of this Chart.js module does open the door for more graphing stuff, like this:

 

[Kim Puleston]

The addition of this Chart.js module does open the door for more graphing stuff, like this:

View attachment 7487

Oh nice! Something like that would make it so easy to see your average usage which would be great for those on limited broadband packages it would at least give them information whether or not they need to upgrade to avoid penalties or downgrade and save some cash...just a scenario.

Is this being included in your release?

 

[RMerlin]

Oh nice! Something like that would make it so easy to see your average usage which would be great for those on limited broadband packages it would at least give them information whether or not they need to upgrade to avoid penalties or downgrade and save some cash...just a scenario.

Is this being included in your release?

It will be in the next release, unless there's any unforeseen issue.

 

[cybrnook]

Guess I will necro bump this thread as I think this is where this belongs. But running your latest @RMerlin on an RT-AC3100. Uptime is over 11 days, and with NAT acceleration disabled, this is how traffic has been categorized (not sure it's really being properly categorized):

 

[paulbates]

Hi cybrnook
I have a 3100 and continue to have nat acc on. I also customized my traffic priority. It's worked for the last 2 Merlin versions I've used on this router. FYI
Paul


Sent from my iPhone using Tapatalk

 

[cybrnook]

What qos settings are you using? I have adaptive with manually inputted bandwidth limits. This keeps my buffer bloat at bay. This was the main reason I noticed I had to disable NAT. When NAT was on, I would score a D/F everytime. Disabling it, while keeping the qos options the same, I am at an A/A+.

Nothing special I am doing.......

 

[paulbates]

I think that's it. I forgot that I tried manual bandwidth limits for a short time and losing the qos stats was one of the side effects. I went back to adaptive and prioritizing the "app" traffic types: web, ftp....

Paul


Sent from my iPhone using Tapatalk

 

[cybrnook]

So the difference you think we are seeing is the fact that on the QoS page, I am using "Adaptive" QoS type with "Manual" for my bandwidth limits?

I assume you are using "Adaptive" for your QoS type with also "Automatic" for your Bandwidth limits?

Also, do you have App Monitoring enabled?

 

[paulbates]

So the difference you think we are seeing is the fact that on the QoS page, I am using "Adaptive" QoS type with "Manual" for my bandwidth limits?

I assume you are using "Adaptive" for your QoS type with also "Automatic" for your Bandwidth limits?

Also, do you have App Monitoring enabled?

I use adaptive and I also arrange the priority of my LAN clients in addition to traffic priority. Not at home this week so can't see the page currently

Paul


Sent from my iPhone using Tapatalk

 

[cybrnook]

I don't see how arranging the priority of protocols on the QoS page would affect the packets for the protocol types being flagged in the QoS Stats graph? I don't mean that in a negative way towards you at all, I just really don't see how me changing the priorities would affect the tagging. Would just order them differently, while all traffic still gets lumped into default, no?

 

[paulbates]

I don't see how arranging the priority of protocols on the QoS page would affect the packets for the protocol types being flagged in the QoS Stats graph? I don't mean that in a negative way towards you at all, I just really don't see how me changing the priorities would affect the tagging. Would just order them differently, while all traffic still gets lumped into default, no?

I don't either, but this wasn't figured out and it's something I did with qos



Sent from my iPhone using Tapatalk

 

[paulbates]

I didn't answer the app monitoring. I used it very early on but not for a number of months.


Sent from my iPhone using Tapatalk

 

[cybrnook]

I give up..... just disabled QoS.

If I enable NAT accel again, reboot. Then go back to the QoS Statics graphs, they work for a short time (seemingly), then start lumping all into default again. As well, with NAT accel enabled again, buffer bloat is back.....