Sonic Wall + Azure VPN

vince-p · 2015-07-12T20:10:26.000Z

I’m trying to set up VPN network connection between my sonic wall nsa 220 and Azure.

I have the tunnel going, but the traffic going to and fro is practically nothing 128 bytes in and 0 out.

The documentation by Sonic Wall was pretty bad and I had to improvise just to get the tunnel open.

I have a address object for the azure network that i’m pretty sure falls under my permit firewall rules, not sure about the azure gateway though, and not sure if I have to set up Routing or NAT.

I used the Azure Static Gateway.

vpn.JPG800×356 80.7 KB

psophos · 2015-07-12T20:22:20.000Z

What traffic are you sending over the link?

If you have a server running in Azure can you traceroute to it from your internal network?

You should not need to set up NAT but you need to make sure that the VNET in Azure and your internal network don’t overlap, or put an exclusion in for your internal network on the Azure side. You tell Azure what IP space your on premises network uses.

Routing might be needed, depending on the setup. The internal net needs to go to the firewall for the Azure internal networks.

Neally · 2015-07-12T20:27:18.000Z

Can’t tell you for Azure, but AWS setup was pretty straight forward.

Maybe look at this:

Jesper M. Christensen – 1 Jul 12

Creating a Windows Azure virtual network with site-to-site VPN to SonicWALL

One of the great new features of Windows Azure is the ability to create a site-to-site VPN connection to your local network. Microsoft delivers configuration instructions for Cisco and Juniper and …

vince-p · 2015-07-12T20:28:18.000Z

I’m able to ping from each side to the other, and now I’m showing the bandwidth counter go higher, though the firewall log is still dropping some packets. I guess it’s ok

vince-p · 2015-07-12T20:29:42.000Z

M Boyle:

What traffic are you sending over the link?

If you have a server running in Azure can you traceroute to it from your internal network?

You should not need to set up NAT but you need to make sure that the VNET in Azure and your internal network don’t overlap, or put an exclusion in for your internal network on the Azure side. You tell Azure what IP space your on premises network uses.

Routing might be needed, depending on the setup. The internal net needs to go to the firewall for the Azure internal networks.

So far I just setup a do-nothing windows vm. so now that’s it pinging I can try to do a bit more. I was at first distracted by a few messages about packet dropping.

vince-p · 2015-07-12T20:32:36.000Z

And now I was able to join the VM to my domain using the DCs in my office. So wow, I can’t believe I did it finally! Got one thing off my bucket list today