Ok, so if I understand what you are saying you should NAT the ports you
are using on the management server. As for those two public ranges
(216Š/27 & 29) you will need to configure those two networks on separate
VLANs (on WAN Switch) and configure them in the zone setup. Your physical
³Public² in
I really do not want to put the firewall in front of anything. I just want
to have my management server protected by the firewall (only allow incoming
traffic from specific static IPs to the management server). Otherwise I
want Cloudstack to handle all of the networking.
My ISP has provided a cr
So you will not be able to NAT the public IPs to the vRouter. If you do
NAT them it will become a mess for management, not to mention you reduce
the effectiveness of Cloudstack as a cloud management tool. You need to
expose that block to your WAN switch of which the public interface will
need to
n firewall and
> you'll see what your options are.
>
> Good luck
> Amin
>
>
>
> From: Fred Newtz
> To: users@cloudstack.apache.org
> Sent: Thursday, April 3, 2014 2:59 PM
> Subject: Public IP Addressing in a Advanced Zone b
ering. Click on firewall and you'll see what
your options are.
Good luck
Amin
From: Fred Newtz
To: users@cloudstack.apache.org
Sent: Thursday, April 3, 2014 2:59 PM
Subject: Public IP Addressing in a Advanced Zone behind a Firewall
Public IP addresses
Public IP addresses confuse me the most in a Cloudstack install. I have a
Firewall that is hosting all of my public IP addresses now. The management
server is supposed to sit behind a NAT device to protect it from attack.
How am I supposed to assign public IP addresses to virtual machines
(virtua
