NetLimiter is a software for managing and controlling Internet traffic. After installing this low-volume program, all of the volume and traffic of the Internet is monitored accurately and in the form of regular charts and tables. Using this program, traffic can be displayed in the form of software and Internet connections. The program shows you which program has the most traffic. You can set specific traffic schedules to use only traffic within that range.
In a nutshell, NetLimiter can monitor, manage, limit, and block network connectivity on a system-wide basis or per individual programs. NetLimiter 4’s Control UI (user interface) might be visually daunting to someone who is not especially tech savvy, but in practice, it’s actually a very easy-to-use software appliance.
In the main application pane, the default “Activity” tab displays a list of all running processes that are actively network connected (or able to connect). Their connection rate, process ID and destination IP address are all visible by means of drilling down through cascaded bullet points. On the right, the “Info View” panel expands pertinent details a little further.
Six more tabs are conveniently situated on the primary application panel – these being ‘Filters’, ‘Applications’, ‘Networks’, ‘Rules’, ‘Blocker’ and ‘Priorities’. Each of the tabs grant immediate view of any configured application rule, LAN/WiFi connection, application connection priority, and etcetera, which you’ve configured. I suspect that a typical home user’s monitoring and adjustments will mostly be carried out within the default ‘Activity’ tab. However, if you’re a quasi IT person or a multi-tasking office manager, running NetLimiter 4 in client-server mode, the additional tabs will prove very helpful indeed.
Not only is “NetFilter 4” adept at connection monitoring and bandwidth management, its hosts a handy-dandy firewall apparatus too. To be fair, its ‘Blocker’ isn’t a full-featured, dedicated firewall capable of replacing a specialized network sentry, but it is handy and reliable. As with the other functions of the application, the ‘blocker’ can be configured to handle both incoming and outgoing traffic, over all supported protocols. If you’d prefer to simply block a program or process from making network connections, as opposed to limiting its bandwidth, this is a wonderfully simple and convenient way to do so. Rounding out the feature set is the ability to prioritize a program. The values can be configured to either grant networking preference to an application, or lessen its connectivity importance.
NetLimiter 4’s interface is clean, clear and uncluttered. On my Core i7 7700HQ laptop, both the “NetLimiter” service and also the client are snappy and responsive without any lag or sluggishness. There’s plenty of space between the various elements. For obvious necessity, there’s design-emphasis on real-time, text-based monitoring. The help documentation is hosted online and I haven’t noticed a downloadable PDF link available.
Along the top of the GUI window, following typical file menu suspects, you’ll find a drop-down list where you can select the bandwidth measurement units: bytes, kilobytes, megabytes, and so forth. Alongside are three conveniently located tick boxes where you can enable/disable ‘the Blocker’, ‘the Limiter’ and ‘the Priorities’ functions. The GUI’s closing and minimizing activity is configurable in that it can be hidden or closed to the system tray. Other options, such as the ability to load the client manager (IE. the user interface) at system startup, update checks, and etcetera, can all be found under the “Tools” menu.
While I’ve been bench-testing, (enjoyably I might add) this fine little software gem, I’ve not experienced usage hiccups, performance issues, system-memory leaks or any other problems. The software has functioned flawlessly for me. An additional advantage of “NetFilter 4” is that it can be used in a quasi client-server role. You can designate one of your PCs to be the server or controller (preferably a parent’s PC at home, or office manager/IT person’s PC at work). Upon installing the application on other family (or office) machines, the pseudo server machine can then govern the bandwidth, port blocking or priority of the connected nodes.