1

I have the following network setup.

Internet -- | ASA 5500 | --- DMZ -- Checkpoint Firewall

The checkpoint firewall is used to build a L2L tunnel for payment services. The checkpoint device requires publicly routable IP address. Our ISP has provided us with an additional /30 subnet that is routed in over our main link.

The external address is assigned to the checkpoint device, but I'm unsure how to pass this traffic through the ASA. No nat is allowed per the payment vendor.

How should the ASA be configured to pass the traffic through to the checkpoint device?

4
  • Does the public IP need to be on the device itself, or just be publicly accessible? Are you using NAT for other devices in the DMZ? What function does the ASA play in your network? – David Houde Sep 6 '14 at 7:11
  • The device itself must be publicly accessible. Nat can not be used (we've tried). Other devices in the DMZ are configured with 1:1 static nat. The ASA acts as both our firewall and router, it connects directly to the internet and directly bridges the internal networks. – drj864 Sep 6 '14 at 13:04
  • Have you been able to resolve this "nonat" issue ? I would appreciate if you could share your solution Thanks Ravi – Ravi Dec 25 '14 at 11:37
  • Did any answer help you? if so, you should accept the answer so that the question doesn't keep popping up forever, looking for an answer. Alternatively, you could provide and accept your own answer. – Ron Maupin Aug 10 '17 at 15:15
1

You have a few options, two of which in particular come to mine.

Solution 1
Many times, when a Vendor says "no NAT is allowed", they really mean "no PAT is allowed". This is typically because of a PAT being, by definition, unidirectional. In most VPN type systems, both peers need to be able to initiate traffic to the other, which isn't possible in a unidirectional communication system, like PAT.

As such, the solution is to give your Checkpoint Firewall a Private address, say 192.168.1.25. Then create a Static NAT on your ASA to translate 192.168.1.25 to one of the IPs in the additional /30 your ISP has assigned.

From the VPN configuration perspective, the remote end will use the Public /30 address as their "opposing peer", and you will use the other end's IP address as your "opposing peer". Then, as long as NAT Traversal is enabled (which it typically is by default, but I can only confirm that on the Cisco ASA), the VPN tunnel should be able to build through the Static NAT.

This is your ideal solution, I would suggest going this route if you can. Mainly, because you are holding in reserve the other 3 IPs of the 4 they gave you in the /30. But, if you see no use for these, now or in the future, Solution 2 might work out for you:

Solution 2
Use the /30 assigned by your ISP as its own "transit" network between the ASA and Checkpoint. You'll need an additional interface on the ASA, or you could have the same effect with a Trunk configuration. The ASA will have two segments off it, the transit network, and the DMZ network. Then your "inside" network will simply be "behind" the Checkpoint.

I was going to try to explain this with text, but I figured a picture was easier. I made up the IPs, since you didn't provide them: Transient /30 network

You could either use Identity NAT on the ASA to allow the traffic through un-natted, or simply configure a NAT Exemption for the /30 network.


All other options beyond this require a bit of creativity, but are probably considered non-standard, and as such should be avoided unless the solutions above don't work. If they don't, please provide specific details as to why, so we can try to provide additional solutions.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.