The VPN policy configuration creates a Tunnel Interface between two end points. Static or Dynamic routes can then be added to the Tunnel Interface. The Route. Configuring Tunnel Interface (static route-based) VPN using Enterprise Command Line. Last Updated: 12/6/ Views 9 Users found this article helpful. How to Configure a Tunnel Interface VPN (Route-Based VPN) between two SonicWall UTM appliances ยท Configuring a Tunnel Interface VPN with DHCP Relay.

Author: Majinn Tazragore
Country: Honduras
Language: English (Spanish)
Genre: Video
Published (Last): 18 October 2011
Pages: 462
PDF File Size: 7.98 Mb
ePub File Size: 20.17 Mb
ISBN: 595-7-76128-393-3
Downloads: 10052
Price: Free* [*Free Regsitration Required]
Uploader: Meztinos

While it’s open it’s just okay. TI5 confihure whatever your new tunnel if id is metric 1, vph when disconnect, auto add access rules. Actually never mind it worked in the end – despite the fact I changed nothing, maybe pulling the route out of the route table and re-adding it a few times eventually worked. SHA1 Text file value: I now see in your own picture above that this option is unchecked which is good.

No Before these steps I had only been able to get an “UP” response on both ends of the VPN, but was still unable to get nodes in the subnets to talk to each other. Sure go ahead and set them both up – just know which tunnel data you’re reading from.

AWS Developer Forums: Help with SonicWall and IPSec VPN

So, I am waiting to see if it will be stable or not. This group requires membership for participation – click to join.


Dell Sonicwall needs to remove that shameful PDF or update it so it’s accurate. An extra hop or three. But the downtime is unacceptable for business use.

The rest of the problems I have, such as failing to ping DCs let alone use them for credential authentication no logon servers available are likely due to another misconfiguration I should be able to sort out. Thinking about setting up a gateway virtual appliance that cpnfigure I spin up in my VPC and or also on my vSphere environment to connect us.

Don’t bother setting up both tunnels just keep the secondary tunnel gateway IP information around in case you need to swap tunnels later, since the sonicwall can’t have both tunnel interfaces created at the same time due to subnet overlap sonicwalo doesn’t have a secondary IP option for tunnel mode.

Wow – sounds a bit over my head, but I’m curious if using BGP worked. That should do it for the sonicwall side, other people have noted the correct aws config including selecting route propagation and making sure your security groups are allowing traffic to your EC2 instances from your subnets and all that jazz. Nick Wagner Posted on: I was encouraged to do this by Amazon tech support. May 4, 4: In reply to Bobby Tables: What zone do you have the remote host in on the Sonicwall?


We’re seeing tunnels dropping sporadically between a and aws.

Site-to-Site VPN, UTM to SonicWall, Connection made but no traffic

ToMoy on Apr 17, 4: Having the same issue on a TZ, would like to know the answer. We’d love to hear about it! This question is answered. Thanks for the reply.

Then at least you can try pinging between the 2 routers. IKE Phase 1 Proposal: Apr 19, 9: I’m sorry, but I get a bit lost in all the different subnets and start loosing the overview of what confugure located where.

Bill Wraith Posted on: Your post saved me and wanted to Thank You for submitting this in the forum. We weren’t able to do 2 VPNs tunnels.

IPSec VPN with SonicWALL – Redirecting traffic over VPN

Jose Luiz Galego Jr. Enough that it is very often that both tunnels are down. I followed the instructions on http: Some differences I notice between our configs in the UTM. I cannot ping my large local network If it’s frustrating to someone who knows the network, I can’t imagine your frustration coming in cold.