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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.10.0.0
• Component/s: Network Devices
• Security Level: Public (Anyone can view this level - this is the default.)
• Assignee: Jayapal
• Reporter: Jayapal
• Created: 25/Jan/17 11:14
• Updated: 25/May/17 10:21
• Resolved: 25/May/17 10:21

Description

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.

Issue Links

• links to: GitHub Pull Request #1922