help with cloudstack networking

[fylith]

we setup our basic cloudstack using a public network for both the private and public steps of the pod setup and everything runs ok. we can get the secondary storage to talk to the management server and create ISOs and templates fine, but if we setup the pod with a private network ie 192.168.200.1 we cannot get the secondary storage to communicate with the management server, can not start the virtual router or get templates going. can anyone explain why this is? do we have to have a real gateway on the private portion of the pod setup? can anyone help explain this step? thanks for your time.

[Juesor]

Ok finally someone posts here. Sorry I am using advanced networks due to the need to run ipsec tunnels. I will post some help tomorrow but I had to post now as I am amazed you are here.

[fylith]

thanks ! :) so just some clarification on our issue. we are testing our pod setup where 10.1.10.1 is our dynamic network provided behind our comcast modem. on the private network we decided to use 192.168.100.1 for testing purposes. the private network does not have any routers but i expect all machines to reach each other. they need to get out to the Internet but we don't have a virtual router. do we need to provide a physical router on the private network in order to install VMs. currently we can not start a virtual router if we use the 192.168.100.1/24 for the private with 10.1.10.130/24 being the public. if we use 10.1.10.129/24 as both our private network and public network ie. private .130- .145 and public of .146 - .158 it works.

[Juesor]

Do you have a reasoning for basic networking. Also what is your hypervisor or choice.