You should acquire a new public ip for the isolated network. Then you can configure firewall, portforwarder or loadbalancer on that ip. You are not limited to use a single public ip in isolated network.
On Wed, Jun 2, 2021, 13:39 Jeremy Hansen <jer...@skidrow.la> wrote: > I’m working through my initial setup of Cloudstack. I added a second vm > host so I could test live migration. Worked out the vlan kinks and that’s > now working great. > > I launched a second guest and noticed it did not allocate a new public > IP. My expectation was that it would allocate another public IP from the > range I defined and the second instance would have its own virtual > router/firewall/port forwarding, etc, but that doesn’t seem to be the > case. I can configure the firewall on the existing virtual router to port > forward to the second instance, but I’d prefer it just allocate another > public IP from the range and allow me to configure each instance as a > separate entity without port conflicts. Is this possible? > > Thanks > -jeremy >
