cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajani Karuturi (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-4442) Source NAT not applied when network starts up
Date Thu, 30 Jul 2015 04:24:04 GMT


Rajani Karuturi commented on CLOUDSTACK-4442:

I am not able to reproduce this in the current master(4.6). Here are the steps I followed

1. create a network offering with the following services. Dhcp: VirtualRouter, SourceNat:
VirtualRouter, Dns: VirtualRouter
2. create a network with the above offering. The network is in Allocated state.
3. launch a vm in the network
4. The network goes to implemented state source nat ip acquired and vm instance creation is
5. access the console of the vm created in step 3 and ping Its successful
[root@VM-adf92598-2745-4203-80b0-1bdb28fdfdb6 ~]# ping
PING ( 56(84) bytes of data.
64 bytes from ( icmp_seq=1 ttl=43 time=287 ms
64 bytes from ( icmp_seq=2 ttl=43 time=277 ms

--- ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 277.868/282.457/287.046/4.589 ms
6. list the nat rules on the VR. I could see one for the source nat ip of the network.
pkts bytes target     prot opt in     out     source               destination
   12   862 SNAT       all  --  *      eth2              to:

> 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
>            Reporter: Dave Cahill
>            Assignee: Rajani Karuturi
>            Priority: Blocker
>             Fix For: 4.6.0
> 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 was sent by Atlassian JIRA

View raw message