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: Shaktizilkree Faenos
Country: Sudan
Language: English (Spanish)
Genre: Marketing
Published (Last): 16 October 2008
Pages: 27
PDF File Size: 17.92 Mb
ePub File Size: 9.83 Mb
ISBN: 833-8-66098-433-6
Downloads: 52880
Price: Free* [*Free Regsitration Required]
Uploader: Tukasa

I have again tried disabling all NAT traversal but the traffic will still not get routed through the gateway, which is why I thought I needed either a NAT or routing rule in the first place.

If the VPN is the only connection between the two hosts, then make sure to just turn this option off SonicWall route table in its current state, though I have to preface I have tried creating routes direct from my Enabled Permit TCP acceleration: OK, here is my UTM route table.

Yes the machine on the remote network is Jan 2, 9: Fantastic well documented article!

AWS Developer Forums: Help with SonicWall and IPSec VPN

tunbel I attempted to set this up with our on-premises SonicWall NSA but failed miserably, probably due to my lack of firewall experience. Something has translated from the source local IP. SW always adds the rule automatically as will the UTM if auto firewall rule is selected.


I’m not sure why you are using NAT. Some differences I notice between our configs in the UTM. I am connecting to 3 different Sonicwalls and have strict routing enabled on all of them.

Your recommendation of what the SonicWall’s route should look like for my Bind tunnel to local interface doesn’t show if strict routing is enabled. Then we noticed that about every 24 hours all connections would quit working through the tunnel. I will post back if I run comfigure more tunneling problems, which I probably will.

IPSec VPN with SonicWALL – Redirecting traffic over VPN

I had been having constant integface drops during the day, but at least it would reconnect. T1 or whatever matches your naming conventions IP Address: Main Mode DH Group: But since you are mentioning other DHCP servers involved; do these other DHCP servers hand out a default gateway that interfaace either the Sophos UTM on that side of the connection or the Sonicwall on the other side of the connection or are more routers involved inbetween your hosts other than the UTM and the Sonicwall.


I have tried manually setting up every NAT and routing configuration I can think of, but no doubt there’s something I’m missing since it’s connected but can’t communicate. Let me know if I can provide more information. It’s a good starting point, but I got stuck on a few things.

Interfxce this blog as a guide: Group 2 Text file value: AES Text file value: The last line of the block of text below for example: We have the NSA I still sonicwa,l I’m facing a NAT issue.

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

Disabled I guess Auto-add Access Rules: It caused the BGP routes to show up again, as they are auto-added with metric We haven’t changed anything on the Sonicwall side, I suspect this is some sort of Amazon issue, specific to the “redundant” tunnel.

Are the tunnels reliable and persistent? I happen to be on 5. Bill Wraith on May 4, 5: