Link to home
Start Free TrialLog in
Avatar of decoleur
decoleur

asked on

Site to Site VPN

How would I set up a Site to Site VPN for two networks that are using the same subnet.

I have two servers behind one pix 501 that I want to allow to have access to all the servers behind another pix 501.


network 1 <---> pix 1 <---> Internet <---> pix 2 <---> network 2

network 1 has two servers:
server1-1 IP 192.168.1.199/24
server1-2 IP 192.168.1.195/24

network 2 has three servers:
server2-1 IP 192.168.1.4
server2-2 IP 192.168.1.33
server2-2 IP 192.168.1.119

from server1-1 I would like to access UDP port 161 on all the servers on network 2
from server1-2 I would like to access tcp port 22 on all servers on network 2

any help would be appreciated.

-t
Avatar of Joesmail
Joesmail

Alternative to using the static address translation is to use the global command.  This is a little more resource intensive, although depending on your current config this might be the better solution.

global (outside) 3 172.x.x.1 172.x.x.254 netmask 255.255.255.0
nat (inside) 3 access-list xxxxxxxxxxx

The rest of the crypto commands apply as they are

Avatar of decoleur

ASKER

good link.

i can see how i can get access from one network to another that have the same subnet.

now how would I set up both sides so server1-1 can connect to server2-1 only on UDP port 161?

would I need to create host entries on both sides? What else?

TIA

-t
Instead of using the entire subnet you can use port address translation:

static (inside,outside) udp 192.168.1.199 161 192.168.1.42 161 netmask 255.255.255.255 0 0

or alternatively use the global command as indicated above using an access list of acceptable traffic.....

access-list 101 permit udp 20.1.1.0 255.255.255.0 192.168.1.199 255.255.255.255
etc...etc....keep adding your traffic here for all servers...

access-list NAT_Address permit ip 192.168.1.0 255.255.255.0 10.1.1.0 255.255.255.0

global (outside) 3 20.1.1.1 20.1.1.254 netmask 255.255.255.0
nat (inside) 3 access-list NAT_Address
two questions which side would i be putting these commands on, and what will have the lowest memory /proc overhead...

i am going to end up connecting to 5 remote pixes in production and keep adding more.

TIA
ASKER CERTIFIED SOLUTION
Avatar of Joesmail
Joesmail

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
pix 2 is suppose to be  10.1.1.0 255.255.255.0 192.168.1.199 255.255.255.255 eq 161 etc....
You could also just add a second IP to each server and create seperate subnet that they use to talk through.

network 1 has two servers:
server1-1 IP 192.168.1.199 - 192.168.2.199
server1-2 IP 192.168.1.195 - 192.168.2.195

network 2 has three servers:
server2-1 IP 192.168.1.4 - 192.168.3.4
server2-2 IP 192.168.1.33 - 192.168.3.33
server2-2 IP 192.168.1.119 - 192.168.3.119

Then whenever you want to talk from one server to the other you could specify the second IP and everything would work with the first IP.

You would probably have to set up the route using the route command though.

Just an idea.
(that should be "everything ELSE would work with the first IP")
Thanks I will try mocking this up now.