At Clouding you have both access to the public network -the internet- as well as being able to use a private network, to which only your servers have access to exchange information between them.
All cloud servers include a network interface connected to the public Clouding network.
- Public IP: this interface has a fixed and exclusive public IP configured for your cloud server, which will always be assigned to you as long as the server exists.
- Measured traffic: the traffic that you send or receive through this interface will be considered public traffic and, such your monthly traffic volume can be discounted.
- Unsecured traffic: the internet is an unsecured network and, therefore, the traffic you receive on the public network cannot be considered secure.
- Non-isolated traffic: we use various advanced techniques to prevent your traffic from being seen by other Cloud Servers hosted in Clouding, but in some situations - for example due to configuration errors - this traffic can be seen by other equipment.
If your Clouding account has two or more servers, you can use a single private network at no additional cost.
- Private IP: this interface has a private IP configured by default, which you can change if you wish and use any private IP range.
- Unmeasured traffic: traffic on this network is never counted, it is totally unlimited and your monthly traffic volume is not discounted.
- Secure traffic: Only your cloud servers hosted on Clouding have access to this private network, therefore it is ideal for exchanging sensitive or confidential traffic between your servers.
- Isolated traffic: each private network is totally isolated from the rest of the networks hosted in Clouding, therefore it's not necessary for you to use encrypted protocols when sharing data between your servers through this network.
How does it work?
When an Ethernet packet leaves your Cloud Server, we assign an 802.3ac ethernet tag, which is done immediately after the packet leaves your server.
Using that tag to identify it while it is in the source hypervisor, it goes to a VXLAN tunnel based on the destination hypervisor. When it reaches the VXLAN, the 802.3ac tag is changed to the VNID assigned to your customer account and the package is sent to the destination hypervisor. There, an 802.3ac tag is used again to isolate it from the rest of the traffic until it is delivered to your other cloud server, now as as a normal package.