Packet Flow Of Pipe Rule Set To Pipe - D-Link NetDefend DFL-210 User Manual

10.1.2. Traffic Shaping in
NetDefendOS
needed in an ISP scenario where individual pipes are allocated to each client.
Pipe Rules
Pipe Rules make up the Pipe Rule set. Each Rule is defined much like other NetDefendOS policies:
by specifying the source/destination interface/network as well as the service to which the rule is to
apply. Once a new connection is permitted by the IP rule set, the Pipe rule set is then checked for
any matching rules. Pipe rules are checked in the same way as IP rules, by going from top to bottom
in the rule set. The first matching Pipe Rule, if any, is used for traffic shaping.
When a Pipe Rule is defined, the pipes to be used with that rule are also specified and they are
placed into one of two lists in the Pipe Rule. These lists are:
• The Forward Chain
These are the pipes that will be used for outgoing (leaving) traffic from the NetDefend Firewall.
One, none or a series of pipes may be specified.
• The Return Chain
These are the pipes that will be used for incoming (arriving) traffic. One, none or a series of
pipes may be specified.
Figure 10.1. Packet Flow of Pipe Rule Set to Pipe
The pipes that are to be used are specified in a pipe list. If only one pipe is specified then that is the
pipe whose characteristics will be applied to the traffic. If a series of pipes are specified then these
will form a Chain of pipes through which traffic will pass. A chain can be made up of at most 8
pipes.
If no pipe is specified in a list then traffic that matches the rule will not flow through any pipe but it
will also mean that the traffic will not be subject to any other pipe rules found later in the rule set.
Pipes Will Not Work With FwdFast Rules
Note: No pipe rules are defined by default
The rule set for pipe rules is initially empty with no rules being defined by default. At
least one rule must be created for traffic shaping to begin to function.
404
Chapter 10. Traffic Management