|
| Chapter 28 Application Patrol |
| Table 134 AppPatrol > Other > Edit (continued) | |
| LABEL | DESCRIPTION |
| Inbound | Type how much inbound bandwidth, in kilobits per second, this policy |
| kbps | allows the traffic to use. Inbound refers to the traffic the ZyWALL sends |
|
| to a connection’s initiator. |
|
| If you enter 0 here, this policy does not apply bandwidth management |
|
| for the matching traffic that the ZyWALL sends to the initiator. Traffic |
|
| with bandwidth management disabled (inbound and outbound are both |
|
| set to 0) is automatically treated as the lowest priority (7). |
|
| If the sum of the bandwidths for routes using the same next hop is |
|
| higher than the actual transmission speed, lower priority traffic may not |
|
| be sent if higher priority traffic uses all of the actual bandwidth. |
|
|
|
| Outbound | Type how much outbound bandwidth, in kilobits per second, this policy |
| kbps | allows the traffic to use. Outbound refers to the traffic the ZyWALL sends |
|
| out from a connection’s initiator. |
|
| If you enter 0 here, this policy does not apply bandwidth management |
|
| for the matching traffic that the ZyWALL sends out from the initiator. |
|
| Traffic with bandwidth management disabled (inbound and outbound are |
|
| both set to 0) is automatically treated as the lowest priority (7). |
|
| If the sum of the bandwidths for routes using the same next hop is |
|
| higher than the actual transmission speed, lower priority traffic may not |
|
| be sent if higher priority traffic uses all of the actual bandwidth. |
|
|
|
| Priority | This field displays when the inbound or outbound bandwidth |
|
| management is not set to 0. Enter a number between 1 and 7 to set the |
|
| priority for traffic that matches this policy. The smaller the number, the |
|
| higher the priority. |
|
| Traffic with a higher priority is given bandwidth before traffic with a |
|
| lower priority. |
|
| The ZyWALL uses a |
|
| bandwidth between traffic flows with the same priority. |
|
| The number in this field is ignored if the incoming and outgoing limits |
|
| are both set to 0. In this case the traffic is automatically treated as being |
|
| set to the lowest priority (7) regardless of this field’s configuration. |
|
|
|
| Maximize | This field displays when the inbound or outbound bandwidth |
| Bandwidth | management is not set to 0. Enable maximize bandwidth usage to let |
| Usage | the traffic matching this policy “borrow” any unused bandwidth on the |
|
| |
|
| |
|
| After each application or type of traffic gets its configured bandwidth |
|
| rate, the ZyWALL uses the fairness- based scheduler to divide any |
|
| unused bandwidth on the |
|
| traffic types that need more bandwidth and have maximize bandwidth |
|
| usage enabled. |
|
|
|
| Log | This field controls what kind of record the ZyWALL creates when traffic |
|
| matches this policy. See Chapter 46 on page 723 for more on logs. |
|
| no - the ZyWALL does not record anything |
|
| log - the ZyWALL creates a record in the log |
|
| log alert - the ZyWALL creates an alert |
|
|
|
| 461 |
ZyWALL USG 50 User’s Guide | |
|
|