cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Murali Reddy (JIRA)" <>
Subject [jira] [Updated] (CLOUDSTACK-4442) Source NAT not applied when network starts up
Date Wed, 28 Aug 2013 07:41:53 GMT


Murali Reddy updated CLOUDSTACK-4442:

    Fix Version/s:     (was: 4.2.0)
> Source NAT not applied when network starts up
> ---------------------------------------------
>                 Key: CLOUDSTACK-4442
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Devices
>    Affects Versions: 4.2.0
>            Reporter: Dave Cahill
>            Assignee: Murali Reddy
>            Priority: Blocker
>             Fix For: Future
> Create a network with Source NAT but no static NAT, and no firewall rules applied.
> Observed behavior:
> Source NAT is not applied when the first VM is launched (when network is implemented)
> Expected:
> Source NAT enabled at network implement time
> Network devices:
> Should affect all network devices; verified in 2 separate environments, one with Virtual
Router only, one MidoNet only
> Further information:
> This bug seems to be a result of this change:
> The above change was made as a fix for CLOUDSTACK-234.
> If the user enables Static NAT, Source NAT will be applied as a side effect.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message