CPUG

The Check Point User Group

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

1. Come to CPUG CON 2008 EUROPE in Switzerland on September 8th - 9th!
    Two days full of technical content for Check Point administrators in the beautiful Swiss Alps!
    We already have 52 attendees signed up from 14 countries!
2. CCSA/CCSE One-Week Dual-Certification Training Course with CPUG in San Francisco!
    Courses Starting 8/25, 10/6, 11/3, 12/8, (2009) 1/19, 2/9, 3/9, 4/6, 5/4, 6/8, 7/6, 8/3, 9/7.
3. Corrent S3500 SecureXL Turbocards For Sale - Last Six Remaining - Get Your Spares!
4. 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-12
BarryStiefel BarryStiefel is offline
Administrator
 
Join Date: 2005-08-11
Location: San Francisco, CA
Posts: 549
Rep Power: 10
BarryStiefel has disabled reputation
Default ARPs disappear after a short time on Windows

ARPs disappear after a short time on Windows

Contributed by PhoneBoy
Published in geeklog Saturday, May 17 2003 @ 05:09 AM EST
Published in oldfaq 2002-Nov-10 00:12 dwelchATphoneboyDOTcom



The following article explains why ARP entries entered with the arp command disappear after a short time on Windows NT/2000 platforms.

If you are using the NG release of FireWall-1, enable "Automatic ARP Configuration" in the Global Properties, Network Address Translation tab if you are using automatic NAT rules. If not or if this fails for some reason, then we will need to configure local.arp on the NT firewall. Let's use the network described in the Q&A entry Routing and ARP issues with NAT:

Our network---------------------------------------------------------------------------- | | L| o| c| a| --------- -------- ---- l| 126.0.10.98| Fire |206.99.98.1 | | |CSU | MCI |-------------| |-----------------| Router |----| |---------- N| le0 | Wall |be0 | | |DSU | e| |_________| |________| |____| t| | | | 126 | . | -------- 0 |------|Web serv|126.0.10.50 . | -------- 10 | . | ---- 0 |------|FTP | | ---- | | ----- |------|Mail | | ----- |----------------------------------------------------------------------------

Suppose that the web server's translated address is 206.99.98.50 and the MAC address of the external interface on the firewall is 08:00:20:76:ea:77. On a UNIX platform, we would add an ARP request to the firewall machine as follows:

arp -s 206.99.98.50 08:00:20:76:ea:77 pub

This ARP message causes the firewall to respond to TCP/IP packets addressed to 206.99.98.50, which allows these packets to get to the firewall. The firewall then takes packets addressed to 206.99.98.50 and re-routes them to 126.0.10.50 thru the internal interface of the firewall.

In Windows NT, the 'arp' command will not function in this manner. Version 2.1c and later of FireWall-1 will do the proxy arps for you. You must create a file called %FWDIR%\state\local.arp (case matters!), which is formatted as follows:

translated_ip_address mac_address

In the example above, this file would contain:

206.99.98.50 08-00-20-76-ea-77

Once you've set this file up, you will need to re-install the current rulebase.

Note that you must have a NAT rule configured for local.arp to work.

-- RayLodato - 07 Jan 2004

FAQForm FAQs.Class: NetworkAddressTranslationFAQs FAQs.OS: OsWindows 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 06:51.


Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
LinkBacks Enabled by vBSEO 3.0.0