Actually this is not quite true. You can design a network offering with no NAT or firewall services and give a public range of ips for the network. Or you (the admin) can utilize the default 'shared network' offering to create a similar network on a specific VLAN.
On 8/13/13 7:03 AM, "Nguyen Anh Tu" <ng.t...@gmail.com> wrote: >2013/8/13 Mark van der Meulen <m...@vdm.id.au> > >> Are you saying that the only way CloudStack supports public(read: >>networks >> outside immediate pod) access is via NAT? Can I not give the VM's >>publicly >> routable IP's(or equivalent for the network)? > > >Hi Mark, > >At the moment Cloudstack only supports public access via NAT (staticNat or >sourceNat). For using Route instead of NAT, I made a small patch. You can >find the reference here: >https://cwiki.apache.org/confluence/display/CLOUDSTACK/Routing+between+Gue >st+networks > > >-- > >N.g.U.y.e.N.A.n.H.t.U
