Guys - I located the problem - using vlan://untagged for Public network is the cause of problem for me:
https://issues.apache.org/jira/browse/CLOUDSTACK-8451?focusedCommentId=14560646&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14560646 After 4.2 release, the broadcast URI was changed from NULL to vlan://untagged or something, and I rememeber this caused lot of other porblems as well. So my current workarround, is to allow ACS to use tagged Public network - but we should fix this if possible, since it's not related to systemvm/patches/debian/config/opt/cloud/bin/vpc_snat.sh or anythign similar . If anyone can reproduce the problem please... Thx On 19 May 2015 at 15:26, Ian Southam <isout...@schubergphilis.com> wrote: > > On 19 May 2015, at 09:30, Rohit Yadav <rohit.ya...@shapeblue.com<mailto: > rohit.ya...@shapeblue.com>> wrote: > > I think you’ve already figured out a workaround “SNAT all – * eth2 > 0.0.0.0/0 0.0.0.0/0 to:IP”, probably the fix needs to go into > "systemvm/patches/debian/config/opt/cloud/bin/vpc_snat.sh” (on 4.5 for > example) and usage of SetSourceNatCommand. > > OK, we should pop this not the 4.6 version too. > > Does it really need to be this permissive? > > — > Grts! > Ian > -- Andrija Panić
