ZyWALL 2 and ZyWALL 2WE
MetricThe metric sets the priority for the ZyWALL’s routes to the Internet. If the two routes have the same metric, the ZyWALL uses the following
1.Normal route: designated by the ISP (see Remote Node Setup chapter) or a static route (see the IP Static Route Setup chapter)
2.
For example, if the normal route has a metric of "1" and the
If you want the traffic redirect route to take first priority over the normal route, all you need to do is set the traffic redirect route’s metric to "1" and the normal route to "2" (or greater).
TableFIELD | DESCRIPTION | EXAMPLE |
|
|
|
Authen | This field sets the authentication protocol used for outgoing calls. | CHAP/PAP |
| Options for this field are: |
|
| CHAP/PAP - Your ZyWALL will accept either CHAP or PAP when |
|
| requested by this remote node. |
|
| CHAP - accept CHAP only. |
|
| PAP - accept PAP only. |
|
Telco Option |
|
|
Allocated | The field sets a ceiling for outgoing call time for this remote node. The | 0 |
Budget | default for this field is 0 meaning no budget control. | (default) |
Period(hr) | This field is the time period that the budget should be reset. For | 0 |
| example, if we are allowed to call this remote node for a maximum of 10 | (default) |
| minutes every hour, then the Allocated Budget is (10 minutes) and the |
|
| Period(hr) is 1 (hour). |
|
Schedules | You can apply up to four schedule sets here. For more details please |
|
| refer to the Call Schedule Setup chapter. |
|
This field specifies if you want to make the connection to this remote | No | |
Connection | node a | (default) |
| section. |
|
Remote Node Setup |