![]() ![]() You'll need to create multiple objects (server-inside, and server-outside), I assume this is a one-to-one-NAT. Then, it's as simple as setting up a rule in the address translation page. In Checkpoint, check your VPN community settings to make sure that "disable NAT inside the VPN" is NOT checked, as that will override any translation rules you write. Is your question about address translation, or bringing up the VPN? My question is how do i configure the tunnel on checkpoint side to match the ASA configuration so they can talk to each other? I am using a Nokia IP130 with the SmartDashboard R55 to configure the Checkpoint firewall. ![]() With a peer XX.XX.32.4 (where the tunnel will end). If this is correct, then XX.XX.82.75 should travel through the tunnel searching for XX.XX.32.27. The private ip of internal server on Checkpoint side is: 172.23.45.14 and it should be nated to XX.XX.82.75. Phase 1 settings are fine on both sides,matching.Īccording to our debug information we are receiving from remote site:ĪSA is dropping it since it's not matching the traffic. ![]() I am trying to create a tunnel between our company Checkpoint Firewall and a clients Cisco ASA 5510. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |