Like every other website on the planet, SmallNetBuilder uses cookies. Our cookies track login status, but we only allow admins to log in anyway, so those don't apply to you. Any other cookies you pick up during your visit come from advertisers, which we don't control.
If you continue to use the site, you agree to tolerate our use of cookies. Thank you!

Router Charts

Click for Router Charts

Router Ranker

Click for Router Ranker

NAS Charts

Click for NAS Charts

NAS Ranker

Click for NAS Ranker

More Tools

Click for More Tools

LAN & WAN Reviews

QoS / Bandwidth Control

Regular SmallNetBuilder readers know that I think that Bandwidth control is a very desirable feature to have on SOHO routers. Implemented correctly, it can keep kids (or employees) from sucking up the bulk of your bandwidth for music and video downloads, or any other undesirable activity. So I was looking forward to seeing how this feature checked out in the 9000VPN.

But my enthusiasm quickly cooled once I realized that the 9000VPN's QoS feature allows upstream bandwidth only to be capped to programmable values. This means that it will help if someone on your LAN is running a server that uses up a lot of bandwidth, but it will have no effect for over-active downloaders.

At any rate, bandwidth can be limited by IP address (Figure 8) or Application / Port (Figure 9).

OvisLink MU-9000VPN QoS by IP

Figure 8: QoS by IP

This implementation is more flexible than the physical port method used by the Draytek Vigor 2900G [reviewed here], but I feel the upstream-only control seriously limits its usefulness.

OvisLink MU-9000VPN QoS by Application

Figure 9: QoS by Application

I used Qcheck to run a simple throughput test using the IP Grouping settings shown in Figure 8. I confirmed that the bandwidth cap was in effect for the LAN to WAN direction only, and found that a setting of 1000kbps yielded a measured throughput of about 440kbps, less than half the programmed value.

I also was confused by the Priority selector in the IP Grouping section, since the High, Medium and Low Priority settings are used for Application QoS. But OvisLink assured me that the IP Grouping setting would take priority over the Application level setting. If that is the case, I think OvisLink should remove the Priority selectors from the IP Grouping section.

More LAN & WAN

Wi-Fi System Tools
Check out our Wi-Fi System Charts, Ranker and Finder!

Support Us!

If you like what we do and want to thank us, just buy something on Amazon. We'll get a small commission on anything you buy. Thanks!

Over In The Forums

Howdy all,I am writing this in hopes of getting some advice from people who are more experienced with NAS devices than myself. I currently use Onedriv...
Hi,RT-AC86C 384.12_alpha1-g40c9e42009Apologies if this has been covered, I looked but could not find a specific response.I am using Smart Connect on t...
After 4 days, Port Forwarding rule disappears from router. It can be easily reentered and will persist for approximately the same period, before disap...
I live in a complex that has great broadband. I have been annoyed with my Linksys's inability to keep things running, and since my alexa stuff does no...
Greetings,Just setup a R6700V3 to replace an 8 year old D-Link 655. Roku Premiere was killing the 655 every 4-24 hours.My Windows 10 PC connects via e...

Don't Miss These

  • 1
  • 2
  • 3