Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
4.2.1
-
None
-
Security Level: Public (Anyone can view this level - this is the default.)
-
None
Description
Configuring PF on vm secondary ip failed for shared network with ip range 192.168.x.x
Attachments
Issue Links
- duplicates
-
CLOUDSTACK-6041 [Automation] Creating port forwarding rule for secondary IP (ranges - 172.16.x.x and 192.168.x.x) in Shared Network fails with "Invalid vm ip address"
- Resolved