background image

 

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

VP

N B

ox t

o B

ox c

onn

ecti

on

V

P

N

 C

lie

n

to

 B

o

x

 c

o

n

n

e

c

ti

o

n

 (

m

o

d

e

 c

o

n

fi

g

)

LAN2

LAN1

Client c

onnecti

on to LA

N 2 via 

VPN Cl

ient con

nection

 to LAN

1

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

 

 
 
 
 
 
 
 
 
 
 

Summary of Contents for FVG318v1 - ProSafe 802.11g Wireless VPN Firewall Switch

Page 1: ...are 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 V P N C li e n t t o B o x c o n n e c t io n m o d e c o n f ig 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 T...

Page 2: ...PN policies on 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 8 ...

Page 3: ...multiple VPN policies FVX538 1x Box to box policy from the FVX538 to the FVS338 Policy name BoxtoBox 1x Client to Box policy on the FVX538 to connect to the VPN clients Policy name LAN1toVPN 1x Manual VPN policy using the IKE policy used for the box to box connection to allow the VPN clients to connect to the LAN behind the FVS338 Policy name LAN2toClient FVS338 1x Box to box policy from the FVS33...

Page 4: ...NS address of 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 BoxtoBox Input the pre shared key as at point Configure the Public or DNS address of the Remote lo...

Page 5: ...ent 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 subnet modifying the Start IP address to 192 168 0 0 with subnet mask 255 255 255 0 Click on Apply ...

Page 6: ...o be the LAN of the FVS338 as 172 22 102 0 24 Ensure that the Select IKE Policy is set to BoxtoBox Click on Apply FVS338 VPN Config Policy 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 Endpo...

Page 7: ...Party ID type as IP Subnet and the subnet and mask as 172 22 0 0 255 255 255 0 this will address both LAN1 and LAN2 The gateway IP address will be specified at the WAN address of the FVX538 in our case In My identity change the pre shared key to match the VPN policy LAN1toVPN created on the FVX538 12345678 Set the Virtual adapter as Required as specify a unique value for the Internal network IP ad...

Page 8: ...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 address FVS338 From Monitoring Diagnostic on the FVS338 ping the VPN client IP address 1902 168 0 1 ...

Reviews: