Differences in the Checkpoint Source files - definitions needed

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Differences in the Checkpoint Source files - definitions needed

L0 Member

Source files available vary between versions.  Can someone elaborate on what the differences are between the files when both are present?

 

What are the differences between these two files?

Objects_5_0.C

Objects.C

 

And What are the differences between these files?

Rulebases_5_0.fws

Rules.C

Policy.W

 

This question specifically comes from an environment that is using Checkpoint version R65

They have supplied files with:

Rulebases_5_0.fws

Policy.W

Objects_5_0.C

Objects.C

 

When we import using Policy.W for Policy, and Rulebases_5_0.fws for Rulebases we get 876 rules.

When we import using Rulebases_5_0.fws for both Policy and Rulebases, and check the box for "Policy comes from Rulesbases_5_0.fws" we get 3415 rules.  There are also a different amount of NATs as well.

 

So what is the difference between Policy.W, Rulebases_5_0.fws, and Rules.C?  

3 REPLIES 3

L1 Bithead

the _5_0 versions are the newer versions (NG/NGX).  the others are legacy (4.x).   Check Point is not good at cleaning up after themselves.  So, stick with the _5_0 versions

Hmmm.  The Expedition interface lists "Rules.C" as the new format. 

 

So are the file versions like this?

 

Policy.W - oldest versions

Rulebases_5_0.fws - in between R65 and R75?

Rules.C - up to R80

Policy.W - oldest versions

Rulebases_5_0.fws - in between R65 -> R77.    

R80 is database based so no file.

 

Not sure what the Rules.C file is.  I do not have one on a 77.30 system here.

  • 4020 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!