Netgear FVG318v1 FVG318 Reference Manual - Page 111

Table 6-1., VPN Manual and Auto Policy Configuration Fields continued

Page 111 highlights

ProSafe 802.11g Wireless VPN Firewall FVG318 Reference Manual Table 6-1. VPN Manual and Auto Policy Configuration Fields (continued) Field Policy Name Policy Type: Remote End Point: NetBIOS Traffic Selection Local IP Remote IP Description The descriptive name of the VPN policy. Each policy should have a unique policy name. This name is not supplied to the remote VPN endpoint. It is only used to help you identify VPN policies. A policy can be generated automatically or manually: To create an Auto VPN Policy, you must first create an IKE policy and then add the corresponding Auto Policy for that IKE Policy. • Manual: All settings (including the keys) for the VPN tunnel are manually input for each end point. No 3rd party server or organization is involved. • Auto: Some parameters for the VPN tunnel are generated automatically. This requires using the IKE (Internet Key Exchange) protocol to perform negotiations between the 2 VPN Endpoints. The IP address or Internet name (FQDN) of the remote gateway or client PC. Conversely, the remote VPN endpoint must have the FVG318 local IP values entered as it's Remote VPN Endpoint. If enabled, it will allow NetBIOS broadcast to travel over the VPN tunnel The IP addresses on both the remote and local sides that will be part of the tunnel. They can be either a single IP address, several IP addresses in a range, or an entire subnet. The drop-down menu allows you to configure the source IP address of the outbound network traffic for which this VPN policy will provide security. Usually, this address is from your network address space. The choices are: • ANY for all valid IP addresses in the Internet address space • Single IP Address • Range of IP Addresses • Subnet Address The drop-down menu allows you to configure the destination IP address of the outbound network traffic for which this VPN policy will provide security. Usually, this address is from the remote site's corporate network address space. The choices are: • ANY for all valid IP addresses in the Internet address space • Single IP Address • Range of IP Addresses • Subnet Address Advanced Virtual Private Networking 6-5 v1.0, September 2007

  • 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

ProSafe 802.11g Wireless VPN Firewall FVG318 Reference Manual
Advanced Virtual Private Networking
6-5
v1.0, September 2007
Policy Name
The descriptive name of the VPN policy. Each policy should have a
unique policy name. This name is not supplied to the remote VPN
endpoint. It is only used to help you identify VPN policies.
Policy Type:
A policy can be generated automatically or manually: To create an Auto
VPN Policy, you must first create an IKE policy and then add the
corresponding Auto Policy for that IKE Policy.
Manual
: All settings (including the keys) for the VPN tunnel are
manually input for each end point. No 3rd party server or organization
is involved.
Auto
: Some parameters for the VPN tunnel are generated
automatically. This requires using the IKE (Internet Key Exchange)
protocol to perform negotiations between the 2 VPN Endpoints.
Remote End Point:
The IP address or Internet name (FQDN) of the remote gateway or client
PC. Conversely, the remote VPN endpoint must have the FVG318 local
IP values entered as it’s Remote VPN Endpoint.
NetBIOS
If enabled, it will allow NetBIOS broadcast to travel over the VPN tunnel
Traffic Selection
The IP addresses on both the remote and local sides that will be part of
the tunnel. They can be either a single IP address, several IP addresses
in a range, or an entire subnet.
Local IP
The drop-down menu allows you to configure the source IP address of
the outbound network traffic for which this VPN policy will provide
security.
Usually, this address is from your network address space. The choices
are:
ANY for all valid IP addresses in the Internet address space
Single IP Address
Range of IP Addresses
Subnet Address
Remote IP
The drop-down menu allows you to configure the destination IP address
of the outbound network traffic for which this VPN policy will provide
security. Usually, this address is from the remote site's corporate network
address space. The choices are:
ANY for all valid IP addresses in the Internet address space
Single IP Address
Range of IP Addresses
Subnet Address
Table 6-1.
VPN Manual and Auto Policy Configuration Fields (continued)
Field
Description