Page History

...

API:

replaceNetworkACLList:

replaceNetworkACLList API taken from the support acl  deny rules FS \[1\].

...

Only one of above parameters is mandatory

API:

While creating private gateway we can map network acl id to the private gateway. For this a new param to createPrivateGateway API is added.

If acl id not passed then private gateway will be associated with default BLOCK acl id.

createPrivateGateway:

New parameter: 

aclid (otional) - Id of the network cal

Work Flow:

1. create private gateway
2. By While creating user can pass acl id to API, if not by default private gateway associated with default BLCOK networkACL
3. Add network ACL items into networkACL. These networkACL items (ACL rules) get applied to the private gateway.

DB Changes:

A new column 'gatewayId' is nework_acl_id' is added to the firewallvpc_rules gateways table.

itpables rules changes:

...

ACL_OUTBOUND_eth3 - This chain contains the all the EGRESS rules

UI changes:

1. UI change while creating private gateway.

Network-> Network-VPC -><vpcName> ->ConfigureVPC:<vpcname>PrivateGateway-><GatewayIp>>Add Private Gateway.

1. In Add new Private Gateway pop up add the  "Network ACL" drop down list.

   By default BLOCK acl id should be selected. User can change it by selecting item from the drop down. 

2. Add the 'Network ACL' tab beside the static route tab on the private gateway page.

   - Network ACL tab page shows the network acl associated with the private gateway. User can  also edit

     network acl id from this page. 

     When we click on the private gateway we have currently two tabs, 1. Details 2.Static Routes. Add NetworkACL tab after the static routes.

Upgrade:

On upgrade the for existing private gateways all the Ingress/Egress traffic is allowed which is to pertain the pre upgrade behavior.

...