Using Vpn Routing Between Branches - ZyXEL Communications ZyWALL 5 Support Notes

Configuration on Local ZyWALL
Pre-Shared Key must be identical on both entities
Local ID Type & Content on Local ZyWALL must be identical as
Peer ID Type & Content on Peer VPN gateway
Peer ID Type & Content on Local ZyWALL on Local ZyWALL must be identical as
Local ID Type & Content on Peer VPN gateway
Note:
1) If "ID Type" is mis-configured on Local/Remote IPSec Gateway, the ZyWALL will show
[NOTFY:ERR_ID_INFO] error message in related IKE log.
2) If "Pre-shared Key" or ID "Content" are mis-configured on Local/Remote IPSec Gateway,
ZyWALL will show [NOTFY:ERR_ID_INFO] error message in related IKE log.

Using VPN routing between branches

1. Setup VPN in Branch Office A
2. Setup VPN in Branch Office B
3. Setup VPN in Headquarter
This page guides us how to setup VPN routing between branch offices through headquarter. So that whenever
branch office A wants to talk to branch office B, headquarter plays as a VPN relay. Users can gain benefit
from such application when the scale of branch offices is very large, because no additional VPN tunnels
between branch offices are needed. In this support note, we skip the detailed configuration steps for Internet
access and presume that you are familiar with basic ZyNOS VPN configuration.
Configuration on Peer VPN gateway
All contents copyright (c) 2006 ZyXEL Communications Corporation.
ZyWALL 5 Support Notes
104