[Kea-users] config-hash-get – uses full config to hash?

[Diogo André de Assumpção]

Hi all,

I was exploring using the `config-hash-get` command to get a hash of the loaded config and then compare with a candidate config to see if anything was change before loading.

Using the same config that I have loaded in the server, I couldn’t get a hash that matched the one we get via the `config-hash-get` command.

Is that something in the way I’m generating the hash? I’m passing the entire dhcp4 config (ie. {"Dhcp4":…}) to the hash function.

I also noticed that if I do a `config-get` command, the output will contain every optional field that is usually not present in a manually generated config. Could that be the reason why the hashes don’t match?

Thanks,
– Diogo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20250512/4f9c04e6/attachment.htm>