- Contact Us
This section outlines the various aspects for deploying Bandwidth Controller on your network.
The product consists of 3 components that work together to provide a total bandwidth management solution.
The core part of the product is the Kernel Component. It operates at Layer 3 in the network stack and provides high speed traffic shaping services. The kernel component runs as a network driver which means it is active at all times.
The second component is the Service. It controls the kernel component and provides functionality such as scheduling, rule storage and logging. The service runs at Windows startup but may be started and stopped at any time by the administrator.
The final component is the Manager Application. The manager provides a user interface that allows you to configure the bandwidth management. It also has a bandwidth monitor that shows each traffic stream running through the system.
The manager application also provides remote access to the service.
Bandwidth Controller Standard Edition can operate in two different modes: Gateway Mode or Distributed Mode.
Gateway mode is the standard method used for bandwidth management. In this mode, all traffic is fed through a central server. The server provides bandwidth shaping and monitoring for the entire network. The product should be installed on a computer that sits between the internet connection and the local network. Typically a server between the modem and the router.
Distributed mode allows the product to function without the need for a server. It is a fully client-side solution where the product is installed onto each computer on the local network. The product then distributes bandwidth evenly between the computers.
Note that distributed mode supports a maximum of 5 computers.
For both installation types, only the Server Package needs to be installed. The Client Package only needs to be installed onto the computer that will provide remote access to the server. That is because the client package contains only the manager application and help files, whereas the server package contains the actual bandwidth shaper.
The product uses ports for communication that need to be opened on the firewall to allow remote management to function.
In gateway mode the server requires port 24824 TCP to be opened.
In distributed mode each computer needs the following ports to be opened: 24824 TCP (remote management), 24825 TCP (peer communication) and 24826 UDP (peer discovery).
When the server package installs the kernel component there are several messages displayed by the operating system regarding driver signing. The messages are there to warn the user that a network driver is being installed and that care should be taken to ensure the software is well tested.
Bandwidth Controller has been extensively tested for over 5 years and is designed to provide a secure, stable and robust bandwidth management platform. Even so, the driver signing messages prevent the product from being installed without user intervention as each message must be manually clicked by the user.
If quiet / automated installation is required, the driver signing messages can be turned off. To do this, right click My Computer, select Properties, click the Hardware tab, click the Driver Signing button then select Ignore. This will prevent the driver signing message from appearing on that machine.
To install the product without the need for user intervention, run the installer with the /automatic switch from the command line.
For example: BandwidthControllerStandardSetup.exe /automatic
This will install both the client and server packages into the program files folder and create the necessary shortcuts in the start menu.
After setup is complete, run the manager application and enter the details of the computer in the Network Adapter Wizard.
Note: It is important to configure the internet speed and network adapters correctly, otherwise the product may not function.
Set the line speed of your internet connection in kilobits per second. These values are used by the server to determine the correct traffic flows for prioritization and speed limiting.
Note: This step should be done for each computer when running in distributed mode.