System information

Appendix A: Advanced Device Configuration 391
Address Configuration for Connected Devices
• To communicate with “sp3” and “sp4,” a route would needed to “sub2,”
which has the network IP address 192.168.4.0 as shown below:
• 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.
Enabling Native IP and Accessing a Device’s Native Features
Using Real IP Addresses for Example 2
After creating the VPN tunnel as described in “IPSec VPN Configuration for
Example 2” on page 385 or “PPTP VPN Configuration for Example 2” on
page 388, the user uses the OnBoard side IP address configured for the
appropriate private subnet to access the OnBoard, and then enables Native IP
access to the desired device.
Enabling Native IP Access
In this example, to enable native IP access on “sp1” or “sp2” on “sub1,” the
user would enter the OnBoard side IP address for “sub1” (which is
192.168.1.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://192.168.1.1.
• Chose the “Devices” left menu option.
• Select “sp1” or “sp2.”
• 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:192.168.1.1
ssh -t username:@192.168.1.1 menu
• Select “Access Devices” from the menu.
• Select either “sp1” or “sp2” from the devices menu.
route add -net 192.168.4.0 mask 255.255.255.0 via 192.168.2.1