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 the Total textbox under Pipe Limits
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 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.
Command-Line Interface
gw-world:/> add PipeRule ReturnChain=std-in
SourceInterface=lan
SourceNetwork=lannet
DestinationInterface=wan
DestinationNetwork=all-nets
Service=all_services
Name=Outbound
Web Interface
1.
Go to: Traffic Management > Traffic Shaping > Add > Pipe Rule
2.
Specify a suitable name for the pipe, for instance outbound
3.
Now enter:
•
Service: all_services
•
Source Interface: lan
•
Source Network: lannet
•
Destination Interface: wan
•
Destination Network: all-nets
4.
Under the Traffic Shaping tab, make std-in selected in the Return Chain control
5.
Click OK
This setup limits all traffic from the outside (the Internet) to 2 megabits per second. No priorities are applied, nor
any dynamic balancing.
10.1.4. Limiting Bandwidth in Both Directions
Using a Single Pipe for Both Directions
A single pipe does not care in which direction the traffic through it is flowing when it calculates
total throughout. Using the same pipe for both outbound and inbound traffic is allowed by
NetDefendOS but this will not partition the pipe limit exactly in two between the two directions.
In the previous example only bandwidth in the inbound direction is limited. In most situations, this
is the direction that becomes full first. But what if the outbound traffic must be limited in the same
way?
10.1.4. Limiting Bandwidth in Both
Directions
Chapter 10. Traffic Management
495
Содержание NetDefend DFL-1660
Страница 28: ...1 3 NetDefendOS State Engine Packet Flow Chapter 1 NetDefendOS Overview 28 ...
Страница 88: ...2 6 3 Restore to Factory Defaults Chapter 2 Management and Maintenance 88 ...
Страница 166: ...3 10 DNS Chapter 3 Fundamentals 166 ...
Страница 254: ...4 7 5 Advanced Settings for Transparent Mode Chapter 4 Routing 254 ...
Страница 268: ...5 4 IP Pools Chapter 5 DHCP Services 268 ...
Страница 368: ...6 7 Blacklisting Hosts and Networks Chapter 6 Security Mechanisms 368 ...
Страница 390: ...7 4 7 SAT and FwdFast Rules Chapter 7 Address Translation 390 ...
Страница 414: ...8 3 Customizing Authentication HTML Pages Chapter 8 User Authentication 414 ...
Страница 490: ...9 8 6 Specific Symptoms Chapter 9 VPN 490 ...
Страница 528: ...10 4 6 Setting Up SLB_SAT Rules Chapter 10 Traffic Management 528 ...
Страница 544: ...11 7 HA Advanced Settings Chapter 11 High Availability 544 ...
Страница 551: ...12 3 5 Limitations Chapter 12 ZoneDefense 551 ...
Страница 574: ...Default 512 13 9 Miscellaneous Settings Chapter 13 Advanced Settings 574 ...
Страница 575: ...13 9 Miscellaneous Settings Chapter 13 Advanced Settings 575 ...