How can I route all traffic to SonicWall NSv using the same address space (same VNet) and different subnet behind X0 interface?

Description

Image


IP Addresses used in this article



  SONICWALL NSv


VNET

10.5.0.0/16


VNET NAME

AzureNSvSonicWALL


WAN IP

X1 :10.5.0.4/24


LAN IP

X0: 10.5.1.4/24


AZURE LAN GW IP

10.5.1.1


AZURE INSTANCE

10.5.2.4/24


AZURE LAN

10.5.2.0/24


Resolution

  1. 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.Image

  2. Create a route table defining the resource group under Home  > Route tables.
    Note: SonicWall and virtual machine belong to the same resource group.
    Image

  3. Add route which will send any traffic to the next hop as 10.5.1.4 under Home > Route Tables > Azure_Traffic_via_X0.
    Image

  4. Associate the subnet to the route table by defining the virtual network AzureNSvSonicWALL and Subnet X0.
    Image

  5.  Create the Address Objects for this example:
    Image

    Image
  6. After configuring the above steps, create a route in SonicOS to reach LAN 10.5.2.0/24 subnet via X0 interface with gateway 10.5.1.1 (default IP of Azure LAN GW). 
            
             

 NOTE: A static NAT and an Access Rule would be required to access the locally hosted Virtual machine from WAN zone.  

 

Related Articles

  • What wireless cards and USB broadband modems are supported on firewalls and access points?
    Read More
  • How to export and import connection profiles in NetExtender
    Read More
  • Unable access High availability idle device using monitoring IP address
    Read More
not finding your answers?
was this article helpful?