How can I route all traffic to SonicWall NSv using the same address space (same VNet) and different subnet behind X0 interface?
03/26/2020 1 6091
IP Addresses used in this article
- Create a virtual machine (10.5.2.4/24) which is using the same address space (same resource group) but different subnet behind X0 interface of SonicWall 10.5.1.4/24 and X1 interface of SonicWall 10.5.0.4/24.
- Create a route table defining the resource group under Home > Route tables.
Note: SonicWall and virtual machine belong to the same resource group.
- Add route which will send any traffic to the next hop as 10.5.1.4 under Home > Route Tables > Azure_Traffic_via_X0.
- Associate the subnet to the route table by defining the virtual network AzureNSvSonicWALL and Subnet X0.
NOTE: After configuring please create a route in the SonicWall to reach 10.5.2.0/24 subnet via X0 of SonicWall with gateway as 10.5.1.1.
The local hosted Virtual machine will not be accessed through the Public is, so a static NAT is required to access the virtual machine via WAN and an access rule.