Andrija, Thanks for the clarification. I found it confusing at first that "public" refers in reality to external to cloudstack, be it corporate intranet or public internet.
I understand that know. What I am still trying to achieve is a way to differentiate/manage external IPs of the different types ACS can manage. I.e. My couldstack has now 3 different of external/public IPs. * Local fiber provider range which supports IPV4 only * IPs from an SDWan that also support IPV6 * A local network that we call GuestAdmin, that administrators of ACS Projects can access via externally provided VPN fir the purpose. SSVMs are here. Each of them sets on a different VLAN. Now I have added all as Public, using different VLAN-IP-RANGE. And it is working just fine. The only drawback is that we need know what type of IP is each, as I cannot find a way to label, group or differentiate this IPs within ACS. I think ACS does not have any functionality yet to help with this use case, does it? Regarsds, Rafael On Thu, 2020-10-08 12:39 PM, Andrija Panic <[email protected]> wrote: > Rafael, > > re your last email - this is only saying that CLoudStack Public network can > have either "a real public / publicly routable" IP address range, or some > other private Ip range - but both of those are, so to speak, external to > CloudStack - and whatever the IP (range) defined fort the cloudstack > "Public" network - those IP (be it really public or private) will be > attached to VR only. > > Using Isolated network offering - has NOTHING to do with the "public" > network. The Isolated network is a network on VR's internal interfaces, > between the VR and VMs in that Isolated, while the CloudStack "public" > network is the network/IP of the external NIC (publicly facing NIC) of the > VR. > > Let me know if you need more clarification > > Best, >
