Vpn tunnel ASA5505 help

Below is the configuration for the remote site's vpn. They are using an ASA5510 and we are using an ASA5505.  They're syntax is slightly different and I'm not familiar with it. After looking at their config, what would my settings have to be on the ASA5505 to successfully connect?

ASA5510 config:

access-list MWPH_PSS extended permit ip 128.1.0.0 255.255.0.0  192.168.109.0 255.255.255.0
access-list MWPH_PSS extended permit ip 192.168.109.0 255.255.255.0 128.1.0.0 255.255.0.0
crypto ipsec transform-set PSS esp-3des esp-sha-hmac
crypto map PSSmap  interface outside
crypto map PSSmap 1 match address MWPH_PSS
crypto map PSSmap 1 set peer 12.176.xxx.xxx
crypto map PSSmap 1 set transform-set PSS
 
 crypto isakmp policy 25
 authentication pre-share
 encryption 3des
 hash sha
 group 2
 lifetime 43200
 
tunnel-group 12.176.xxx.xxx type ipsec-l2l
tunnel-group 12.176.xxx.xxx ipsec-attributes
 pre-shared-key xxxxxx
schmad01Asked:
Who is Participating?
 
Markus BraunConnect With a Mentor CEOCommented:
if you use ASDM, there is a setting that says something like " permit vpn to bypass access-lists"
if that one is set, there is nothing else you need to do (in shell its "sysopt connection permit-vpn")
if it is not checked, you need to allow the vpn traffic in your incoming access-list on your outside interface
, the one where you allow traffic from the internet to go inside. you  basically
access-list INCOMING permit ip  128.1.0.0 255.255.0.0 192.168.109.0 255.255.255.0
INCOMING of course to be replaced by whatever name you use
0
 
Markus BraunCEOCommented:
Hi, its basically a mirror with some minor changes:

this "MWPH_PSS" ist just the name, it can be anything, or leave it as it is


access-list MWPH_PSS extended permit ip 128.1.0.0 255.255.0.0 192.168.109.0 255.255.255.0
access-list MWPH_PSS extended permit ip 192.168.109.0 255.255.255.0 128.1.0.0 255.255.0.0

one of the access-lists is not needed
their access-list is THEIR LAN IP 2 YOUR LAN IP
YOUR access-list is YOUR_LAN_IP 2 THEIR_LAN_IP

PSS ist just another name that you can leave too or change it - it just has to match on the last line of the crypto map
crypto ipsec transform-set PSS esp-3des esp-sha-hmac
crypto map PSSmap  interface outside
crypto map PSSmap 1 match address MWPH_PSS
crypto map PSSmap 1 set peer 12.176.xxx.xxx   <<<here you need to put their peer IP
crypto map PSSmap 1 set transform-set PSS   <<<<<<see comment above
 
 crypto isakmp policy 25
 authentication pre-share
 encryption 3des
 hash sha
 group 2
 lifetime 43200
 
this is THEIR tunnel group to YOU
tunnel-group 12.176.xxx.xxx type ipsec-l2l
tunnel-group 12.176.xxx.xxx ipsec-attributes
 pre-shared-key xxxxxx

you need

tunnel-group THEIR_PEER_IP type ipsec-l2l
tunnel-group THEIR_PEER_IP ipsec-attributes
 pre-shared-key AND_OF_COURSE_THE_SAME_KEY

also

you should have a NAT (inside) 0 access-l NONAT

or something similar - if not then e.g.


access-list NONAT extended permit ip 192.168.109.0 255.255.255.0 128.1.0.0 255.255.0.0 <<<<< i am assuming 192.168.109.0 is YOUR network, if not just switch the ip's around
NAT (inside) 0 access-l NONAT

inside is the default name for the well inside or LAN interface , if you named it something different then of course it

NAT (YOUR_INTERFACE) 0 access-l NONAT (WHILE NONAT again is just what i named it)

also if you have a access-l for the traffic from the LAN outgoing, you should permit that traffic too, otherwise traffic wont be passed

I hope i cleared it up a bit, if not you have to post your config so i can see what you already have

0
 
Markus BraunCEOCommented:
ALMOST forgot

you have to, of course match the name of your crypto map

crypto map PSSmap

if yours is not that name, you need to change it to that (PSSmap - is their name - yours can of course be the same unless you already have other tunnels then you need to use your existing name)
0
The Firewall Audit Checklist

Preparing for a firewall audit today is almost impossible.
AlgoSec, together with some of the largest global organizations and auditors, has created a checklist to follow when preparing for your firewall audit. Simplify risk mitigation while staying compliant all of the time!

 
schmad01Author Commented:
I will post my config soon as I can, but also, I don't have this option in my ASA : crypto ipsec transform-set PSS esp-3des esp-sha-hmac

at least the hmac part.
0
 
Markus BraunCEOCommented:
that hmac part is only in shell configs i believe, if you use the WEB Interface its not visible/choosable
0
 
schmad01Author Commented:
I' m not sure what you mean by shell config.  Let's forget everything in the beginning. Forget the names.  Let's say we are starting from scratch. The home site has an asa5505, the remote an asa5510. The home peer is 12.176.xxx.xxx.  The remote peer is 65.210.xxx.xxx.  The home internal subnet is 192.168.109.0.  The remote internal subnet is 128.1.0.0.  Now what commands do I need to set up a successful site to site vpn connection for both sides and allow both internal subnets to see each other?
0
 
schmad01Author Commented:
Anyone?
0
 
Markus BraunCEOCommented:
r u using the ASDM (WEB) or the console/seriel//ssh/telnet? (Shell)
0
 
Markus BraunCEOCommented:
access-list MYVPNLIST permit ip 192.168.109.0 255.255.255.0 128.1.0.0 255.255.0.0
access-list NONATLIST permit ip 192.168.109.0 255.255.255.0 128.1.0.0 255.255.0.0

nat (inside) 0 access-list NONATLIST

crypto ipsec transform-set MYCRYPT esp-3des esp-sha-hmac
crypto map outside_map 100 match address MYVPNLIST
crypto map outside_map 100 set peer 65.210.xxx.xxx
crypto map outside_map 100 set transform-set MYCRYPT
crypto map outside_map interface outside
crypto isakmp identity hostname
crypto isakmp enable outside


THIS SHOULD BE DEFAULT - SO ITS ALREADY CONFIGURED
crypto isakmp policy 65535
 authentication pre-share
 encryption 3des
 hash sha
 group 2

0
 
Markus BraunCEOCommented:
nat (inside) 0 access-list NONATLIST

the name "inside" is the name of the interface your LAN is on, so if you called it something else, you have to replace the "inside" with whatever you called it (its that "nameif xxxxxxx" line on VLAN 1 (usually))




0
 
Markus BraunCEOCommented:
for the other side, just switch the IP's in that access-list and change the peer

e.g.
access-list MYVPNLIST permit ip  128.1.0.0 255.255.0.0 192.168.109.0 255.255.255.0
access-list NONATLIST permit ip 128.1.0.0 255.255.0.0 192.168.109.0 255.255.255.0

nat (inside) 0 access-list NONATLIST

crypto ipsec transform-set MYCRYPT esp-3des esp-sha-hmac
crypto map outside_map 100 match address MYVPNLIST
crypto map outside_map 100 set peer 12.176.xxx.xxx
crypto map outside_map 100 set transform-set MYCRYPT
crypto map outside_map interface outside
crypto isakmp identity hostname
crypto isakmp enable outside
0
 
Markus BraunCEOCommented:
and of course the tunnel groups for your peers
tunnel-group 12.176.xxx.xxx type ipsec-l2l
tunnel-group 12.176.xxx.xxx ipsec-attributes
 pre-shared-key xxxxxx

always the other peer of course not yourself
0
 
schmad01Author Commented:
The tunnel is up. Thank you.
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.

All Courses

From novice to tech pro — start learning today.