System information

Address Configuration for Connected Devices
402 AlterPath OnBoard Administrator’s Guide
Enabling Native IP and Accessing a Device’s Native Features
Using Virtual Network Addresses for Example 3
After creating the VPN tunnel as described in “IPSec VPN Configuration for
Example 3” on page 399 or “PPTP VPN Configuration for Example 3” on
page 400, the user enables native IP and accesses a device’s native features.
In this example, to access “sp4,” which is a type of service processor that does
not work with virtual network addresses because it is not compatible with
DNAT, the user would enter the OnBoard’s real address, as described in
“Enabling Native IP and Accessing a Device’s Native Features Using Real IP
Addresses for Example 2” on page 391.
Enabling Native IP Access for Example 3
In this example, to enable native IP access to “sp1,” “sp2,” or “sp3,” the user
would enter the OnBoard’s virtual IP address, which is 172.20.0.1, in one
of the two following ways:
• In a browser on the user’s workstation, the user would do the following:
• Bring up the Web Manager using http://172.20.0.1.
• Chose the Devices left menu option.
• For either “sp1,” “sp2,” or “sp3,” click “Enable Native IP access.”
• On the user’s workstation’s command line, the user would do the
following:
• Use ssh to connect to the OnBoard’s console and to access the
rmenush menu in one of the following ways:
ssh username:@172.20.0.1
ssh -t username:@172.20.0. menu
• Select “Access Devices” from the menu.
• Select either “sp1,” “sp2,” or “sp3” from the devices menu.
• Select “Enable native IP” from the list of management actions the user
is authorized to perform on the device.
OR
• Use ssh to execute the nativeipon command directly using the
device alias:
ssh username:device_alias@172.20.0.1 nativeipon