Because Bandwidth Controller runs on a computer between the clients and the internet, it has access to all traffic streams being used by the entire network. To effectively control bandwidth usage you must first consider the different types of traffic that need limiting or prioritization.
One way of doing this is by using the built-in traffic monitor. It will allow you to see the different traffic types being used on the network. Rules can be created based on the users and services you see being used, and then adjusted in real time while still viewing the network usage.
Select the network adapter that the traffic must travel through.
In most cases this setting is has no effect, because the product is installed on the internet gateway computer with the traffic passing through both adapters. For that type of network layout, a rule will function the same regardless of the adapter that is chosen.
Select the direction of the traffic to filter. Upload is all data that travels from the local network to the internet, and download is for data received from the net.
Note that TCP downloads use a small part of the upload stream for connection information such as acknowedgment packets. If you limit or block one direction too severely you may consequently limit the other direction. See the Prioritize Acknowledgement Packets switch on the Advanced Processing window for a way to overcome this issue.
Choose between the following network protocols:
- Any: Filters all network traffic regardless of protocol.
- IP: Filters only IP traffic. This includes protocols such as TCP and UDP that are layered on top of IP. If you wish to filter a specific port or internet service, TCP or UDP must be chosen instead of IP, as ports are only applicable to those protocols.
- TCP: This is the most often used protocol for internet applications. We recommend you use this or IP when in doubt.
- UDP: Used for games, VoIP and other types of applications that can tolerate information loss in transit.
- ICMP: Filters only ICMP traffic which includes the ping and traceroute applications.
- Other: Filters all traffic that does not belong to one of the 4 protocols above.
The local endpoint specifies the user or computer you wish to control within your organization. You can control users by computer name / domain name, IP address, MAC address or even a group of addresses.
Domain names are recommended over IP addresses because IP addresses may change periodically on some networks (such as the built-in Windows Internet Connection Sharing).
Most TCP or UDP internet services are effectively designed with a non-changing remote port, and a randomly generated local port. For these protocols we recommend leaving the local port set to 'Any', and entering the internet service's port in the remote endpoint (see below).
The remote endpoint specifies the remote server (and optionally a port / service number) to control. As with local users, you can control remote servers by domain name, IP address, MAC address and address group.
Even though MAC addresses are allowed, they are not recommended as the underlying protocols do not always transmit MAC addresses the entire way. The effect of this is packets coming from the internet are stamped with the MAC address of the router at the very edge of the network. The remote MAC address field is really only used for LAN to LAN traffic shaping.
Most internet services are defined by their server's port number. For example HTTP is port 80 and email uses ports 25 and 110. By entering the appropriate port number here, you can capture a single application's traffic rather than all streams.