Bug: rfc1918 range handling.

[Stoatwblr]

Problem:

When fusioninventory does a netinventory or netdiscovery, it insists on renaming anything with a RFC1918 address (10., 191.168., 172.{16..32}.*) to "internal", even if there is functioning DNS for the address inside the network.

This is highly undesireable in an enterprise network with several thousand hosts that have RFC1918 assignments and valid DNS within the network.

What should happen:

Fusioninventory should respect existing names if they match dns lookups. Ideally fusioninventory should use DNS lookups to populate unknown entries, as long as fqDNS lookups verify the data.

arbitrarily renaming existing and named entries to "internal" is counterproductive.