ZyXEL Prestige 792H SDSL Router 91-004-342004B 사용자 설명서

제품 코드
91-004-342004B
다운로드
페이지 428
Prestige 792H G.SHDSL Router 
VPN Screens 
 
14-9 
The following table describes the labels in this screen. 
Table 14-7 VPN IKE 
LABEL  
DESCRIPTION 
IPSec Setup 
 
Active  Select this check box to activate this VPN policy. 
Keep Alive
 
Select either Yes or No from the drop-down list box.  
Select Yes to have the Prestige automatically reinitiate the SA after the SA lifetime 
times out, even if there is no traffic. The remote IPSec router must also have keep 
alive enabled in order for this feature to work.  
Name  Type up to 32 characters to identify this VPN policy. You may use any character, 
including spaces, but the Prestige drops trailing spaces. 
IPSec Key Mode  Select IKE or Manual from the drop-down list box. Manual is a useful option for 
troubleshooting if you have problems using IKE key management.  
Negotiation Mode
 
Select Main or Aggressive from the drop-down list box. Multiple SAs connecting 
through a secure gateway must have the same negotiation mode. 
 
Encapsulation 
Mode 
Select Tunnel mode or Transport mode from the drop-down list box. 
DNS Server (for 
IPSec VPN) 
If there is a private DNS server that services the VPN, type its IP address here. The 
Prestige assigns this additional DNS server to the Prestige 's DHCP clients that have 
IP addresses in this IPSec rule's range of local addresses. 
A DNS server allows clients on the VPN to find other computers and servers on the 
VPN by their (private) domain names. 
Local
 
Local IP addresses must be static and correspond to the remote IPSec router's 
configured remote IP addresses.  
Two active SAs can have the same configured local or remote IP address, but not 
both. You can configure multiple SAs between the same local and remote IP 
addresses, as long as only one is active at any time. 
In order to have more than one active rule with the Secure Gateway Address field 
set to 0.0.0.0, the ranges of the local IP addresses cannot overlap between rules.  
If you configure an active rule with 0.0.0.0 in the Secure Gateway Address field and 
the LAN’s full IP address range as the local IP address, then you cannot configure 
any other active rules with the Secure Gateway Address field set to 0.0.0.0