System information

Address Configuration for Connected Devices
388 AlterPath OnBoard Administrator’s Guide
creates the routes needed to get packets flowing through the tunnel, so
neither the user nor the administrator need to create routes to support
IPSec access to devices.
• Enable native IP and access the device’s native features.
See “Enabling Native IP and Accessing a Device’s Native Features Using
Real IP Addresses for Example 2” on page 391.
PPTP VPN Configuration for Example 2
After the private subnets, device, and user account configuration in “Two
Private Subnets and User Configuration for Example 2” on page 382 is
completed, a VPN connection must be created. This example shows the
configuration steps that must be performed by the OnBoard administrator and
by a user on a remote workstation for setting up an PPTP VPN connection
1
that would enable the authorized user “allSps” to access “sp1,” “sp2,” “sp3,”
and “sp4.”
The OnBoard administrator must do the following to enable the PPTP client:
• Make sure that the PPTP service is enabled.
• Configure PPTP on the OnBoard.
The following screen example shows an example PPTP configuration on
the Network → VPN connections screen.
Figure A-12:PPTP VPN Configuration Example: Address Pools
Figure A-12 shows the following address pools:
• PPTP local address pool: 192.168.2.1-10
• PPTP remote address pool: 192.168.3.1-10
1. A VPN connection must exist before a user can access native IP management features on a
device.