Apr 15, 2002 · If you use NAT, the WAN interface of the SonicWALL is publicly addressed and can be hit directly from the Internet. If you don't use NAT, the WAN interface simply passes outbound traffic to the
Nov 04, 2010 · 60 videos Play all SonicWALL Configuration Videos Firewalls.com Top Five Useful Knots for camping, survival, hiking, and more - Duration: 10:47. Nature Reliance Recommended for you I am using the Sonicwall VPN Traffic Sensor against a Sonicwall NSA 2400, but most of the VPN tunnels do not show any traffic. I am using PRTG ver 13.4.6.3374. Here is a set of OID's I pulled from the Sonicwall for one of the tunnels I'm trying to monitor (I edited the IP's): Network Address Translation (NAT) & Load Balancing (LB) provides the ability to balance incoming traffic across multiple, similar network resources. Do not confuse this with the WAN ISP & LB feature on the SonicWALL appliance. While both features can be used in conjunction, WAN ISP & LB is used to balance On the other end, you configure the remote sonicwall to NAT 192.168.97.0/24 traffic to 192.168.1.0/24. So, your 192.168.97.1 hits the NAT on the VPN policy and changed to 192.168.1.1. This happens coming the other way when 192.168.1.0/24 hosts at SiteB attempt to access resources on 192.168.1.0/24 at SiteA.
The correct way would be to fully add the 10.0.0.10/32 network on the tunnel, thus allowing just that remote endpoint. Depending on the NATing, Inter Zone the SonicWall can potentially see the source IP, that the source is from a VPN IP, and the remote admin would need to make allow rule for that traffic to be allowed.
Thanks for getting back to me. I had seen that post about setting up nat-t for the sonicwall. After talking about it yesterday, what I need to do it policy based routing to a Cymphonix across the VPN tunnel. So the VPN tunnel is now looking for HTTP/HTTPS traffic going specifically to that host.
The correct way would be to fully add the 10.0.0.10/32 network on the tunnel, thus allowing just that remote endpoint. Depending on the NATing, Inter Zone the SonicWall can potentially see the source IP, that the source is from a VPN IP, and the remote admin would need to make allow rule for that traffic to be allowed.
Application Notes for Configuring SonicWALL VPN for Supporting H.323 Trunk and Station Traffic to Avaya Communication Manager and Avaya IP Office - Issue 1.0 Abstract These Application Notes describe the steps for configuring SonicWALL’s VPN to support an Avaya IP Telephony infrastructure consisting of a Main Site with Avaya Communication Nov 04, 2010 · 60 videos Play all SonicWALL Configuration Videos Firewalls.com Top Five Useful Knots for camping, survival, hiking, and more - Duration: 10:47. Nature Reliance Recommended for you I am using the Sonicwall VPN Traffic Sensor against a Sonicwall NSA 2400, but most of the VPN tunnels do not show any traffic. I am using PRTG ver 13.4.6.3374. Here is a set of OID's I pulled from the Sonicwall for one of the tunnels I'm trying to monitor (I edited the IP's):