Netgear FVG318v1 FVG318 Reference Manual - Page 121

VPN Consortium Scenario 2: FVG318 Gateway to Gateway with Digital Certificates

Get Netgear FVG318v1 - ProSafe 802.11g Wireless VPN Firewall Switch PDF manuals and user guides View all Netgear FVG318v1 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 121 highlights

ProSafe 802.11g Wireless VPN Firewall FVG318 Reference Manual VPN Consortium Scenario 2: FVG318 Gateway to Gateway with Digital Certificates The following is a typical gateway-to-gateway VPN that uses Public Key Infrastructure x.509 (PKIX) certificates for authentication. The network setup is identical to the WonAeNgIiPveAnddinress Scenario 1. The IKE Phase 1 and Phase 2 parameters are identical to the ones given in Scenario 1, with the exception that the identification is done with signatures authenticated by PKIX certificates. LAN IP Addresses Note: Before completing this configuration scenario, make sure the correct Time Zone is set on the FVG318. For instructions on this topic, see "Configuring Your Time Zone" on page 2-11. 1. Obtain a root certificate. a. Obtain the root certificate (that includes the public key) from a Certificate Authority (CA) Note: The procedure for obtaining certificates differs from a CA like Verisign and a CA such as a Windows 2000 certificate server, which an organization operates for providing certificates for its members. For example, an administrator of a Windows 2000 certificate server might provide it to you via e-mail. b. Save the certificate as a text file called trust.txt. 2. Install the trusted CA certificate for the Trusted Root CA. a. Log in to the FVG318. b. Select VPN > Certificates from the menu. c. In the Self Certificate Requests section, click Browse to locate the trust.txt file. d. Click Upload. 3. Create a certificate request for the FVG318. e. Fill in the required fields on the Generate Self Certificate section. • Name. Enter a name to identify this certificate. • Subject. This is the name that other organizations will see as the holder (owner) of this certificate. This should be your registered business name or official company name. Generally, all certificates should have the same value in the Subject field. Advanced Virtual Private Networking v1.0, September 2007 6-15

  • 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-15
v1.0, September 2007
VPN Consortium Scenario 2: FVG318 Gateway to Gateway with
Digital Certificates
The following is a typical gateway-to-gateway VPN that uses Public Key Infrastructure x.509
(PKIX) certificates for authentication. The network setup is identical to the one given in
Scenario 1. The IKE Phase 1 and Phase 2 parameters are identical to the ones given in Scenario 1,
with the exception that the identification is done with signatures authenticated by PKIX
certificates.
1.
Obtain a root certificate.
a.
Obtain the root certificate (that includes the public key) from a Certificate Authority (CA)
b.
Save the certificate as a text file called
trust.txt
.
2.
Install the trusted CA certificate for the Trusted Root CA.
a.
Log in to the FVG318.
b.
Select VPN > Certificates from the menu.
c.
In the
Self Certificate Requests
section, click
Browse
to locate the
trust.txt
file.
d.
Click
Upload
.
3.
Create a certificate request for the FVG318.
e.
Fill in the required fields on the Generate Self Certificate section.
•
Name. Enter a name to identify this certificate.
•
Subject. This is the name that other organizations will see as the holder (owner) of this
certificate. This should be your registered business name or official company name.
Generally, all certificates should have the same value in the Subject field.
Note:
Before completing this configuration scenario, make sure the correct Time Zone is
set on the FVG318. For instructions on this topic, see
“Configuring Your Time
Zone” on page 2-11
.
Note:
The procedure for obtaining certificates differs from a CA like Verisign
and a CA such as a Windows 2000 certificate server, which an
organization operates for providing certificates for its members. For
example, an administrator of a Windows 2000 certificate server might
provide it to you via e-mail.
WAN IP Address
LAN IP Addresses