disassociate & delete all NSGs except the WinTest1 VM's.

I deployed a RouterOS (CHRVM) too and prepared the environment: (The Public IPs and NSGs are not mandatory.) Route traffic between Subnet1 and Subnet2 with RouterOS

Public IP (WinTest1-ip & WinTest2-ip) it allows to access to the resource from the internet.

It's like a simple client endpoint firewall. Network Security Group (WinTest1-nsg & WinTest2-nsg) The Network Security Groups help to control the inbound and outbound traffic.Virtual Network Interface (wintest1867 & wintest2207).As you can see in the picture there are some more (auto-generated) resources: I created two subnets (subnet1 & subnet2) and one VM in each subnet (WinTest1 & WinTes2). The traffic across the subnets in the VNet is routed by default, so the resources in different subnets can communicate. Only do static assignment of a private IP when it's necessary, such as when assigning many IP addresses to VMs. In case of virtual machines you have to configure static IP address from the Azure Portal instead of from the VM's operation system. It provides the IP addresses to the resources. With subnets you can create one or more segments in your address space.Įach subnet has a DHCP server which cannot configurable. Azure Virtual Network (VNet) is a resource which defines IP address space and subnets. In Azure, it doesn't work that you connect WAN network cable to ether1 and LAN network to ether2, configure IP addresses and set a NAT or route and you are happy, because this is cloud and Azure use SDN (sofware-defined-network) so it's a littlebit more complicated.įirst, you have to configure a virtual network to connect and access anything. But I didn't explain how to use it as a router or in other roles.

In my previous article I presented how to deploy MikroTik CHR in Microsoft Azure: Run RouterOS in Azure.

Mikrotik chr azure