CPUG

The Check Point User Group

A Resource For The Check Point Community.  Fast.  Useful.  Independent.

1. CCSA/CCSE One-Week Dual-Certification Training Course with CPUG in San Francisco!
    Courses Starting 12/8, (2009) 1/19, 2/9, 3/9, 4/6, 5/4, 6/8, 7/6, 8/3.
2. Join Us On LinkedIn - We now have a CPUG group.


Go Back   CPUG: The Check Point User Group > Check Point Firewall-1/VPN-1 And Related Products > NAT (Network Address Translation)
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 2005-08-13
Senior Member
 
Join Date: 2005-08-12
Posts: 162
Rep Power: 4
roadrunner has an average reputation (10+)
Default Static NAT for all hosts between two networks

Static NAT for all hosts between two networks

Question
Hi all,

Here is my configuration :

- 2 Nokia IP440, IPSO 3.7.1 - NG AI

I need to configure static NAT for all hosts between 2 networks configured like this. Network A 10.1.0.0 ------FW-------NetworkB 172.16.0.0

What I want exactly to do is to translate in static each host on Network A with an Ip address like 10.1.X.X on Network B with in an IP address 172.16.X.X. ( X must be the same on each side of the firewall) I think I can do it with NAT configured for an address range ( but I'm not sure X will remain the same on each side of the FW), Can you confirm me that or explain me how to do this if it's possible.


Answer
You can translate entire address ranges or even networks. The assumption is that you have the same size contiguous range of addresses on both sides. You could do something like this:

# Original Translated
# Source Destination Service Source Destination Service
1 net-10-1-0-0 NOT net-10-1-0-0 Any net-172-16-0-0 (S) Orig Orig
2 NOT net-10-1-0-0 net-172-16-0-0 Any Orig net-10-1-0-0 (S) Orig


(net-10-1-0-0 and net-172-16-0-0 must have the same netmask)

In this instance


10.1.0.1 becomes 172.16.0.1
10.1.0.2 becomes 172.16.0.2
10.1.0.3 becomes 172.16.0.3
Furthermore:


172.16.0.1 becomes 10.1.0.1
172.16.0.2 becomes 10.1.0.2
172.16.0.3 becomes 10.1.0.3
Hopefully 172.16.0.0 is an unused subnet on the other side of your firewall, else you will have to use address ranges to "exclude" the used address on the other side of the firewall.

-- PhoneBoy - 01 Jan 2004


FAQForm
FAQs.Class: NetworkAddressTranslationFAQs
FAQs.OS:
FAQs.Version:
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


All times are GMT -7. The time now is 13:11.


Powered by vBulletin® Version 3.7.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.2.0