Netgear FVS338 FVS338 Reference Manual - Page 96

Remote LAN IP, Address and Subnet Mask, Apply, VPN > IPsec VPN > Connection Status

Page 96 highlights

FVS338 ProSafe VPN Firewall 50 Reference Manual • The remote WAN IP address must be a public address or the Internet name of the remote gateway. The Internet name is the Fully Qualified Domain Name (FQDN) as registered in a Dynamic DNS service. Both local and remote endpoints should be defined as either FQDN or IP addresses. A combination of IP address and FQDN is not allowed. Tip: For DHCP WAN configurations, first, set up the tunnel with IP addresses. Once you validate the connection, use the wizard to create new policies using FQDN for the WAN addresses. 6. Enter the local LAN IP and Subnet Mask of the remote gateway in the Remote LAN IP Address and Subnet Mask fields. Note: The Remote LAN IP address must be in a different subnet than the Local LAN IP address. For example, if the local subnet is 192.168.1.x, then the remote subnet could be 192.168.10.x. but could not be 192.168.1.x. If this information is incorrect, the tunnel will fail to connect. 7. Click Apply to save your settings: the VPN Policies page shows the policy is now enabled. Figure 5-4 8. If you are connecting to another NETGEAR VPN firewall, use the VPN Wizard to configure the second VPN firewall to connect to the one you just configured. After both firewalls are configured, go to VPN > IPsec VPN > Connection Status to display the status of your VPN connections. Figure 5-5 5-4 v1.0, March 2009 Virtual Private Networking

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200

FVS338 ProSafe VPN Firewall 50 Reference Manual
5-4
Virtual Private Networking
v1.0, March 2009
The remote WAN IP address must be a public address or the Internet name of the remote
gateway. The
Internet name
is the Fully Qualified Domain Name (FQDN) as registered in
a Dynamic DNS service. Both local and remote endpoints should be defined as either
FQDN or IP addresses. A combination of IP address and FQDN is not allowed.
6.
Enter the local LAN IP and Subnet Mask of the remote gateway in the
Remote LAN IP
Address and Subnet Mask
fields.
7.
Click
Apply
to save your settings: the VPN Policies page shows the policy is now enabled.
8.
If you are connecting to another NETGEAR VPN firewall, use the VPN Wizard to configure
the second VPN firewall to connect to the one you just configured.
After both firewalls are configured, go to
VPN > IPsec VPN > Connection Status
to display
the status of your VPN connections.
Tip:
For DHCP WAN configurations, first, set up the tunnel with IP addresses.
Once you validate the connection, use the wizard to create new policies
using FQDN for the WAN addresses.
Note:
The Remote LAN IP address
must
be in a different subnet than the Local LAN
IP address. For example, if the local subnet is 192.168.1.x, then the remote
subnet could be 192.168.10.x. but
could not
be 192.168.1.x. If this information
is incorrect, the tunnel will fail to connect.
Figure 5-4
Figure 5-5