D-Link DFL-1660 User Manual page 403

Network security firewall
Hide thumbs Also See for DFL-1660:
Table of Contents

Advertisement

10.1.12. More Pipe Examples
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
in-pipe
out-pipe
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
all_1mbps
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.
Lets assume we have a symmetric 2/2 Mbps link to the Internet. We will allocate descending
priorities and traffic requirements to the following users:
Priority 6 - VoIP (500 kpbs)
Priority 4 - Citrix (250 kpbs)
Priority 2 - Other traffic (1000 kpbs)
Min Prec
Def Prec
0
0
0
0
Forward
Return
Pipes
Pipes
out-pipe
in-pipe
Max Prec
Grouping
7
PerDestIP
7
PerSrcIP
Source
Source
Interface
Network
lan
lannet
403
Chapter 10. Traffic Management
Net size
Pipe limit
24
1000kb
24
1000kb
Destination
Destination
Interface
Network
wan
all-nets
Service
all

Advertisement

Table of Contents
loading

Table of Contents