Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have asked a similiar question, but didn't get any answers so i am going to try and rephrase.

i have 4 locations corporate and 3 remotes

when you are at the corporate location, you have full access to all networks. 192.168.3.x 192.168.2.x 192.168.1.x 192.168.0.x

all locations are connected via site-to-site vpn with the corporate location. if you are at a remote location, you have access to that location & the corporate location.

the corporate location handles all VPN traffic.

however, when you VPN into the corporate location, you can not see outside the corporate location.

can anyone provide some information or a link explaining how to allow the VPN users to see all locations?

thanks

static route configuration:

Gateway of last resort is 207.255.x.1 to network 0.0.0.0

C 207.255.x.0 255.255.255.0 is directly connected, outside

S 10.0.1.6 255.255.255.255 [1/0] via 207.255.x.1, outside

S 10.0.1.5 255.255.255.255 [1/0] via 207.255.x.1, outside

S 192.168.0.0 255.255.255.0 [1/0] via 192.168.0.1, inside

C 192.168.1.0 255.255.255.0 is directly connected, inside

S 192.168.2.0 255.255.255.0 [1/0] via 192.168.2.1, inside

S 192.168.3.0 255.255.255.0 [1/0] via 192.168.3.1, inside

S* 0.0.0.0 0.0.0.0 [1/0] via 207.255.x.1, outside

                 [1/0] via 192.168.1.1, outside
share|improve this question
    
added the static route configuration information –  Jeff Jan 29 '11 at 19:46

2 Answers 2

up vote 3 down vote accepted

If you're sitting your VPN users in the same network as your office you need to add static routing to the other locations on your VPN client settings explicitely, unless you're using your VPN also as your default gateway.

My preferred solution though is to create a new network just for VPN remote users, this gives you a bit of a better view of who they are and what they do, from there on you can either choose to configure static routes on your clients or just activate the VPN as the default gateway for the user.

I'm not a fan of having the VPN as default gateway for the remote user traffic, so I recommend adding static routes to the configuration instead.

share|improve this answer
    
thanks for pointing me in the right direction. by adding static routes to the other locations - do you mean the connection gateways under remote access VPN. do i need to configure these similar to the tunnel groups & crypto maps on the site-to-site vpn configuration? sorry i dont know alot about ASA configurations, this was all setup before my time, and no one left here really has an understanding of. interested in learning tho. –  Jeff Jan 29 '11 at 18:25
    
The connection gateways under remote access VPN, by default your VPN Client will only know of the local network in which he's assigned, by adding static routes in the client it should all work as a bliss –  lynxman Jan 30 '11 at 16:42
    
I see, this might be a stupid question but im not sure of it. so i would have my local network already there, then add the outside ip network with incremental metric values (1 local, 2 network2, etc.)? –  Jeff Jan 31 '11 at 14:13
    
No need for incremental metric but you're on the right track, let's say that your office network is XX.XX.1.X and you get assigned an IP there, to add a route to network XX.XX.2.X you would just add a route through the endpoint of your VPN connection –  lynxman Jan 31 '11 at 14:16
    
Ok I understand what you mean. Appreciate your help with this, thanks again. –  Jeff Jan 31 '11 at 14:17

Couple of suggestions here. You may want to set up tunnels between the remote sites instead of routing via the main site, saves bandwidth etc. ASA site-to-site VPN is fairly limited and the routing is fairly tricky to troubleshoot etc a much nicer setup would be to use DMVPN and a routing protocol (such as EIGRP or OSPF). DMVPN can do next hop resolution whereby the spokes automatically set up tunnels between themselves instead of routing everything via the hub.

If you still wish to enable access between remote sites via your central site you should look in to the command:

same-security-traffic permit intra-interface

This allows the ASA to route traffic out on the same interface it came in on.

share|improve this answer
    
i am not familiar enough with ASAs to want to change the configuration around.. yet atleast. the setup has been this way since before i got here, and there are 4 remote locations that depend heavily on the site-to-site vpn for a centralized database, if im going to break that connection i have to be able to bring it back up and quick or it could be my ass.. i appreciate your response tho, im going to look into the same-security-traffic permit intra-interface command. thanks –  Jeff Jan 31 '11 at 15:15

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.