Jun 09, 2020
A remote client can successfully connect a tunnel to the Cisco VPN router via QuickVPN but cannot connect through the tunnel to the Alpha, as it did before. The W2k3 server and PCs IP can be pinged through the tunnel but ping times out to the Alpha IP. WireShark is no help for encrypted packets. For VPN Tunnel ID, must also enable the Check Point gateway to ping the other end of the tunnel to check if the tunnel is up. Select Ping. I have a problem with BOVPN between my watchguard and a Palo alto firewall in other side, the tunnel is up but when I ping to the host in other side it show : timeout and also for other type of traffic does not passing. and when I ping to some hosts we get 2 recieved packets and lost the other packets. I need to understand and resolve my issue. I know openswan works because when I connect from home network with an internal ip address of 10.0.0.97 to work's VPN, I'm able to ping but when I use the public xFinity wifi it indicates that the tunnel is up but I can't ping the internal hosts of my VPN. Sometimes a tunnel does not come up or it comes up but no traffic passes through, if a static route is defined in the Network > Routes page which conflicts with the Local or Destination Network defined in the VPN Policy. By default, Static Routes on a SonicWALL will overrule VPN Tunnel routes. I have setup a Site to Site VPN using 2 x 220 SRX's. My tunnel is up and I have tried so many reconfigs but I can't seem to get them to pass traffic or ping I tried so many changes I am not sure what my next move should be. Is it a policy or did I mess up on the routes I'm not sure.
Aug 02, 2017
Site to Site VPN tunnel is up but only passing traffic in The most common cause of this issue is network address translation, checking the network address translation table on the SonicWall to ensure there are no incorrect NATs is advisable. The expected traffic flow for local hosts going across the VPN is to see the Ingress Interface and …
networking - SonicWall VPN tunnel is up, but no traffic
My VPC is connected to my premises via IPSec VPN, tunnel is shown to be UP on AWS console. Things that work: I can see the traffic from my premises (subnet 192.168.0.0/16) to AWS VPC ( 10.0.0.0/16) on VPC flowlogs, marked as accepted. IPsec tunnel established but no traffic - SOLVED I have been using. pfsense 1.2.3 on watchguard x1000 hardware and been trying to tunnel with both m0n0wall and sonicwall. the tunnel has always come up no problem but the damn traffic didn't go through! but changing to md5 instead of sha1 made the difference! crazy really and i have been thinking about changing from pfsense just because of this. Solved: Client VPN cannot ping site-to-site - The Meraki The firewalls can ping each other. I confirmed that the client VPN on the MX90 is included in the VPN. On the remote MXs, I looked at the remote VPN participants and confirmed that the client VPN subnet was listed as a participant. The site to site VPN was not changed, it is set up with the MX90 as the hub, and all other sites as spokes. Does Ensure VPN Tunnels Pass Traffic Between Customer Gateways Aug 02, 2017