Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 467
  • Last Modified:

Cisco ASA5510 VPN Clients

Hi
I have users connecting to ASA5510 with Cisco VPN Client. They can connect to internal LAN but not to DMZ lan or other internal LAN's connected off the internal LAN.

How can i allow access to multiple internal LANs?
I guess i first need to tell the VPN client to pass the internal LAN information to the client. As i imagine the client only knows of 10.52.0.0/16 and routes all other taffic to the internet insted of passing to ASA.

Is this correct ? If so how do i get the Client to know that 192.168.33.0/24 traffic should also get routed to ASA ?

Regards
0
Rbauckham69
Asked:
Rbauckham69
  • 4
  • 4
  • 2
  • +2
3 Solutions
 
MikeKaneCommented:
You would need to edit the Access-list that you are using in your split tunnel config.    You need to add another line to the ACL that will allso encrypt the subnets for your DMZ.  

0
 
jmeggersSr. Network and Security EngineerCommented:
You may also have to advertise the VPN subnet to any other segments inside the LAN.  If they don't know where the VPN pool is located, they won't know how to route return traffic to it.
0
 
fgasimzadeCommented:
You would also need to create access lists to access DMZ and NAT0 statements as well.. Can you post your configs?
0
Get Certified for a Job in Cybersecurity

Want an exciting career in an emerging field? Earn your MS in Cybersecurity and get certified in ethical hacking or computer forensic investigation. WGU’s MSCSIA degree program was designed to meet the most recent U.S. Department of Homeland Security (DHS) and NSA guidelines.  

 
Ernie BeekExpertCommented:
In addition to MikeKane and fgasimzade,

Indeed the access lists for matching the traffic going in to the tunnel and being exempted from nat. Also the ASA needs to have a route to the remote (internal) networks and machines on those networks need to have a route to the ip range of the VPN clients through the ASA.

The VPN client only knows the network(s) the ASA is telling it to recognize. If split tunneling is enabled, the rest will go out the internet connecting (local to the client). SO that's why the ASA has got to know (and be able to reach) all the other networks and allow traffic to and from those networks through the VPN.

0
 
Rbauckham69Author Commented:
Thanks to all for your assistance. But i'm still unsure where i should be editing / adding etc.
Is this possible thru the ASDM?

0
 
Rbauckham69Author Commented:
access-list Site_splitTunnelAcl standard permit 10.52.0.0 255.255.0.0

Do i just add another line such as

access-list Bracknell_splitTunnelAcl standard permit 172.22.1.0. 255.255.255.0

?


0
 
fgasimzadeCommented:
Yes, if this is your DMZ LAN
0
 
Rbauckham69Author Commented:
Bingo...easy when you know how.

I also have sites connected thru DMVPN. SHould i be able to also allow access to them the same way. Or is there further complications due to the tunnels that connect them?
0
 
Ernie BeekExpertCommented:
When you know, everything is easy ;)

Split tunnels are for client vpn access. I assume we're talking site 2 site here?
In that case you need to make some other adjustments (also at the device at the other side of the tunnel. The tunnel settings define what networks are to be reached and exempted from nat.
In that case I think it would be easier if you could post a sanitized copy of the config so we can point out what adjustments you would need.
0
 
Rbauckham69Author Commented:
well i want to connect to the other site to site networks thru the VPN clients...

i have the ASA / DMZ at one site where the VPN clients connect. thru and another GW on my LAN which has 3 sites now connected with csico DMVPN.
Previously i understood that we couldn't connect to other sites when "VPN clienting" due to the fact that there was more than 1 ipsec tunnel to route over?

Should i be able to connect now?
Apologies.....Not very clearly explained no doubt!
0
 
Ernie BeekExpertCommented:
Well I think I understand ;)

I was thinking the tunnels were terminated on the ASA. If that was the case you could use 'hairpinning' to get traffic to go the remote vpn's.
In this setup...... I don't know. I'm not too much of an expert with DMVPN, but I got the feeling that it isn't going to work this way.
0
 
Ernie BeekExpertCommented:
Thx for the points :)

Perhaps it's an idea (if you really need it) to post a related question to see if someone can get the DMVPN to remote VPN to work.
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.

Join & Write a Comment

Featured Post

Get Cisco Certified in IT Security

There’s a high demand for IT security experts and network administrators who can safeguard the data that individuals, corporations, and governments rely on every day. Pursue your B.S. in Network Operations and Security and gain the credentials you need for this high-growth field.

  • 4
  • 4
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now