Optional Services
Bandwidth Management
Source
Action
192.168.0.10-192.168.0.20
Do PR
192.168.10.0/255.255.255.0
Do PR
Source
Destination
Action
192.168.0.15
WAN
Do PR
192.168.0.10-192.168.0.20
WAN
No PR
192.168.10.0/255.255.255.0
ANY
No PR
211.21.48.196
10.10.1.0/255.255.255.0
No PR
Note: Rules are matched top down. Once one rule is matched, the rest will be ignored. In this case, the connections
from 192.168.0.15 may meet the criteria of the first and second IP Pair rules, only the first rule will be applied. Hence
the rules will not perform NoPR on 192.168.0.15 even though it matches the second rule.It shall be noted that Web
Service Rules are prioritized over IP Pair Rules. As 192.168.10.0/255.255.255.0 is configured to be NoPR in IP Pair
Rules, but DoPR in Web Service Rules, HTTP connections will still apply persistent routing.
Bandwidth Management
Bandwidth Management (BM) allocates bandwidth to applications. To secure the bandwidth of critical applications,
FortiWAN Bandwidth Management (BM) defines inbound and outbound bandwidth based on traffic direction, i.e. take
FortiWAN as the center, traffic flows from WAN to LAN is inbound traffic, otherwise, it is outbound traffic. No matter
which direction a connection is established in, a connection must contain inbound traffic and outbound traffic. The
section will mainly explain how to guarantee bandwidth based on priority settings, and how to manage inbound and
outbound traffic by configuring busy/idle hours, data source/destination, and service type, etc.
Bandwidth Management consists of Classes and Filters (IPv4/IPv6). Click "Expand Link Settings" or "Collapse Link
Settings" to show or hide configuration details of links and bandwidth limit.
FortiWAN provides mechanisms to record, notify and analysis on events refer to the Bandwidth Management service,
see "
" and "
".
Inbound BM and Outbound BM
Bandwidth Management is divided into inbound BM and outbound BM, which are used to control the inbound traffic
and outbound traffic respectively on each WAN port. Packets (network streams) that are transferred inward (from WAN
to LAN, DMZ or localhost) on a WAN port are counted to inbound traffic; packets that are transferred outward (from
LAN, DMZ or localhost to WAN) on a WAN port are counted to outbound traffic. Therefor, both inbound BM and
outbound BM are required if you would like to control a connection in the two ways (Bandwidth Management ignores
the direction of a connection, the initiator of the connection). BM policy consists of BM classes and filters. A BM class
defines the bandwidth to allocate applications on each WAN port, while a BM filter defines the associated application
226
FortiWAN Handbook
Fortinet Technologies Inc.
