
Appendices 195
• The target device named sp4 with IP 192.168.4.22 does not work with virtual network (DNAT)
addressing, so it cannot be contacted using a virtual IP address. Therefore, the administrator
does not assign sp4 a virtual IP.
To make it possible to assign the virtual addresses shown in Figure C.3, the SP manager’s
administrator must configure a virtual network with the following values:
• Address: A virtual address from the desired virtual address range to assign to the SP manager,
in this case: 172.20.0.1
• Netmask: 255.255.0.0
Finally, the administrator also must configure the target devices that support virtual addressing with
a virtual address from the 172.20.0.0 virtual network IP range. In this example, virtual IP address
172.20.0.2 is assigned to the target device sp1 on the Web Manager Config Target Devices screen
to implement the configuration. On the Target Devices screen, the IP addresses for sp1, sp2, and
sp3 are hidden, and the user can only see the target devices’ virtual IP addresses. Because sp4 does
not work with virtual IPs and no virtual IP was configured for sp4, the user sees sp4’s real IP
address.
IPSec VPN configuration for example 3
After the private subnets, target device and user account configuration in Virtual network and
target device configuration for example 3 on page 194 is completed, a VPN connection must be
created. With a virtual network, only one IPSec VPN connection must be configured to create the
IPSec VPN tunnel from the user’s workstation to sp1, sp2 and sp3, which are on both private
subnets in example 3.
Configuration of connSub2 would be still be needed as in IPSec VPN configuration for example 2
on page 188, because the only way a user could contact sp4 would be through the private subnet IP.
The values used for enabling an IPSec VPN connection are the same as in IPSec VPN configuration
for example 2 on page 188, except the SP manager’s administrator must configure the Left subnet:
by entering 172.20.4.0/22 to configure the connection to the virtual network.
As in the earlier example, the administrator must perform the following actions to enable the IPSec
client to access the subnets where the target devices reside:
• Give the user a copy of the parameters used to configure the IPSec connection profiles on
the SP manager.
The administrator can send a copy of the relevant portions of the ipsec.conf file after the
changes are saved and applied in the Web Manager for the user to insert into the ipsec.conf file
on the user’s workstation.
The authorized user must perform the following configuration to enable the IPSec client running on
the user’s workstation to bring up the VPN tunnel to access the subnets where the target devices
reside and then to access the native IP features on the target devices.
• Use the same values used by the SP manager’s administrator to create an IPSec VPN
connection profile on the user’s workstation.
Kommentare zu diesen Handbüchern