Citrix Systems switch 4 Manual De Usuario

214

gateway to avoid IP conflicts. If Source NAT is enabled, the guest VMs in VPC reaches the enterprise
network via private gateway IP address by using the NAT service.

The Source NAT service on a private gateway can be enabled while adding the private gateway. On
deletion of a private gateway, source NAT rules specific to the private gateway are deleted.

To enable source NAT on existing private gateways, delete them and create afresh with source NAT.

The traffic on the VPC private gateway is controlled by creating both ingress and egress network ACL
rules. The ACLs contains both allow and deny rules. As per the rule, all the ingress traffic to the private
gateway interface and all the egress traffic out from the private gateway interface are blocked.

You can change this default behaviour while creating a private gateway. Alternatively, you can do the
following:

1.

In a VPC, identify the Private Gateway you want to work with.

2.

In the Private Gateway page, do either of the following:

• Use the Quickview. See 

• Use the Details tab. See 

3.

In the Quickview of the selected Private Gateway, click Replace ACL, select the ACL rule, then
click OK

4.

Click the IP address of the Private Gateway you want to work with.

5.

In the Detail tab, click the Replace ACL button. 

The Replace ACL dialog is displayed.

6.

select the ACL rule, then click OK.

Wait for few seconds. You can see that the new ACL rule is displayed in the Details page.

CloudPlatform enables you to specify routing for the VPN connection you create. You can enter one or
CIDR addresses to indicate which traffic is to be routed back to the gateway.

1.

In a VPC, identify the Private Gateway you want to work with.

2.

In the Private Gateway page, click the IP address of the Private Gateway you want to work with.

3.

Select the Static Routes tab.

4.

Specify the CIDR of destination network.

5.

Click Add.

Wait for few seconds until the new route is created.