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.
|Published (Last):||11 May 2009|
|PDF File Size:||19.35 Mb|
|ePub File Size:||19.67 Mb|
|Price:||Free* [*Free Regsitration Required]|
Site-to-Site VPN, UTM to SonicWall, Connection made but no traffic
The connection is up, but no traffic is being exchanged. AES Text file value: We are not able to get the tunnel working.
Any suggestions on what may be occurring? I was using the document referencing firmware version 6. Tried Hamachi, but it’s throughput seems slow – something must be standing in between. In either case, if you are using the GUI, follow mvisible’s directions above Re: Connections – I have strict routing enabled.
I have remedied the remaining communication issues by following your original recommendation of disabling NAT traversal options on both appliances. We weren’t able to do 2 VPNs tunnels.
IPSec VPN with SonicWALL – Redirecting traffic over VPN
Oh, another thing is that I found I have to enter NAT policies to stop NAT rules from being applied on ssh and conigure servers that have ports forwarded in some cases, but which shouldn’t be translated if going through the VPN tunnel. Anyone else had frequent tunnel drop outs, especially in the past month? Fantastic well documented article! For good measure I tried removing all custom NAT rules I implemented in case they were mucking up the traffic, but that doesn’t seem to have made any change either.
Jun 18, 2: Disabled I guess Auto-add Access Rules: My traffic on the remote machine We haven’t changed anything on the Sonicwall side, I suspect this is some sort of Amazon issue, specific to the “redundant” tunnel.
I still suspect I’m facing a NAT issue. Feb 11, 1: In reply to Bobby Tables:.
May 15, 1: So I scheduled a script cronjob to reset the tunnel everyday at 6 AM, and now we have no issues. Now, it seems to be more stable while it is up – no sporadic dropping and reconnecting since a recent vpn maintenance period at Amazon, but I don’t know if that has anything to do with itbut it drops after about a day and stays off.
Maybe adding a network diagram where cknfigure list all the subnets on both sides of UTM and Sonicwall could enlighten a bit. My developers are constantly getting kicked out with a “broken pipe” and they are frustrated. I made some progress.
AWS Developer Forums: Help with SonicWall and IPSec VPN
The trick is to set the VPN policy type to “Tunnel Interface” and create static routes for each tunnel. Apr 19, 9: Apr 28, Clear Don’t Fragment Bit: Also, after you add the association you’ll need to choose “route propogation” to make it live.
Interfave the downtime is unacceptable for business use. This question is answered. If more routers are involved, all of them should know how and where to route packets to other networks I put the metric on the static routes at just out of curiosity.
Though as I said the above NAT rules are in place manually. The bash script that runs is: