NETGEAR FVG318 - ProSafe 802.11g Wireless VPN Firewall 8... User manual

Configure VPN between ProSafe VPN Client Software and FVG318
The following configuration is tested with:
NETGEAR FVG318 with firmware version 1 0 41
NETGEAR ProSafe VPN Client Software version 10 5 1
Configure the FVG318
1 Log into the FVG318’s admin GUI
2 Click on VPN Wizard on the left panel under VPN
3 Click Next
4 Enter a connection name and a value for the pre-shared key The same name and
pre-shared key have to be entered when configuring the ProSafe VPN client
software Select This VPN tunnel will connect to A remote VPN client

5 A summary of the VPN policy will be displayed Click Done

6 You can review the IKE policy and VPN policy by clicking on IKE Policies
7 And VPN Policies under VPN In most cases, you can just leave them as it

Configure the ProSafe VPN Client Software
1 Right click on the ProSafe VPN client icon on the system tray and select Security
Policy Editor
2 Under the Options menu, select Global Policy Settings The Global Policy Setting
dialog box opens Make sure Allow to Specify Internal Network Address is
checked

3 Under the Edit menu, select Add and select Connection
4 A new connection will be created You can rename the connection name by
double click on the name On the right panel, under Remote Party Identity and
Addressing, select IP Subnet as ID Type, enter the LAN subnet on the FVG318 as
Subnet and enter the LAN subnet mask as Mask Choose All for Protocol Check
the box Connect using and select Secure Gateway Tunnel For ID Type, choose
Domain Name and enter fvx_local com under Domain Name Select Gateway IP
Address and enter the WAN IP address of the FVG318

5 On the left panel, click on Security Policy On the right panel, select Aggressive
Mode under Phase 1 Negotiation Mode Make sure Enable Perfect Forward
Secrecy is unchecked Leave Enable Replay Detection checked

6 Click on My Identity on the left panel On the right panel, select None under
Select Certificate For ID Type, select Domain Name and enter <policy
name><digit> fvg_remote com where the policy name is the VPN policy name
you entered when configure VPN Wizard on the FVG318 and digit can be any
digit, it is being used to distinguish multiple VPN client user connected to the
FVG318 at the same time In our example, the domain name will be
testvpn1 fvg_remote com Another VPN client user can use
testvpn2 fvg_remote com as domain name For Virtual Adapter, select Disabled
Enter 0 0 0 0 for Internal Network IP Address Select Any for Internet Interface
If you cannot find Domain Name under ID Type, you may not have select
Aggressive mode under Security Policy as indicated on Step (5)

7 Click on the Pre-Shared Key button, and Click Enter Key Enter the same pre-
shared key you’ve entered when configure the FVG318 Click OK

8 On the left panel, expand Security Policy and Authentication (Phrase 1) and click
on Proposal 1 On the right panel, you can keep everything as default Make sure
they match the screen below
9 On the left panel, expand on Key Exchange (Phrase 2) and click on Proposal 1
On the right panel, left everything as default Make sure they mach the screen
below
10 Save the policy by click on the save button or choose File->Save

11 To connect, right click on the ProSafe VPN client icon on the system tray and
choose Connect, select the Connection Profile you just created
12 A connection status window should be displayed and eventually, it should said
Successfully connect to your connection profile
13 You can test the VPN by pinging resources behind the FVG318 Note that if you
have not enable Response to ping on Internet port in the FVG318 WAN option
menu, you won’t be able to ping the LAN interface IP address of the FVG318
14 If the VPN will not connect, double check the parameters in both the FVG318 and
the VPN Client Policy, make sure they are matching on both side
15 For more troubleshooting, you can review the VPN log on the FVG318 and the
Log Viewer on the ProSafe VPN client by right click on the ProSafe VPN client
icon on the system tray and select Log Viewer A successful connection should
appear as follow in the Log Viewer