Jun 24, 2013 · I am trying to connect my ASA 5510 to Azure with a site-to-site VPN. We currently have two sites and two ASA 5510 creating a site-to-site VPN and both ASAs have the latest 9.1 ASA firmware release. One site is the main site and the other site is a satellite site.
[HELP] ASA 5510 VPN Configuration Issues with Site to Site and R Hello, I'm having problems setting up a Remote access and Site to Site VPN at the exact same time. LAN-to-LAN VPN on an ASA 5505 - PacketLife.net Jul 11, 2011 Cisco Security :: ASA 5510 - Site To Site IPSEc VPN Cisco Security :: ASA 5510 - Site To Site IPSEc VPN Configuration Access List Sep 12, 2011. I configurated Ipsec vpn at asa 5510. my inside ip 192.168.10.156my public ip: 85.x.x.xmy peer ip : 62.x.x.x the project is that: the remote site want the interesting traffic like that: source ip 172.16.1.104 can access destination ip 10.0.154.27 ASA 5510 VPN site-to-site - Security, hacker detection
cisco asa - Site-to-Site VPN Tunnel Up Not Passing Traffic
Cisco ASA Site-to-Site IKEv1 IPsec VPN Hi Mark, It sounds like your ASA isn’t configured correctly for NAT. It should be configured to translate all traffic from the 192.168.2.0/24 subnet that exits the outside interface UNLESS the destination is 192.168.39.0/24 (the other end of the VPN).
[HELP] ASA 5510 VPN Configuration Issues with Site to Site
Mar 28, 2013 · Hello I have a site to site VPN with a cisco ASA 5510. I am having an issue with the tunnel dropping. As a work around I setup a trace route every 60 sec to keep the tunnel up. As part of the VPN config I disabled the DPD on the ASA. Is there a way in Azure to keep the tunnel up all the time? Oct 14, 2009 · The tunnel can be built over IPSec or SSL. When done he can disconnect the VPN connection. SITE-TO-SITE Site-to-site VPN is often used for branch offices, when a manageable amount of branch offices is available. You place a VPN device like Cisco ASA or a Cisco router on both sites. You configure both devices to setup a tunnel with each other. Hi Mark, It sounds like your ASA isn’t configured correctly for NAT. It should be configured to translate all traffic from the 192.168.2.0/24 subnet that exits the outside interface UNLESS the destination is 192.168.39.0/24 (the other end of the VPN).