D-Link NetDefendOS, Руководство пользователя

Страница: 794 / 912

Figure 10.7. A Basic Traffic Shaping Scenario
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 Def Prec Max Prec Grouping Net size Pipe limit
in-pipe 0 0 7 PerDestIP 24 1000 Kbps
out-pipe 0 0 7 PerSrcIP 24 1000 Kbps
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
Name Forward
Pipes Return
Pipes Source
Interface Source
Network Destination
Interface Destination
Network Selected
Service
all_1mbps out-pipe in-pipe lan lannet wan all-nets all_services
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:
Chapter 10: Traffic Management
794