D-Link DFL-2500 - Manual (Page 269)

Figure 10.1. Pipe rule set to Pipe Packet Flow
Where one pipe is specified in a list then that is the pipe whose characteristics will be applied to the
traffic. If a series of pipes are specified then these will form a Chain of pipes through which traffic
will pass. A chain can be made up of at most 8 pipes.
If no pipe is specified in a list then traffic that matches the rule will not flow through any pipe but it
will also mean that the traffic will not be subject to any other pipe rules found later in the rule set.
10.1.3. Simple Bandwidth Limiting
The simplest use of pipes is for bandwidth limiting. This is also a scenario that doesn't require much
planning. The example that follows applies a bandwidth limit to inbound traffic only. This is the
direction most likely to cause problems for Internet connections.
Example 10.1. Applying a Simple Bandwidth Limit
Begin with creating a simple pipe that limits all traffic that gets passed through it to 2 megabits per second,
regardless of what traffic it is.
CLI
gw-world:/> add Pipe std-in LimitKbpsTotal=2000
Web Interface
1. Go to Traffic Management > Traffic Shaping > Pipes > Add > Pipe
2. Specify a suitable name for the pipe, for instance std-in
3. Enter 2000 in Total textbox
4. Click OK
Traffic needs to be passed through the pipe and this is done by using the pipe in a Pipe Rule.
We will use the above pipe to limit inbound traffic. This limit will apply to the the actual data packets, and not the
connections. In traffic shaping we're interested in the direction that data is being shuffled, not which computer
initiated the connection.
Create a simple rule that allows everything from the inside, going out. We add the pipe that we created to the
return chain. This means that the packets travelling in the return direction of this connection (outside-in) should
pass through the std-in pipe.
10.1.3. Simple Bandwidth Limiting Chapter 10. Traffic Management
269