How do I route all traffic to SonicWall NSv using the same address space (same VNet) and same subnet?

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 INSTANCE

          10.5.1.5/24

 

 

Resolution

  1. Create a virtual machine (10.5.1.5/24) which uses the same address space (same resource group) behind X0 interface of SonicWall 10.5.1.5/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 belongs to same resource group.
    Image

  3. Add a 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

 

NOTE: Deploy a virtual appliance into a different subnet than the resources that route through the virtual appliance.

CAUTION: Deploying the virtual appliance to the same subnet, then applying a route table to the subnet that routes traffic through the virtual appliance, can result in routing loops, where traffic never leaves the subnet.

Related Articles

  • Remediation Playbook
    Read More
  • How To change the SSO PSK
    Read More
  • How do I SSH into a SonicWall NSv Azure using SSH key pair?
    Read More
not finding your answers?
was this article helpful?