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
LVL 18
decoleurAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JoesmailCommented:
JoesmailCommented:
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

decoleurAuthor Commented:
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
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

JoesmailCommented:
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
decoleurAuthor Commented:
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
JoesmailCommented:
pix 1:
network 1 has two servers:
server1-1 IP 192.168.1.199/24
server1-2 IP 192.168.1.195/24

access-list 101 permit tcp 20.1.1.0 255.255.255.0 192.168.1.4 255.255.255.255 eq 22
access-list 101 permit tcp 20.1.1.0 255.255.255.0 192.168.1.33 255.255.255.255  eq 22
access-list 101 permit tcp 20.1.1.0 255.255.255.0 192.168.1.119 255.255.255.255  eq 22

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

===================================================================

pix 2:
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

access-list 101 permit udp 20.1.1.0 255.255.255.0 192.168.1.199 255.255.255.255 eq 161
access-list 101 permit udp 20.1.1.0 255.255.255.0 192.168.1.195 255.255.255.255 eq 161

access-list NAT_Address permit ip 192.168.1.0 255.255.255.0 20.1.1.0 255.255.255.0

global (outside) 3 10.1.1.1 10.1.1.254 netmask 255.255.255.0
nat (inside) 3 access-list NAT_Address

==========================================================================





Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JoesmailCommented:
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....
brakk0Commented:
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.
brakk0Commented:
(that should be "everything ELSE would work with the first IP")
decoleurAuthor Commented:
Thanks I will try mocking this up now.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Software Firewalls

From novice to tech pro — start learning today.