[jira] [Commented] (CLOUDSTACK-9757) VPC traffic from vm to additional public subnet is not working

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902846#comment-15902846
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9757:


Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1922
  
@jayapalu can you fix the bug on 4.9 as well, send a PR? thanks.


> VPC traffic from vm to additional public subnet is not working
> --
>
> Key: CLOUDSTACK-9757
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9757
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Devices
>Reporter: Jayapal Reddy
>Assignee: Jayapal Reddy
> Fix For: 4.10.0.0
>
>
> 1. Add additional Public IP to Physical Network (specify a VLAN ID to isolate 
> traffic),
> 2. Create PortForward rule in VPC
> i) Acquire New IP , which used additional Public IP
> ii) Map a VM instance to use this Public IP
> 3. Observe that when VM ping additional public subnet then it is  not working
> For additional public subnet ip SNAT rules are not configured when 
> PF/Staticnat is configured. Due to this PF/StaticNAT VM traffic from to 
> additional public subnet is not SNATed to public ip.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9757) VPC traffic from vm to additional public subnet is not working

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15886889#comment-15886889
 ] 

ASF subversion and git services commented on CLOUDSTACK-9757:
-

Commit 48cbef6d248551a446e1e6a293001037e9cbb9a2 in cloudstack's branch 
refs/heads/master from [~rajanik]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=48cbef6 ]

Merge pull request #1922 from Accelerite/vpcApub

CLOUDSTACK-9757: Fixed issue in traffic from additional public subnetAcquire ip 
from additional public subnet and configure nat on that ip.
After this pick any from that network and access additional public subnet from 
this vm. Traffic is supposed to go via additional public subnet interface in 
the VR.

* pr/1922:
  CLOUDSTACK-9757: Fixed issue in traffic from additional public subnet

Signed-off-by: Rajani Karuturi 


> VPC traffic from vm to additional public subnet is not working
> --
>
> Key: CLOUDSTACK-9757
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9757
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Devices
>Reporter: Jayapal Reddy
>Assignee: Jayapal Reddy
> Fix For: 4.10.0.0
>
>
> 1. Add additional Public IP to Physical Network (specify a VLAN ID to isolate 
> traffic),
> 2. Create PortForward rule in VPC
> i) Acquire New IP , which used additional Public IP
> ii) Map a VM instance to use this Public IP
> 3. Observe that when VM ping additional public subnet then it is  not working
> For additional public subnet ip SNAT rules are not configured when 
> PF/Staticnat is configured. Due to this PF/StaticNAT VM traffic from to 
> additional public subnet is not SNATed to public ip.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9757) VPC traffic from vm to additional public subnet is not working

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15886888#comment-15886888
 ] 

ASF subversion and git services commented on CLOUDSTACK-9757:
-

Commit 48cbef6d248551a446e1e6a293001037e9cbb9a2 in cloudstack's branch 
refs/heads/master from [~rajanik]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=48cbef6 ]

Merge pull request #1922 from Accelerite/vpcApub

CLOUDSTACK-9757: Fixed issue in traffic from additional public subnetAcquire ip 
from additional public subnet and configure nat on that ip.
After this pick any from that network and access additional public subnet from 
this vm. Traffic is supposed to go via additional public subnet interface in 
the VR.

* pr/1922:
  CLOUDSTACK-9757: Fixed issue in traffic from additional public subnet

Signed-off-by: Rajani Karuturi 


> VPC traffic from vm to additional public subnet is not working
> --
>
> Key: CLOUDSTACK-9757
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9757
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Devices
>Reporter: Jayapal Reddy
>Assignee: Jayapal Reddy
> Fix For: 4.10.0.0
>
>
> 1. Add additional Public IP to Physical Network (specify a VLAN ID to isolate 
> traffic),
> 2. Create PortForward rule in VPC
> i) Acquire New IP , which used additional Public IP
> ii) Map a VM instance to use this Public IP
> 3. Observe that when VM ping additional public subnet then it is  not working
> For additional public subnet ip SNAT rules are not configured when 
> PF/Staticnat is configured. Due to this PF/StaticNAT VM traffic from to 
> additional public subnet is not SNATed to public ip.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9757) VPC traffic from vm to additional public subnet is not working

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15886890#comment-15886890
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9757:


Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/1922


> VPC traffic from vm to additional public subnet is not working
> --
>
> Key: CLOUDSTACK-9757
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9757
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Devices
>Reporter: Jayapal Reddy
>Assignee: Jayapal Reddy
> Fix For: 4.10.0.0
>
>
> 1. Add additional Public IP to Physical Network (specify a VLAN ID to isolate 
> traffic),
> 2. Create PortForward rule in VPC
> i) Acquire New IP , which used additional Public IP
> ii) Map a VM instance to use this Public IP
> 3. Observe that when VM ping additional public subnet then it is  not working
> For additional public subnet ip SNAT rules are not configured when 
> PF/Staticnat is configured. Due to this PF/StaticNAT VM traffic from to 
> additional public subnet is not SNATed to public ip.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9757) VPC traffic from vm to additional public subnet is not working

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15886887#comment-15886887
 ] 

ASF subversion and git services commented on CLOUDSTACK-9757:
-

Commit baac747089ef48ea6627a6aacf27156222862352 in cloudstack's branch 
refs/heads/master from Jayapal
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=baac747 ]

CLOUDSTACK-9757: Fixed issue in traffic from additional public subnet


> VPC traffic from vm to additional public subnet is not working
> --
>
> Key: CLOUDSTACK-9757
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9757
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Devices
>Reporter: Jayapal Reddy
>Assignee: Jayapal Reddy
> Fix For: 4.10.0.0
>
>
> 1. Add additional Public IP to Physical Network (specify a VLAN ID to isolate 
> traffic),
> 2. Create PortForward rule in VPC
> i) Acquire New IP , which used additional Public IP
> ii) Map a VM instance to use this Public IP
> 3. Observe that when VM ping additional public subnet then it is  not working
> For additional public subnet ip SNAT rules are not configured when 
> PF/Staticnat is configured. Due to this PF/StaticNAT VM traffic from to 
> additional public subnet is not SNATed to public ip.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9757) VPC traffic from vm to additional public subnet is not working

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15882575#comment-15882575
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9757:


Github user jayapalu commented on the issue:

https://github.com/apache/cloudstack/pull/1922
  
tag:mergeready


> VPC traffic from vm to additional public subnet is not working
> --
>
> Key: CLOUDSTACK-9757
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9757
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Devices
>Reporter: Jayapal Reddy
>Assignee: Jayapal Reddy
> Fix For: 4.10.0.0
>
>
> 1. Add additional Public IP to Physical Network (specify a VLAN ID to isolate 
> traffic),
> 2. Create PortForward rule in VPC
> i) Acquire New IP , which used additional Public IP
> ii) Map a VM instance to use this Public IP
> 3. Observe that when VM ping additional public subnet then it is  not working
> For additional public subnet ip SNAT rules are not configured when 
> PF/Staticnat is configured. Due to this PF/StaticNAT VM traffic from to 
> additional public subnet is not SNATed to public ip.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9757) VPC traffic from vm to additional public subnet is not working

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15880540#comment-15880540
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9757:


Github user ustcweizhou commented on the issue:

https://github.com/apache/cloudstack/pull/1922
  
LGTM as it is same to commit edd839ab10226760749d4fc15703a41eddc1dfdd
not tested yet, as VPC with RVR is working fine, so I assume this fixes the 
issue in VPC with single VR.




> VPC traffic from vm to additional public subnet is not working
> --
>
> Key: CLOUDSTACK-9757
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9757
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Devices
>Reporter: Jayapal Reddy
>Assignee: Jayapal Reddy
> Fix For: 4.10.0.0
>
>
> 1. Add additional Public IP to Physical Network (specify a VLAN ID to isolate 
> traffic),
> 2. Create PortForward rule in VPC
> i) Acquire New IP , which used additional Public IP
> ii) Map a VM instance to use this Public IP
> 3. Observe that when VM ping additional public subnet then it is  not working
> For additional public subnet ip SNAT rules are not configured when 
> PF/Staticnat is configured. Due to this PF/StaticNAT VM traffic from to 
> additional public subnet is not SNATed to public ip.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9757) VPC traffic from vm to additional public subnet is not working

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879989#comment-15879989
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9757:


Github user kishankavala commented on the issue:

https://github.com/apache/cloudstack/pull/1922
  
LGTM


> VPC traffic from vm to additional public subnet is not working
> --
>
> Key: CLOUDSTACK-9757
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9757
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Devices
>Reporter: Jayapal Reddy
>Assignee: Jayapal Reddy
> Fix For: 4.10.0.0
>
>
> 1. Add additional Public IP to Physical Network (specify a VLAN ID to isolate 
> traffic),
> 2. Create PortForward rule in VPC
> i) Acquire New IP , which used additional Public IP
> ii) Map a VM instance to use this Public IP
> 3. Observe that when VM ping additional public subnet then it is  not working
> For additional public subnet ip SNAT rules are not configured when 
> PF/Staticnat is configured. Due to this PF/StaticNAT VM traffic from to 
> additional public subnet is not SNATed to public ip.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9757) VPC traffic from vm to additional public subnet is not working

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879850#comment-15879850
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9757:


GitHub user jayapalu reopened a pull request:

https://github.com/apache/cloudstack/pull/1922

CLOUDSTACK-9757: Fixed issue in traffic from additional public subnet

Acquire ip from additional public subnet and configure nat on that ip.
After this pick any from that network and access additional public subnet 
from this vm. Traffic is supposed to go via additional public subnet interface 
in the VR.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Accelerite/cloudstack vpcApub

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1922.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1922


commit 0645cbe14c33c8271bd2f13785288c0be0c8038c
Author: Jayapal 
Date:   2017-02-22T10:50:48Z

CLOUDSTACK-9757: Fixed issue in traffic from additional public subnet




> VPC traffic from vm to additional public subnet is not working
> --
>
> Key: CLOUDSTACK-9757
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9757
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Devices
>Reporter: Jayapal Reddy
>Assignee: Jayapal Reddy
> Fix For: 4.10.0.0
>
>
> 1. Add additional Public IP to Physical Network (specify a VLAN ID to isolate 
> traffic),
> 2. Create PortForward rule in VPC
> i) Acquire New IP , which used additional Public IP
> ii) Map a VM instance to use this Public IP
> 3. Observe that when VM ping additional public subnet then it is  not working
> For additional public subnet ip SNAT rules are not configured when 
> PF/Staticnat is configured. Due to this PF/StaticNAT VM traffic from to 
> additional public subnet is not SNATed to public ip.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9757) VPC traffic from vm to additional public subnet is not working

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879849#comment-15879849
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9757:


Github user jayapalu closed the pull request at:

https://github.com/apache/cloudstack/pull/1922


> VPC traffic from vm to additional public subnet is not working
> --
>
> Key: CLOUDSTACK-9757
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9757
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Devices
>Reporter: Jayapal Reddy
>Assignee: Jayapal Reddy
> Fix For: 4.10.0.0
>
>
> 1. Add additional Public IP to Physical Network (specify a VLAN ID to isolate 
> traffic),
> 2. Create PortForward rule in VPC
> i) Acquire New IP , which used additional Public IP
> ii) Map a VM instance to use this Public IP
> 3. Observe that when VM ping additional public subnet then it is  not working
> For additional public subnet ip SNAT rules are not configured when 
> PF/Staticnat is configured. Due to this PF/StaticNAT VM traffic from to 
> additional public subnet is not SNATed to public ip.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9757) VPC traffic from vm to additional public subnet is not working

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877983#comment-15877983
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9757:


Github user jayapalu commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1922#discussion_r102432766
  
--- Diff: server/src/com/cloud/network/router/CommandSetupHelper.java ---
@@ -703,6 +722,10 @@ public void createVpcAssociatePublicIPCommands(final 
VirtualRouter router, final
 sourceNatIpAdd = new Pair(ip, 
ipAddr.getNetworkId());
 addSourceNat = add;
 }
+
+if (!firstIP || add) {
+firstIP = false;
+}
--- End diff --

for additional public subnet on delete it is not sure which ip is set to 
first ip. So on delete we want to set sourcenat to true for all ips to delete 
source nat rules. 

@ramkatru 
I will add above comment.


> VPC traffic from vm to additional public subnet is not working
> --
>
> Key: CLOUDSTACK-9757
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9757
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Devices
>Reporter: Jayapal Reddy
>Assignee: Jayapal Reddy
> Fix For: 4.10.0.0
>
>
> 1. Add additional Public IP to Physical Network (specify a VLAN ID to isolate 
> traffic),
> 2. Create PortForward rule in VPC
> i) Acquire New IP , which used additional Public IP
> ii) Map a VM instance to use this Public IP
> 3. Observe that when VM ping additional public subnet then it is  not working
> For additional public subnet ip SNAT rules are not configured when 
> PF/Staticnat is configured. Due to this PF/StaticNAT VM traffic from to 
> additional public subnet is not SNATed to public ip.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9757) VPC traffic from vm to additional public subnet is not working

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15874305#comment-15874305
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9757:


Github user ramkatru commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1922#discussion_r101983289
  
--- Diff: server/src/com/cloud/network/router/CommandSetupHelper.java ---
@@ -703,6 +722,10 @@ public void createVpcAssociatePublicIPCommands(final 
VirtualRouter router, final
 sourceNatIpAdd = new Pair(ip, 
ipAddr.getNetworkId());
 addSourceNat = add;
 }
+
+if (!firstIP || add) {
+firstIP = false;
+}
--- End diff --

Please add a comment explaining this. Not very readable.



> VPC traffic from vm to additional public subnet is not working
> --
>
> Key: CLOUDSTACK-9757
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9757
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Devices
>Reporter: Jayapal Reddy
>Assignee: Jayapal Reddy
> Fix For: 4.10.0.0
>
>
> 1. Add additional Public IP to Physical Network (specify a VLAN ID to isolate 
> traffic),
> 2. Create PortForward rule in VPC
> i) Acquire New IP , which used additional Public IP
> ii) Map a VM instance to use this Public IP
> 3. Observe that when VM ping additional public subnet then it is  not working
> For additional public subnet ip SNAT rules are not configured when 
> PF/Staticnat is configured. Due to this PF/StaticNAT VM traffic from to 
> additional public subnet is not SNATed to public ip.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9757) VPC traffic from vm to additional public subnet is not working

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15873871#comment-15873871
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9757:


Github user cloudmonger commented on the issue:

https://github.com/apache/cloudstack/pull/1922
  
### ACS CI BVT Run
 **Sumarry:**
 Build Number 361
 Hypervisor xenserver
 NetworkType Advanced
 Passed=105
 Failed=0
 Skipped=7

_Link to logs Folder (search by build_no):_ 
https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0


**Failed tests:**

**Skipped tests:**
test_01_test_vm_volume_snapshot
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_11_ss_nfs_version_on_ssvm
test_nested_virtualization_vmware
test_3d_gpu_support
test_deploy_vgpu_enabled_vm

**Passed test suits:**
test_deploy_vm_with_userdata.py
test_affinity_groups_projects.py
test_portable_publicip.py
test_over_provisioning.py
test_global_settings.py
test_scale_vm.py
test_service_offerings.py
test_routers_iptables_default_policy.py
test_loadbalance.py
test_routers.py
test_reset_vm_on_reboot.py
test_deploy_vms_with_varied_deploymentplanners.py
test_network.py
test_router_dns.py
test_non_contigiousvlan.py
test_login.py
test_deploy_vm_iso.py
test_list_ids_parameter.py
test_public_ip_range.py
test_multipleips_per_nic.py
test_regions.py
test_affinity_groups.py
test_network_acl.py
test_pvlan.py
test_volumes.py
test_nic.py
test_deploy_vm_root_resize.py
test_resource_detail.py
test_secondary_storage.py
test_vm_life_cycle.py
test_routers_network_ops.py
test_disk_offerings.py


> VPC traffic from vm to additional public subnet is not working
> --
>
> Key: CLOUDSTACK-9757
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9757
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Devices
>Reporter: Jayapal Reddy
>Assignee: Jayapal Reddy
> Fix For: 4.10.0.0
>
>
> 1. Add additional Public IP to Physical Network (specify a VLAN ID to isolate 
> traffic),
> 2. Create PortForward rule in VPC
> i) Acquire New IP , which used additional Public IP
> ii) Map a VM instance to use this Public IP
> 3. Observe that when VM ping additional public subnet then it is  not working
> For additional public subnet ip SNAT rules are not configured when 
> PF/Staticnat is configured. Due to this PF/StaticNAT VM traffic from to 
> additional public subnet is not SNATed to public ip.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)