A Basic Traffic Shaping Scenario - D-Link NetDefendOS User Manual

The reason for using 2 different pipes in this case, is that these are easier to match to the physical
link capacity. This is especially true with asynchronous links such as ADSL.
First, two pipes called in-pipe and out-pipe need to be created with the following parameters:
Pipe Name Min Prec
in-pipe 0
out-pipe 0
Dynamic Balancing should be enabled for both pipes. Instead of PerDestIP and PerSrcIP we
could have used PerDestNet and PerSrcNet if there were several networks on the inside.
The next step is to create the following Pipe Rule which will force traffic to flow through the
pipes.
Rule Forward
Name Pipes
all_1mbps out-pipe
The rule will force all traffic to the default precedence level and the pipes will limit total traffic to
their 1 Mbps limit. Having Dynamic Balancing enabled on the pipes means that all users will be
allocated a fair share of this capacity.
Using Several Precedences
We now extend the above example by allocating priorities to different kinds of traffic accessing
the Internet from a headquarters office.
Assume there is a symmetric 2/2 Mbps link to the Internet. Descending priorities and traffic
requirements will be allocated to the following users:
Figure 10.7. A Basic Traffic Shaping Scenario
Def Prec Max Prec
0 7
0 7
Return Source
Pipes Interface
in-pipe lan
794
Chapter 10: Traffic Management
Grouping Net size
PerDestIP 24
PerSrcIP 24
Source Destination
Network Interface
lannet wan
Pipe limit
1000 Kbps
1000 Kbps
Destination Selected
Network Service
all-nets all_services