- Print
- DarkLight
Supported Networking Scenarios
Overview
This document is designed to help you understand and configure the networking options for CloudLabs VM Labs. CloudLabs offers two networking options for lab VMs: default networking and advanced networking. This document explains the features, benefits, and limitations of each option and how to configure them for different networking scenarios.
CloudLabs Default Networking
Default networking is the simplest and most convenient option for CloudLabs VM Labs. It does not require any setup or configuration from the lab admin. CloudLabs will automatically create the required network, subnet, IP address, and firewall rules for each lab VM. The lab VMs will be isolated from each other and other resources in the Azure subscription. The lab VMs will have full internet access with CloudLabs-managed DNS.
Some of the benefits of default networking are:
It is easy to use and does not require any networking knowledge or skills.
It is secure and prevents unauthorized access to the lab VMs or other resources.
All VMs are configured to run on their private networks so that no machines can access each other.
It is scalable and can handle any number of lab VMs without affecting performance or availability.
Some of the limitations of default networking are:
It does not allow any customization or flexibility for the lab network IP range.
It does not support any communication or integration between the lab VMs and other resources in Azure, on-premises, etc.
It does not support any advanced networking scenarios or topologies.
You should use default networking when:
You want to create a simple and isolated lab environment for your users.
You do not need any communication or integration between the lab VMs or any other private resources.
To use default networking, when you create a lab, do not select the advanced networking option, or your lab will be created with the default network automatically.
Advanced Networking
Advanced networking is an optional and powerful feature for CloudLabs VM Labs. It allows the CloudLabs admins to create one or more custom networks of their choice of IP range and deploy their lab VMs in those networks. The lab VMs will have full internet access by default unless restricted intentionally. The lab VMs can also communicate with other VMs or resources in the same or different networks, depending on the NSG rules and the network connectivity options.
Some of the benefits of advanced networking are:
It allows you to customize and optimize the lab network settings, including the IP address range, according to your needs and preferences.
It supports various communication and integration scenarios and topologies between the lab VMs and other resources in your organization, such as Azure, on-premises, or other network resources.
It enables you to route the lab traffic via your network infrastructure and perform additional traffic filtering.
Some of the limitations of advanced networking are:
It requires some networking knowledge and skills to set up and manage.
It may incur additional costs for creating and using custom networks and hybrid connectivity options, such as VPN Gateway, etc.
It may introduce some security risks or challenges if not configured properly or securely.
You should use advanced networking when:
You need to communicate or integrate the lab VMs with other resources in Azure, on-premises, or on other networks.
You have some specific networking requirements or preferences for your lab, as documented in the example scenarios below.
You require VM labs to be able to communicate with each other.
Networking Scenarios
The following table lists common networking scenarios and topologies and their support in CloudLabs.
Scenario | Default Networking | Advanced Networking | Details |
Internet Access | Yes | Yes | Full Internet access is enabled by default for all networking configurations. |
Lab-to-lab communication | No | Yes | Enables network communication between lab users and virtual machines. |
Open additional ports to the lab VM | Yes | Yes | By default, RDP/SSH/VNC ports are allowed for inbound traffic based on your lab OS. If you wish to allow additional ports, Please contact support for customizing ports for your virtual machines. |
Custom Private IP Range for Lab VMs | No | Manual by CloudLabs Admins | You will have the opportunity to customize your IP range with advanced networking. |
Enable license server or any other server/network access from Lab VMs | No | Yes | If you wish to have your lab virtual machines access to your own Azure networks, hosted in your own Azure subscriptions for accessing any machine, such as license server, etc. In that case, it is supported by advanced networking. Please follow the advanced networking configuration guide for more setup information. Similarly, network access to on-prem resources is also supported via advanced networking through site-to-site VPN connectivity. Please contact support for setting up hybrid connectivity. |
Access Lab VMs by Private IPs | No | Yes (Not Recommended) | This scenario is functional but makes it difficult for lab users to connect to their lab VM. Please contact support for more information. |
Customized Network Traffic Routing | No | Yes | With Advanced Networking, you can customize internet traffic for your Lab VMs, allowing you to filter traffic through proxy/firewall etc., for content filtering, etc. Please contact support for more information. |
Content Filter-DNS or Agent-Based | Yes | Yes | Content filtering is supported by the following options:
|
Content Filter-Network Proxy or Routing Based | No | Yes | Content filtering works with advanced networking if the lab VMs can use a customer-provided proxy server that supports content filtering or configure a customer-defined network routing via a firewall/appliance, etc. |
Content Filter-CloudLabs Managed | Yes | Yes | CloudLabs-managed content filtering is supported. Please contact support for setup. |
Cyber field scenario, consisting of a set of vulnerable VMs on the network for lab users to discover and hack into (ethical hacking) | Yes | Yes | Supported via nested virtualization labs with Hyper-V Virtual Network technologies. See Nested Virtualization for more information. |
Enable using Azure Bastion for lab VMs | Not Required | Not Required | CloudLabs VM Labs includes in-browser RDP and SSH access and does not require Bastion Service. |