Netgear DGFV338 Hub and Spoke VPN network using the VPN Prosafe Client
Netgear DGFV338 - ProSafe Wireless ADSL Modem VPN Firewall Router Manual
 |
View all Netgear DGFV338 manuals
Add to My Manuals
Save this manual to your list of manuals |
Netgear DGFV338 manual content summary:
- Netgear DGFV338 | Hub and Spoke VPN network using the VPN Prosafe Client - Page 1
) via a single VPN connection to a central (Hub) Firewall/Router. The configuration can apply to any of the VPN Firewall/Router from firmware version 3.5.0.24 and above, and VPN clients from version 10.8.3 and above. The diagram below shows a typical scenario. FVS338 (Spoke 1) Public IP: 83.71.251 - Netgear DGFV338 | Hub and Spoke VPN network using the VPN Prosafe Client - Page 2
the Firewall/Routers 4 FVX538 VPN Config (Policy name: BoxtoBox 4 FVS338 VPN Config (Policy name: BoxtoBox 4 FVX538 VPN Config (Policy name: LAN1toVPN 5 FVX538 VPN Config (Policy name: LAN2Client 6 FVS338 VPN Config (Policy name: LAN2Client 6 VPN client configuration 7 Testing the connection - Netgear DGFV338 | Hub and Spoke VPN network using the VPN Prosafe Client - Page 3
via a modem or modem/router FVS338 connected to the Internet via a modem or modem/router VPN Client PCs connected Wireless/Wired to the Internet (via a LAN allowing IPSEC traffic) Logical setup FVX538 LAN IP: 172.22.101.101/24 DHCP: 172.22.101.0/24 Mode Config DHCP: 192.168.0.0/24 Firmware version - Netgear DGFV338 | Hub and Spoke VPN network using the VPN Prosafe Client - Page 4
the Remote location, and the LAN details (the Remote LAN IP address is intended as the subnet address). Click on Apply FVS338 VPN Config (Policy name: BoxtoBox) Access the VPN Wizard via the VPN configuration page. Configure the Connection name (for admin reasons this will match the other box as - Netgear DGFV338 | Hub and Spoke VPN network using the VPN Prosafe Client - Page 5
the VPN Wizard via the VPN configuration page. Create a new VPN client policy named LAN1toVPN (with any pre-shared key) Take note of the Remote and Local identifier whether using the default ones or new ones. Click on Apply Edit the LAN1toVPN. Change the Local IP setting to any and the Remote IP to - Netgear DGFV338 | Hub and Spoke VPN network using the VPN Prosafe Client - Page 6
name: LAN2Client) Access the VPN Wizard via the VPN configuration page. In the VPN Policy section click on Add (this will create a new manual VPN policy which will use an existing IKE policy) Create a new VPN client policy named LAN2toClient Specify the Remote Endpoint IP address to be the Public - Netgear DGFV338 | Hub and Spoke VPN network using the VPN Prosafe Client - Page 7
VPN client configuration This configuration requires advanced IP address planning. The VPN client policy needs to be able to address both Local Area Network #1 and Local Area Network #2 in the same client policy profile, therefore, the two networks must be presentable as one subnet or one address - Netgear DGFV338 | Hub and Spoke VPN network using the VPN Prosafe Client - Page 8
the connection VPN Client From the VPN client run ipconfig to confirm once the VPN is established that the Virtual adapter interface is assigned with the IP address specified in the policy (in this case 192.168.0.1 ) Test the VPN connection to both the FVX538 and FVS338 by pinging each box LAN IP
-
1 -
2 -
3 -
4 -
5 -
6 -
7 -
8
 |
 |
Version 1.0
Hub and Spoke VPN using the VPN Prosafe Client
This document describes the steps to undertake in configuring a Hub-and-Spoke network over
the Internet using VPNs (box-to-box and client-to-box).
In particular it describes how to allow VPN clients (
Spoke
) to access Remote LANs (
Spokes
) via
a single VPN connection to a central (
Hub
) Firewall/Router.
The configuration can apply to any of the VPN Firewall/Router from firmware version 3.5.0.24 and
above, and VPN clients from version 10.8.3 and above.
The diagram below shows a typical scenario.
Internet
Spoke 2
192.168.0.x/24
VPN Box to Box connection
VPN Client to Box connection (mode config)
LAN2
LAN1
Client connection to LAN 2 via VPN Client connection to LAN1
FVS338 (Spoke 1)
Public IP: 83.71.251.20
LAN IP : 172.22.102.102
VPN Information:
BoxToBox
(To FVX538)
LAN2toClient
(FVS338 To VPN clients via FVX538)
FVX538
Public IP: 83.71.251.19
LAN IP: 172.22.101.101
VPN Information:
BoxToBox
(To FVS338)
LAN1toVPN
(FVX538 To VPN clients)
LAN2toClient
(VPN Clients to FVS338 via FVX538)
LAN1