I do have rules for this on my first machine in iptables which worked
fine before we installed the management server.
As I didn't find a firewall to onfigure in the admin web ui of
cloudstack, i'm guessing it's because our setup so far isn't right.
As i described we have different IP adresses for our physical machines
and for the vms.
and i'm not sure what alle the expected gateways in pods etc are for.
please help =/
Am 01.06.2013 00:04, schrieb Ahmad Emneina:
what you can do is setup a NAT rule and poke a hole in the firewall to
allow access to the vm's from the internet.
On Fri, May 31, 2013 at 1:55 PM, A S <darksister...@yahoo.de> wrote:
As I hadn't subscribed before, I'm not sure, if this message did reach you.
-------- Original-Nachricht --------
Betreff: need help with network setup
Datum: Fri, 31 May 2013 22:21:56 +0200
Von: A S <darksister...@yahoo.de>
An: users@cloudstack.apache.org
Hi,
me and my group are trying to setup cloudstack as an project for
university.
We plan to use three physical servers for the cloud which are at the
university.
Only the one which is acting as the management server has direct accces
to the internet.
So he acts as a gateway for the other two machines.
The three machines have private ips : 192.168.0.x
The VMs should use private ips: 10.100.x.y
For "public" Ips whe have 10.90.x.y. Only reachable via vpn to our
university.
We are struggling to find the right configuration for our network.
We only want one zone, one pod and one cluster.
But the basic setup manager in the tour of the web ui is not happy with
a gateway with a 192.168.0.x address and and ip range with adresses from
10.100.x.y, for example.
How can we solve this?
And it seems like the cloudstack firewall prevents the first machine
acting as a gateway for the other two machines, which don't have
internet acces, so we can't access the machines via internet.
Thank for your help!
