Cyclades AlterPath OnBoard, Руководство администратора

Страница: 401 / 460

Appendix A: Advanced Device Configuration 365
Understanding Address Configuration for Connected Devices
The next bulleted items shows how to create an appropriate route to the virtual
network.
• Create a static route to inform the workstation that the devices to be
contacted are at the other end of the point-to-point link.
In this example, to communicate with “sp1,” “sp2,” and “sp3,” a route
would needed to the virtual network whose IP address is
172.20.0.0
as shown below:
To communicate with “sp4”, because it cannot be contacted through a
virtual network IP address, the same route mentioned in “PPTP VPN
Configuration for Example 2” on page 352 would be needed to “sub2,”
which has the network IP address 192.168.4.1 as shown below:
• Enable native IP and access the device’s native features.
Enabling native IP and accessing the device’s native features is the same as
described under “Enabling Native IP and Accessing a Device’s Native
Features Using Real IP Addresses for Example 2” on page 355.
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 362 or “PPTP VPN Configuration for Example 3” on
page 364, 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 355.
route add -net 172.20.0.0 mask 255.255.0.0 via 192.168.2.1
route add -net 192.168.4.1 mask 255.255.252.0 via 192.168.2.1