I've seen questions that have touched on this, but I'm still a little confused. So I'm hoping you can help. :-)
We have two physical locations, both of which are connected using a Cisco ASA 5505 VPN on each side. Works great. On one side we also have a remote-access VPN for a few remote users. These users can access resources on one side of the site-to-site VPN (the side they connect to), but not the other.
Here is what we have:
siteA 192.168.222.0/24 <- Site2Site VPN --> siteB 192.168.1.0/24
192.168.2.0/24 <-- RA VPN --> remote users
So users connect to the Cisco ASA 5505 on the siteB side and can access all resources in 192.168.1.0/24. However, they can't access anything on 192.168.222.0/24. It seems to be a routing issue from what I can tell, but I can't find a way to get routing of a second subnet to work over the site-to-site VPN other than the initial subnets you setup in the VPN config.
ideas?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
You'd be better off using reverse route injection on your crypto map configurations so the ASA's can handle inter-site routing. Eg:
crypto dynamic-map Outside_dyn_map 20 set reverse-route
On your ASA which handles the remote access VPN terminate, send it a default to be the ASA's IP address so it can handle routing:
route <Interface name> 0.0.0.0 0.0.0.0 <next-hop IP> tunneled
Business Accounts
Answer for Membership
by: KeremEPosted on 2009-05-25 at 18:00:06ID: 24469530
You need to::
- add a static routing to RA VPN box so that it will direct 192.168.222.0/24 traffic to the site2siteVPN box.
- add a static routing to site2site VPN box so that all 192.168.2.0/24 traffic is directed to RA-VPN box.
- If site2Site box is not the default gateway for SiteA hosts you need to add a static route to direct all 192.168.2.0/24 traffic to Site2Site 122.168.222.0/24 side interface.
As you will notice these are all static routings so you won't need to configure it over the VPN. Just aadd it to the configuration of VPN boxes.
Cheers,
K.