attempting to flow is 4 Mbps. Since the pipe limit is 2 Mbps, the actual flow will be close to 1 Mbps
in each direction.
Raising the total pipe limit to 4 Mbps will not solve the problem since the single pipe will not know
that 2 Mbps of inbound and 2 Mbps of outbound are the intended limits. The result might be 3 Mbps
outbound and 1 Mbps inbound since this also adds up to 4 Mbps.
Using Two Separate Pipes Instead
The recommended way to control bandwidth in both directions is to use two separate pipes, one for
inbound and one for outbound traffic. In the scenario under discussion each pipe would have a 2
Mbps limit to achieve the desired result. The following example goes through the setup for this.
Example 10.2. Limiting Bandwidth in Both Directions
Create a second pipe for outbound traffic:
Command-Line Interface
gw-world:/> add Pipe std-out LimitKbpsTotal=2000
Web Interface
1.
Go to Traffic Management > Traffic Shaping > Pipes > Add > Pipe
2.
Specify a name for the pipe, for example std-out
3.
Enter 2000 in Total textbox
4.
Click OK
After creating a pipe for outbound bandwidth control, add it to the forward pipe chain of the rule created in the
previous example:
Command-Line Interface
gw-world:/> set PipeRule Outbound ForwardChain=std-out
Web Interface
1.
Go to Traffic Management > Traffic Shaping > Pipe Rules
2.
Right-click on the pipe rule that was created in the previous example and choose Edit
3.
Under the Traffic Shaping tab, select std-out in the Forward Chain list
4.
Click OK
This results in all outbound connections being limited to 2 Mbps in each direction.
10.1.5. Creating Differentiated Limits Using Chains
In the previous examples a static traffic limit for all outbound connections was applied. What if the
aim is to limit web surfing more than other traffic? Assume that the total bandwidth limit is 250
kbps and 125 kbps of that is to be allocated to web surfing inbound traffic.
The Incorrect Solution
Two "surfing" pipes for inbound and outbound traffic could be set up. However, it is not usually
required to limit outbound traffic since most web surfing usually consists of short outbound server
10.1.5. Creating Differentiated Limits
Using Chains
Chapter 10. Traffic Management
456
Summary of Contents for DFL-1600 - Security Appliance
Page 27: ...1 3 NetDefendOS State Engine Packet Flow Chapter 1 NetDefendOS Overview 27 ...
Page 79: ...2 7 3 Restore to Factory Defaults Chapter 2 Management and Maintenance 79 ...
Page 146: ...3 9 DNS Chapter 3 Fundamentals 146 ...
Page 227: ...4 7 5 Advanced Settings for Transparent Mode Chapter 4 Routing 227 ...
Page 241: ...5 4 IP Pools Chapter 5 DHCP Services 241 ...
Page 339: ...6 7 Blacklisting Hosts and Networks Chapter 6 Security Mechanisms 339 ...
Page 360: ...7 4 7 SAT and FwdFast Rules Chapter 7 Address Translation 360 ...
Page 382: ...8 3 Customizing HTML Pages Chapter 8 User Authentication 382 ...
Page 386: ... The TLS ALG 9 1 5 The TLS Alternative for VPN Chapter 9 VPN 386 ...
Page 439: ...Figure 9 3 PPTP Client Usage 9 5 4 PPTP L2TP Clients Chapter 9 VPN 439 ...
Page 450: ...9 7 6 Specific Symptoms Chapter 9 VPN 450 ...
Page 488: ...10 4 6 Setting Up SLB_SAT Rules Chapter 10 Traffic Management 488 ...
Page 503: ...11 6 HA Advanced Settings Chapter 11 High Availability 503 ...
Page 510: ...12 3 5 Limitations Chapter 12 ZoneDefense 510 ...
Page 533: ...13 9 Miscellaneous Settings Chapter 13 Advanced Settings 533 ...