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!
PIX Checkpoint VPN Problem
hi all,
i am having a strange problem and i have tried doing googling but still not getting any strong answer to overcome the issue.
we have one partner in another country and we are trying to setup VPN Tunnel between us and this partner using PIX 515E and Checkpoint FW NXG on the other side.
configured the Crypto Map and ISAKMP and also with help from lrmoore did the natting and acl. the thing is like this.
Site 1.
crypto ipsec transform-set Partnet2 esp-3des esp-md5-hmac
crypto map transam 20 ipsec-isakmp
crypto map transam 20 match address Partnet2
crypto map transam 20 set peer 192.162.10.92
crypto map transam 20 set transform-set NI
crypto map transam 20 set security-association lifetime seconds 3600 kilobytes 4
crypto map transam interface outside
isakmp enable outside
isakmp key ******** address 192.168.10.92 netmask 255.255.255.255
isakmp identity address
isakmp keepalive 10 30
isakmp nat-traversal 20
isakmp policy 20 authentication pre-share
isakmp policy 20 encryption 3des
isakmp policy 20 hash md5
isakmp policy 20 group 2
isakmp policy 20 lifetime 86400
access-list Partner2 permit ip host 100.90.72.20 host 172.22.13.25
access-list Partner2 permit ip host 100.90.72.10 host 192.168.7.5
access-list Partner2 permit ip host 192.168.7.5 host 100.90.72.10
access-list Partner2 permit ip host 100.90.72.10 host 172.17.53.5
access-list Partner2_NAT permit ip host 172.20.4.205 host 172.16.7.5
access-list Partner2_NAT permit ip host 172.20.4.205 host 172.17.53.5
access-list Partner2_NAT1 permit ip host 172.20.4.205 host 172.22.13.25
global (outside) 20 100.90.72.10
global (outside) 30 100.90.72.20
nat (inside) 20 access-list NI_NAT 0 0
nat (inside) 30 access-list NI_NAT1 0 0
Site 2. Checkpoint FW NGX
Problem: when we initiate the connection the VPN Tunnel comes up and we can access there servers. but when they try to initiate the connection; i see on pix that it stops at phase 2 of IPsec.
Question:
for inbound do we need something extra in ACL or simple VPN access-list works for both inbound and outbound. any help would be great, i really need it up
i am having a strange problem and i have tried doing googling but still not getting any strong answer to overcome the issue.
we have one partner in another country and we are trying to setup VPN Tunnel between us and this partner using PIX 515E and Checkpoint FW NXG on the other side.
configured the Crypto Map and ISAKMP and also with help from lrmoore did the natting and acl. the thing is like this.
Site 1.
crypto ipsec transform-set Partnet2 esp-3des esp-md5-hmac
crypto map transam 20 ipsec-isakmp
crypto map transam 20 match address Partnet2
crypto map transam 20 set peer 192.162.10.92
crypto map transam 20 set transform-set NI
crypto map transam 20 set security-association lifetime seconds 3600 kilobytes 4
crypto map transam interface outside
isakmp enable outside
isakmp key ******** address 192.168.10.92 netmask 255.255.255.255
isakmp identity address
isakmp keepalive 10 30
isakmp nat-traversal 20
isakmp policy 20 authentication pre-share
isakmp policy 20 encryption 3des
isakmp policy 20 hash md5
isakmp policy 20 group 2
isakmp policy 20 lifetime 86400
access-list Partner2 permit ip host 100.90.72.20 host 172.22.13.25
access-list Partner2 permit ip host 100.90.72.10 host 192.168.7.5
access-list Partner2 permit ip host 192.168.7.5 host 100.90.72.10
access-list Partner2 permit ip host 100.90.72.10 host 172.17.53.5
access-list Partner2_NAT permit ip host 172.20.4.205 host 172.16.7.5
access-list Partner2_NAT permit ip host 172.20.4.205 host 172.17.53.5
access-list Partner2_NAT1 permit ip host 172.20.4.205 host 172.22.13.25
global (outside) 20 100.90.72.10
global (outside) 30 100.90.72.20
nat (inside) 20 access-list NI_NAT 0 0
nat (inside) 30 access-list NI_NAT1 0 0
Site 2. Checkpoint FW NGX
Problem: when we initiate the connection the VPN Tunnel comes up and we can access there servers. but when they try to initiate the connection; i see on pix that it stops at phase 2 of IPsec.
Question:
for inbound do we need something extra in ACL or simple VPN access-list works for both inbound and outbound. any help would be great, i really need it up
Asked:
1 Solution
hi there.....
one thing i am sure that this is something to do the the Checkpoint box, cuz we had exactly the same problem. There is one specific option they need to check for that......but i need to get a check on that. In the mean time you can ask them to look out for some trials... dnt do anything on pix...
one thing i am sure that this is something to do the the Checkpoint box, cuz we had exactly the same problem. There is one specific option they need to check for that......but i need to get a check on that. In the mean time you can ask them to look out for some trials... dnt do anything on pix...
This message means the networks defined at both ends don't match. Verify that the network objects that fall under encryption on the CheckPoint box match with whatever access list you've used for encryption on the PIX.
NGX - PIX VPN setup should pretty much follow the basics in this 4.1 - PIX VPN example:
http://www.cisco.com/warp/public/110/cp-p.html
NGX - PIX VPN setup should pretty much follow the basics in this 4.1 - PIX VPN example:
http://www.cisco.com/warp/public/110/cp-p.html
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.
Join & Write a Comment Already a member? Login.
Featured Post
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
please i need help here, below is what i see on my debug
IPSEC(validate_transform_p
ISAKMP: IPSec policy invalidated proposal
ISAKMP (0): SA not acceptable!
return status is IKMP_ERR_NO_RETRANS
crypto_isakmp_process_bloc
ISAKMP: reserved not zero on payload 8!
ISAKMP: malformed payload