MarcusSjogren
asked on
Cisco ASA Dynamic VPN
Hi,
I am wondering if anybody has come up up with a cleaver solution to this problem?
Scenario:
1. We have a main HUB with ~35 VPNs to different customers.
2. We have one customer who have a Cisco ASA behind an ADSL router with dynamic IP so we must configure it with a dynamic VPN cryptomap in our HUB.
3. VPN is IPSec Site to Site
4. Tunnel work just fine.
The problem is rather that the tunnel is not setup automatically, it requires "interesting traffic" to pass before the tunnel is established.
Is there any way to make it connect automatically?
I tried to configure the customer ASA with "Originate Only" but then I received errors in the HUB where the customer ASA was trying to setup a tunnel for <CustomerASA Local IP 192.168.0.11> and <Main HUB Public IP> which did not match any crypto map.
I also tried to set up an IP SLA but that did not generate the sufficient traffic. Though, issuing a ping from the customer ASA to our office did get the tunnel going ("ping inside 192.168.0.1" for example).
Would be nice to see if anybody have found a solution to this :-)
Cheers!
I am wondering if anybody has come up up with a cleaver solution to this problem?
Scenario:
1. We have a main HUB with ~35 VPNs to different customers.
2. We have one customer who have a Cisco ASA behind an ADSL router with dynamic IP so we must configure it with a dynamic VPN cryptomap in our HUB.
3. VPN is IPSec Site to Site
4. Tunnel work just fine.
The problem is rather that the tunnel is not setup automatically, it requires "interesting traffic" to pass before the tunnel is established.
Is there any way to make it connect automatically?
I tried to configure the customer ASA with "Originate Only" but then I received errors in the HUB where the customer ASA was trying to setup a tunnel for <CustomerASA Local IP 192.168.0.11> and <Main HUB Public IP> which did not match any crypto map.
I also tried to set up an IP SLA but that did not generate the sufficient traffic. Though, issuing a ping from the customer ASA to our office did get the tunnel going ("ping inside 192.168.0.1" for example).
Would be nice to see if anybody have found a solution to this :-)
Cheers!
ASKER
Thanks for your suggestion Asavener, but we currently don't have any server there who can do the polling for us.
Therefore I tried to do it via IP SLA but that did not seem to generate interesting traffic to setup the tunnel.
Therefore I tried to do it via IP SLA but that did not seem to generate interesting traffic to setup the tunnel.
Does the SLA entry show as up when the VPN is connected and down when the VPN is disconnected?
If I recall correctly, the IP SLA does not allow you to specify a source IP address. You might need to edit the VPN access list to include ICMP, source outside IP, destination inside IP at VPN endpoint.
If I recall correctly, the IP SLA does not allow you to specify a source IP address. You might need to edit the VPN access list to include ICMP, source outside IP, destination inside IP at VPN endpoint.
ASKER
asavener:
Hmm - I was farily sure I responded to your answer, but obviously not.
Anyhow - yes, it does show up and down and ICMP is allowed. However - my understanding is that the Cisco ASA cannot generate "Interesting traffic" on its own, it has to be generated from the local LAN. I dont understand why but that seems to be the case.
I dont think that what I want to do is possible.
Hmm - I was farily sure I responded to your answer, but obviously not.
Anyhow - yes, it does show up and down and ICMP is allowed. However - my understanding is that the Cisco ASA cannot generate "Interesting traffic" on its own, it has to be generated from the local LAN. I dont understand why but that seems to be the case.
I dont think that what I want to do is possible.
ASKER
Maybe this can work - I will try it out.
http://serverfault.com/questions/70189/cisco-asa-manually-start-a-vpn-tunnel
http://serverfault.com/questions/70189/cisco-asa-manually-start-a-vpn-tunnel
The ASA can definitely produce interesting traffic, but the source address will be the outside interface. So you have to edit the VPN access list and ONLY include traffic with the correct source and destination addresses. (For example, if you include the outside interface address and the peer address, the VPN will attempt to tunnel its own traffic.)
ASKER
I have indeed tried to create interesting traffic by using IP SLA with correct source IP etc. but that does not seem to be interesting to put inside the VPN tunnel anyway.
Did you create a matching traffic ACL on the other end of the VPN?
ASKER
Are you referring to crypto map acl or normal acl?
The crypto map is the full subnets:
Site A:
192.168.0.0/24 (inside) -> 192.168.1.0/24 (Site B)
Site B:
192.168.1.0/24 (inside) -> 192.168.0.0/24 (Site A)
The crypto map is the full subnets:
Site A:
192.168.0.0/24 (inside) -> 192.168.1.0/24 (Site B)
Site B:
192.168.1.0/24 (inside) -> 192.168.0.0/24 (Site A)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi,
OK - that sounds strange, since I have configured the IP SLA to use a specific source address. But I will see if I can manage to make some tests some day :)
OK - that sounds strange, since I have configured the IP SLA to use a specific source address. But I will see if I can manage to make some tests some day :)
My experience is that the IP SLA on the ASA is a little squirrely.
ASKER
The resolution marked as an accepted solution works OK, but the IP SLA still does not work as expected as interesting traffic does not seem to be generated by the ASA.
A side benefit is that it can sent alert E-mails. (Best if they have an internal mail server. External mail servers are often unavailable due to the same outage causing the VPN to fail.)