Tripp Lite B0930082E4UM Owners Manual for B093- B097- and B098-Series Console - Page 60

OpenVPN

Page 60 highlights

4. Serial Port, Host, Device and User Configuration In Authentication Protocol, select the authentication protocol to be used. Either authenticate as part of ESP (Encapsulating Security Payload) encryption or separately using the AH (Authentication Header) protocol. Enter a Left ID and Right ID. The local host/gateway and remote host/gateway use this identifier for IPsec negotiation and authentication. Each ID must include a '@' and can include a fully qualified domain name preceded by '@' (e.g. left@ example.com). Enter the public IP or DNS address of this Tripp Lite VPN gateway as the Left Address. You can leave this blank to use the interface of the default route. In Right Address, enter the public IP or DNS address of the remote end of the tunnel (only if the remote end has a static or dyndns address). Otherwise, leave this blank. If the Tripp Lite VPN gateway is serving as a VPN gateway to a local subnet (e.g. the console server has a management LAN configured), enter the private subnet details in Left Subnet. Use the CIDR notation (where the IP address number is followed by a slash and the number of 'one' bits in the binary notation of the netmask). For example, 192.168.0.0/24 indicates an IP address where the first 24 bits are used as the network address. This is the same as 255.255.255.0. If the VPN access is only to the console server itself and to its attached serial console devices, leave Left Subnet blank. If there is a VPN gateway at the remote end, enter the private subnet details in Right Subnet. Again, use the CIDR notation and leave blank if there is only a remote host. Select Initiate Tunnel if the tunnel connection is to be initiated from the Left console server end. This can only be initiated from the VPN gateway (Left) if the remote end was configured with a static (or dyndns) IP address. Click Apply to save changes. Note: It is essential the configuration details set up on the advanced console server (referred to as the Left or Local host) exactly match the setup entered when configuring the Remote (Right) host/gateway or software client. 4.9 OpenVPN Console servers with firmware version 3.2 and later include OpenVPN. OpenVPN uses the OpenSSL library for encryption, authentication, and certification, which means it uses SSL/TSL (Secure Socket Layer/Transport Layer Security) for key exchange and can encrypt both data and control channels. Using OpenVPN allows for the building of cross-platform, point-topoint VPNs using either X.509 PKI (Public Key Infrastructure) or custom configuration files. OpenVPN allows secure tunneling of data through a single TCP/UDP port over an unsecured network, thus providing secure access to multiple sites and secure remote administration to a console server over the Internet. OpenVPN also allows the use of Dynamic IP addresses by both the server and client, thus providing client mobility. For example, an OpenVPN tunnel may be established between a roaming windows client and a Tripp Lite advanced console server within a data center. Configuration of OpenVPN can be a complex undertaking. For ease and convenience, Tripp Lite provides a simple GUI interface for basic set up as described below. For more detailed information on configuring OpenVPN Access server or client, refer to the HOW TO and FAQs at http://www.openvpn.net. 60

  • 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
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288

60
In
Authentication Protocol
, select the authentication protocol to be used. Either authenticate as part of
ESP
(Encapsulating
Security Payload) encryption or separately using the
AH
(Authentication Header) protocol.
Enter a
Left ID
and
Right ID
. The local host/gateway and remote host/gateway use this identifier for IPsec negotiation and
authentication. Each ID must include a ‘@’ and can include a fully qualified domain name preceded by ‘@’ (e.g. left@
example.com).
Enter the public IP or DNS address of this Tripp Lite VPN gateway as the
Left Address
. You can leave this blank to use the
interface of the default route.
In
Right Address
, enter the public IP or DNS address of the remote end of the tunnel (only if the remote end has a static or
dyndns address). Otherwise, leave this blank.
If the Tripp Lite VPN gateway is serving as a VPN gateway to a local subnet (e.g. the console server has a management LAN
configured), enter the private subnet details in
Left Subnet
. Use the CIDR notation (where the IP address number is followed
by a slash and the number of ‘one’ bits in the binary notation of the netmask). For example, 192.168.0.0/24 indicates an IP
address where the first 24 bits are used as the network address. This is the same as 255.255.255.0. If the VPN access is
only to the console server itself and to its attached serial console devices, leave
Left Subnet
blank.
If there is a VPN gateway at the remote end, enter the private subnet details in
Right Subnet
. Again, use the CIDR notation
and leave blank if there is only a remote host.
Select
Initiate Tunnel
if the tunnel connection is to be initiated from the Left console server end. This can only be initiated
from the VPN gateway (Left) if the remote end was configured with a static (or dyndns) IP address.
Click
Apply
to save changes.
Note:
It is essential the configuration details set up on the advanced console server (referred to as the Left or Local host) exactly match the
setup entered when configuring the Remote (Right) host/gateway or software client.
4.9 OpenVPN
Console servers with firmware version 3.2 and later include OpenVPN. OpenVPN uses the OpenSSL library for encryption,
authentication, and certification, which means it uses SSL/TSL (Secure Socket Layer/Transport Layer Security) for key
exchange and can encrypt both data and control channels. Using OpenVPN allows for the building of cross-platform, point-to-
point VPNs using either X.509 PKI (Public Key Infrastructure) or custom configuration files.
OpenVPN allows secure tunneling of data through a single TCP/UDP port over an unsecured network, thus providing secure
access to multiple sites and secure remote administration to a console server over the Internet.
OpenVPN also allows the use of Dynamic IP addresses by both the server and client, thus providing client mobility. For
example, an OpenVPN tunnel may be established between a roaming windows client and a Tripp Lite advanced console server
within a data center.
Configuration of OpenVPN can be a complex undertaking. For ease and convenience, Tripp Lite provides a simple GUI interface
for basic set up as described below. For more detailed information on configuring OpenVPN Access server or client, refer to the
HOW TO and FAQs at
.
4. Serial Port, Host, Device and User Configuration