Posted: Fri Mar 13, 2015 12:41 Post subject: QoS: Service-Priority=Port(-Range)
At the QoS-settings, there're selectable services, but they're listed with [0 ~ 0]. Are these Layer 7 filters or is it the same as definig ports for the services?
Last edited by mittelhessen on Fri Mar 20, 2015 9:02; edited 1 time in total
This means, that l7-filtering will be more reliable (but perhaps use a little bit more cpu-power)? Are there any disadvantages for using these predefined l7-filters instead of self-defining ports?
Where can i see the kernel of the running dd-wrt version?
I know that lots of people says that QoS is CPU intensive but I didn't had such expirience... I always get 0.05, 0.00 0.00 when torrenting at the same time watching youtube etc... But VPN and VAPs make my router CPU go higher... And I have very cheap routers...
Quote:
nDPI is a ntop-maintained superset of the popular OpenDPI library. Released under the LGPL license, its goal is to extend the original library by adding new protocols that are otherwise available only on the paid version of OpenDPI. In addition to Unix platforms, we also support Windows, in order to provide you a cross-platform DPI experience. Furthermore, we have modified nDPI do be more suitable for traffic monitoring applications, by disabling specific features that slow down the DPI engine while being them un-necessary for network traffic monitoring.
nDPI is used by both ntop and nProbe for adding application-layer detection of protocols, regardless of the port being used. This means that it is possible to both detect known protocols on non-standard ports (e.g. detect http non ports other than 80), and also the opposite (e.g. detect Skype traffic on port 80). This is because nowadays the concept of port=application no longer holds.
I've already had a look at the Sys-Info tab but i can't see there the kernel-version anywhere! :-/
Mile-Lile wrote:
I know that lots of people says that QoS is CPU intensive but I didn't had such expirience...
I'm running qos at the very old (but good) WRT54GL which only has a 200 mhz cpu. I overclocked it to 250 mhz, which runs very reliable. But i think it can't compete with some newer models which have a much more modern cpu-architecture, more RAM and frequencies beyond 400 mhz.
Joined: 24 Feb 2013 Posts: 1634 Location: Belgrade
Posted: Mon Mar 23, 2015 10:56 Post subject:
Like everythig in ddwrt, it is working for someone and for someone not...
I just checked it, it is working for me but I don't have fq_codel choice etc.
I decreased upload limit to 300 and did speedtest and it limits upload limit with ACK checked... Maybe different kernels or iptables or whatsoever?
I think WRT54GL (r14929) uses kernel 2.6, am a right? So this means, there're no nDPI-filters but only old (and outdated) l7-filters. When i have a look at your linked pdf, this doesn't seem to work very reliable.
So would it be more reliable to define the ports for the services or would it be possible to combine(!) the predefines l7-filters with self-defined ports?
