In one OS, LInux or Windows ,you can only one Main Network, (with Default Gateway) , others is secondary IP (no matter is dedicated NIC or shared NIC)
If you have two network , you have to choose ONE as default / main . You cannot have two. In Linux, you can have two gateway, but that is not going to discuss here. or it is not common way of doing . Some doing it for specific purpose. On Tue, Sep 22, 2020 at 12:07 AM Rafael del Valle <rva...@privaz.io.invalid> wrote: > Andrija, > > I was reading your blog posts. I quote: > > "In public clouds, the public networks will most likely be publicly > routable IP ranges. However, for enterprises these may be either > publicly routable or RFC 1918 (internal) IP ranges." > > This is exactly what I was asking about. What happens if in an Enterprise > deployment you have both categories? > > * IP Addresses that are "publicly routable" > * RFC 1928 (internal) IP ranges (north of cloudstack). > How can you deal with 2 types of "public IPs" within ACS? > > > Rafael > > > > > On Fri, 2020-09-11 03:16 PM, Andrija Panic <andrija.pa...@gmail.com> > wrote: > > I'm not sure that I have got all your points (after a very quick read), > but > > I can advise on the following: > > > > " But Cloudstack complaints if I try to create 2 public networks on the > > same zone" > > > > This is only true of they are overlapping - or having the same gateway, > etc. > > Make sure to have each Public network on a separate VLAN (even though not > > required technically in the real world, it is required by ACS) > > That would allow you to run multiple Public network ranges > > > > best, > > > > On Mon, 7 Sep 2020 at 10:31, Rafael del Valle " > target="_blank"><rva...@privaz.io.invalid> > > wrote: > > > > > Hi! > > > > > > We have multiple public networks, and we would like to model them in > ACS. > > > > > > We find references in the Documentation that seem to suggest it is > > > possible: such as creating network offerings with a tag meant to > identify > > > the physical network. > > > > > > There are several use cases for which we want this: fail tolerance > > > between different connectivity providers, creating instances/networks > > > accessible from corporate network hosting ACS only, etc. > > > > > > Currently the public networks are on different VLANs, accessible trough > > > the same network card (which ACS refers to as physical nets). > > > > > > I can see that the Physical Network has a TAG, and the docs seem to > imply > > > that a tag can be used to identify the public network. But Cloudstack > > > complaints if I try to create 2 public networks on the same zone. > > > > > > The most intuitive solution would be to tag the vlan_ip_range and > create > > > network offerings that pick IPs with a given tag, but they don't seem > to > > > take tags. > > > > > > I can assign IPs from different providers to an account, and they can > > > manually create network/VMs using them. But there seems to be no way to > > > tell ACS that I want a VM/IP assignment on connectivity provider A/B, > or > > > use affinity rules, etc. > > > > > > How is this done with ACS? Is it possible? > > > > > > Rafael > > > > > > > > > > > > > > > > > > > > > > -- > > > > Andrija Panić > > -- Regards, Hean Seng
