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!
LVL 4
MarcusSjogrenAsked:
Who is Participating?
 
asavenerConnect With a Mentor Commented:
OK.  You will need to add a range that matches the possible outside interface addresses of the ASA with the dynamic address.

For example, if the ASA with the dynamic address is Site B:

Site A:
192.168.0.0/24 -> 192.168.1.0/24
192.168.0.0/24->  208.1.1.0/24

Site B:
192.168.1.0/24 -> 192.168.0.0/24
208.1.1.0/24 -> 192.168.0.0/24


Then you set up your IP SLA monitor on Site B, so that it periodically pings a 192.168.0.0/24 address.
0
 
asavenerCommented:
My solution was to set up an automated polling engine at the remote site, such as What's Up Gold or similar running as a service on an internal server.

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.)
0
 
MarcusSjogrenAuthor Commented:
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.
0
Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

 
asavenerCommented:
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.
0
 
MarcusSjogrenAuthor Commented:
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.
0
 
MarcusSjogrenAuthor Commented:
0
 
asavenerCommented:
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.)
0
 
MarcusSjogrenAuthor Commented:
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.
0
 
asavenerCommented:
Did you create a matching traffic ACL on the other end of the VPN?
0
 
MarcusSjogrenAuthor Commented:
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)
0
 
MarcusSjogrenAuthor Commented:
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 :)
0
 
asavenerCommented:
My experience is that the IP SLA on the ASA is a little squirrely.
0
 
MarcusSjogrenAuthor Commented:
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.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.