Amer Networks E5Web GUI - Manual (Page 662)

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
Device:/> add PipeRule ReturnChain=std-in
SourceInterface=lan
SourceNetwork=lan_net
DestinationInterface=wan
DestinationNetwork=all-nets
Service=all_services
Name=Outbound
InControl
Follow the same steps used for the Web Interface below.
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: lan_net
• 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, and neither is any dynamic balancing.
10.1.4. Limiting Bandwidth in Both Directions
Using a Single Pipe for Both Directions
Chapter 10: Traffic Management
662