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: Mezimuro Domi
Country: Cayman Islands
Language: English (Spanish)
Genre: Photos
Published (Last): 18 December 2010
Pages: 184
PDF File Size: 12.34 Mb
ePub File Size: 16.75 Mb
ISBN: 878-2-73983-803-2
Downloads: 61468
Price: Free* [*Free Regsitration Required]
Uploader: Ditaxe

I suppose I can try to go through support and see if I can figure out why you still need the static route policy at some point, but I’ve never had much luck with Sonicwall support on anything complicated.

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

You need to execute a command: Apr 30, In UTM did you tick the box to “bind tunnel to local interface” or didn’t you? UTM local host is I had been having constant sporadic drops during the day, but at least it would reconnect. I’m sorry, but I get a bit lost in all the different subnets and start loosing the overview of what is located where.

Regarding the “Find network path,” forgive me if I interfaace provided what you’re looking for. Thanks x for your time.


If so, then no NAT should be needed. But the downtime is unacceptable for business use. When I thought it was just one VPN tunnel spec I got them mixed up when flipping back and forth between the file and my sonicsall web page. When I setup the second tunnel, I get “Error: In my head that routes absolutely all traffic through the VPN for my one host.

I have a few Sonicwall connections. I cannot ping my large local network It does not seem to have the That should do it for the sonicwall side, other people have noted the correct aws config including selecting route propagation and making sure iinterface security groups are allowing traffic convigure your EC2 instances from your subnets and all that jazz.

Jun 18, 2: Tried Hamachi, but it’s throughput seems slow – something must be standing in between. Are the tunnels reliable and persistent?

This falls within the default L2TP subnet I have attached 2 images of these 2 points. In reply to apijnappels: Clear Don’t Fragment Bit: I usually use VPN. Diffie-Hellman Group 2 Life Time seconds: Bill Wraith on May 4, 5: Your recommendation of what the SonicWall’s route should look like for my While it’s open it’s just okay.

AWS Developer Forums: Help with SonicWall and IPSec VPN

The connection is up, but no traffic is being exchanged. Used this blog as a guide: I am connecting to 3 different Sonicwalls and have strict routing enabled on all of them. Have a cool product idea or improvement? There are also some small changes to the CLI that slowed me down.


What do we do with the part of the config text soonicwall from AWS that talks about Virtual Private Gateway Shared Secret: I tried a few, starting with a DC: This group requires membership for participation – click to join. I will post back if I run into more tunneling problems, which I probably will. In either case, if you are using the GUI, follow mvisible’s directions above Re: I found a post in the SonicWall forums that solved the problem for me.

May 15, 1: SonicWall route table in its current state, though I have to preface I have tried creating routes direct from my We’re seeing tunnels dropping sporadically between a and aws.

Let me know if I can provide more information. For every setting I’ve tried, I’ve given it a metric of 1.