#270 remove duplicates during any import


Importing can create duplicates. Please provide some way to re-use existing objects.

From bug 2980566 "Import from hostsfile may cause duplicate Objects"
When you import a Hostfile twice into same Library Discover Druid creates duplicate Objects.
Hosts with same Name and IP Adress should be ignored.
Milamber ( magicmilamber ) - 2010-04-01 09:58:15 EDT

From the fwbuilder-discussion list:

[Fwbuilder-discussion] How to share objects between imported firewalls?
From: Mike Slifcak <slif@be...> - 2010-06-22 14:00

During a recent deployment exercise, we were interested in bringing our firewall rulesets
under management with Firewall Builder.
We discovered that every Policy Import action creates its own set of objects,
which resulted in a large number of duplicate addresses, address ranges, networks, and
service objects being created exactly the same.

It would be beneficial to share most of these Objects between firewalls:
* Address Ranges
* Address Tables
* Addresses
* DNS Names
* Groups
* Hosts
* Networks
* Services
* Time

Re: [Fwbuilder-discussion] How to share objects between imported firewalls?
From: Sergey Guzenkov <guzenkovsn@gm...> - 2010-06-24 01:56

I think that when importing there should be an option "Substitute
[addresses,protocols] with the matching elements of libraries [tick
boxes for libraries to be used].
There should also be conflict resolution mechanism when 2 libraries
have the same elements. This can be quite easy, for example the last
library listed has higher priority. The only thing that it will
require is that the user should have an opportunity to change the
order of libraries.
Possibly there can be confirmation dialogue for each element
substituted. That dialogue can also be used when you want to merge two
objects that are already in the fwbuilder.


  • Vadim Kurland

    Vadim Kurland - 2011-03-16
    • priority: 5 --> 1
    • assigned_to: nobody --> vkurland
    • status: open --> open-fixed
  • Vadim Kurland

    Vadim Kurland - 2011-03-16

    this is implemented in v4.2.0 build 3501 and later. Packages will be available on the nightly builds site tomorrow.


Log in to post a comment.