Secure Gateway with Dynamic WAN IP Address

- Prestige static WAN IP v.s. peer side dynamic IP
- Prestige dynamic WAN IP v.s. peer side static IP
- Prestige dynamic WAN IP v.s. peer side dynamic IP

Most of the cases, static IP addresses are used for VPN tunneling endpoints. But for SOHO users, generally, it is a dynamic case. In this case, this IP will not be available to pre-defined in the VPN box. There are some tips when configuring Prestige in any dynamic case.

- Prestige static WAN IP v.s. peer side dynamic IP

> 1. In VPN settings of Prestige, please specify the IP address of Secure Gateway as 0.0.0.0.

> 2. In remote side, generally speaking, most VPN clients will bind PPP/Ethernet adapter's dynamic IP address to IPSec automatically . The only thing you need to concern is to specify the interface you want to apply IPSec/VPN correctly. The rest parts are similar with that in static cases.

> 3. Afterward, the VPN connection can ONLY be initiated from dynamic side to static side in order to update its dynamic IP to the static side.

> 4. In peer side, Are you using Win2K built-in IPSec? In this case, W2K won't capture the dynamic IP address automatically for you. You have to obtain your dynamic IP address and then go back to IPSec configuration to setup your current IP address.

- Prestige dynamic WAN IP v.s. peer side static IP

> 1. In VPN settings of Prestige, please specify the IP address of My IP as 0.0.0.0. Prestige will automatically bind it's current WAN IP address to IPSec.

> 2. IPSec tunnel in this case, can ONLY be initiated from Prestige.
> 3. In peer side, Are you using SonicWALL, NetScreen? SonicWALL requires you to enter an ID (in FQDN format) to identify Prestige. Currently, Prestige don't have FQDN support. Prestige will support it since major firmware version V3.52.

- Prestige dynamic WAN IP v.s. peer side dynamic IP

> 1. Prestige v.s. Prestige

>    <Solution 1>

>    1.1. In PrestigeA, please register a DynDNS account from http://www.dyndns.org/.
>    Enable DynDNS function in SMT menu 1 or web configurator Advanced/System/DDNS.
>    You can get here to learn how to enable DynDNS function in Prestige.
>    In VPN settings, please specify the IP address of My IP as 0.0.0.0 and Secure Gateway as 0.0.0.0.

>    1.2. In PrestigeB, please specify the IP address of My IP as 0.0.0.0 and Secure Gateway as the domain name you registered for PrestigeA.

>    1.3. Please always initiate VPN tunnel from PrestigeB on which Secure Gateway is configured as dynamic domain name.

>    <Solution 2>

>    1.1. Register DynDNS account from http://www.dyndns.org/ for both PrestigeA & PrestigeB.

> > 1.2. In PrestigeA, configure My IP as 0.0.0.0 and Secure Gateway as the dynamic domain name of PrestigeB.

> > 1.3. In PrestigeB, configure My IP as 0.0.0.0 and Secure Gateway as the dynamic domain name of PrestigeA.

> > 1.4. You can initiate VPN tunnel from PrestigeA or PrestigeB by this solution.

> 2. Prestige v.s. 3rd Party

>    This is highly dependent on which kind of 3rd party you use. Generally speaking, this 3rd party VPN solution must

>    2.1 Support dyndns for update of it's dynamic WAN IP. (If Prestige is to be the VPN initiator.)

>    Or

>    2.2 Support Secure Gateway can be configured by Domain Name. (If Prestige is to be the VPN responder) But currently, Prestige series don't have FQDN support. Prestige will support it since major firmware version V3.52.