-and-same-subnet--kA1VN0000000HCC0A2-0EMVN00000Ensxo.png)
| 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 | |
-and-same-subnet--kA1VN0000000HCC0A2-0EMVN00000EnsxS.png)
-and-same-subnet--kA1VN0000000HCC0A2-0EMVN00000Ensxq.png)
-and-same-subnet--kA1VN0000000HCC0A2-0EMVN00000Ensxn.png)
-and-same-subnet--kA1VN0000000HCC0A2-0EMVN00000Ensxb.png)
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.