-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Object Names| same name, different case and different content -> checkpoint rules wrong #14
Comments
Hi mjardeli, I did a patch but there are some caveats you should be aware. When an object is found in checkpoint xml AND in a cisco file, the one from checkpoint only is kept. I cannot simply rename the one from the cisco file as it will never be used or referenced. This is the expected behaviour to consider the checkpoint database as a reference. In such cases, I suggest that you do a mass rename of the conflicting cisco object. This change is introducing modification at lower level. Hopefully, it won't affect the rest too much but you should test as much as possible. Thanks, |
Thank you Martin! Is there a way to create a log or a warning when that happens? The worse part is to identify conflicting objects. Can I suggest a file to be added? Maybe configuration_adjustments.txt icmp can be added. I can create/ populate this file. I'll test and let you know! Cheers |
It is is printed near the "Importing" messages. Try with
|
Hi Martin, I just tested, for object host issue is solved. Its detecting/warning dup with checkpoint object. Can it also be done for network group, service and service group? I created the same objects on checkpoint here follow files(customer_network_objects.xml.txt Here follow config example for each one:
I created on checkpoint objects: same_name,dns_servers and TCP_printer. They all have different values than the ones on cisco config actual parsing output:
Objects being detected as duplicated with checkpoint database will allow manual adjustments before importing config. thank you, |
Hi Martin,
Sorry to bother you again, I think this one is important.
I have one case of same object name but different case on config I am parsing. This is allowed on Cisco configs but not allowed on CheckPoint.
I did few tests, and this can lead to a complete different rule on checkpoint.
There are two objects on checkpoint database ( importing using attached customer_network_objects.xml
customer_network_objects.xml.txt
).
Please pay close attention to object names and case ( this is causing all this mess).
CheckPoint Database:
host dns_1 - 1.1.1.1
group dns_servers containing only dns_1.
Cisco config to parse
Parsing output:
Also as the checkpoint group with small case "dns_servers" was not recognized/loaded, it will fail to import using dbedit as a duplicated object will be found.
kind regards,
The text was updated successfully, but these errors were encountered: