-and-different-subnet-behind-X0-interface--kA1VN0000000Gsn0AE-0EMVN00000Enqwj.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 LAN GW IP | 10.5.1.1 | |
AZURE INSTANCE | 10.5.2.4/24 | |
AZURE LAN | 10.5.2.0/24 | |
-and-different-subnet-behind-X0-interface--kA1VN0000000Gsn0AE-0EMVN00000EnqxF.jpg)
-and-different-subnet-behind-X0-interface--kA1VN0000000Gsn0AE-0EMVN00000Enqwl.png)
-and-different-subnet-behind-X0-interface--kA1VN0000000Gsn0AE-0EMVN00000Enqwk.png)
-and-different-subnet-behind-X0-interface--kA1VN0000000Gsn0AE-0EMVN00000Enqwh.png)
-and-different-subnet-behind-X0-interface--kA1VN0000000Gsn0AE-0EMVN00000Enqwi.png)
-and-different-subnet-behind-X0-interface--kA1VN0000000Gsn0AE-0EMVN00000Enqwn.png)
NOTE: A static NAT and an Access Rule would be required to access the locally hosted Virtual machine from WAN zone.