Grouping Users Of A Pipe; A Pipe With Traffic In One Precedence, Grouped Per Ip Address - D-Link NetDefend DFL-210 User Manual

10.1.6. Grouping Users of a Pipe

10.1.6. Grouping Users of a Pipe
10.1.6.1. Overview
If pipes were restricted to the functionality described so far, traffic would be limited without respect
to source or destination. This mode of operation is likely sufficient for managing simple traffic lim-
its and guarantees.
However the ability exists to group traffic within each pipe. This means that traffic will be classified
and grouped with respect to the source or destination of each packet passing through the pipe.
Grouping may be performed on source network, source IP address, source port, destination network,
destination IP address and destination port. In the network grouping cases, the network size may be
specified. The port grouping cases also include the IP address, meaning that port 1024 of computer
A is not the same "group" as port 1024 of computer B.
The benefit of using grouping is that additional bandwidth controls may be applied to each group.
This means that if grouping is performed on, for example, IP address, the firewall can limit and
guarantee bandwidth per IP address communicating through the pipe.
There are precedences in user groups, too. Bandwidth may be limited per precedence as well as for
each group as a whole.
Figure 10.4. A pipe with traffic in one precedence, grouped per IP address.
Bandwidth control first occurs per user and then continues with the pipe as a whole. A pipe with
grouping enabled is illustrated in the drawing below.
10.1.6.2. Applying Per-User Limits and Guarantees
Once the users of a pipe are grouped, you can apply limits and guarantees to each user the same way
you apply them to the pipe as a whole.
To expand on the previous example, we could, for instance, limit how much guaranteed bandwidth
Note
In many cases, this text refers to groups as "users", regardless of the group represent-
ing a physical person, a single connection, or an entire class C network.
219
Chapter 10. Traffic Management