Hi All, We have pre-allocated all my desktops, 400+ in current DDI (replacing with Kea/phpIPAM). Hoping to do the same with kea. I see in section Hosts Storage,
// The example below is not optimal from a performance perspective, but it // nicely showcases the host reservation capabilities. Please use the minimum // set of identifier types used in your network. * "host-reservation-identifiers": [ "circuit-id", "hw-address", "duid", "client-id" ],* // Specify connection to the database holding host reservations. The type // specifies that the MySQL database is used. user and password are the // credentials used to connect to the database. host and name specify // location of the host where the database instance is running, and the // name of the database to use. The server processing a packet will first // check if there are any reservations specified for this client in the // reservations list, within the subnet (configuration file). If there are // no reservations there, the server will try to retrieve reservations // from this database. "hosts-database": { "type": "mysql", "reconnect-wait-time": 3000, // expressed in ms "max-reconnect-tries": 3, "name": "keatest", "user": "keatest", "password": "keatest", "host": "localhost", "port": 3306, "trust-anchor": "my-ca", "cert-file": "my-cert", "key-file": "my-key", "cipher-list": "AES" }, "id": 1 <== is the subnet id? how does it work with multiple subnets/scopes, is there a column to identify a different subnet? in *host-reservation-identifiers * typically config but in my case reservations all in DB. { "subnet4": [ { "id": 1, "pools": [ { "pool": "192.0.2.1 - 192.0.2.200" } ], "subnet": "192.0.2.0/24", "interface": "eth0", "reservations": [ { "hw-address": "1a:1b:1c:1d:1e:1f", "ip-address": "192.0.2.202" }, { "duid": "0a:0b:0c:0d:0e:0f", "ip-address": "192.0.2.100", "hostname": "alice-laptop" }, { "circuit-id": "'charter950'", "ip-address": "192.0.2.203" }, { "client-id": "01:11:22:33:44:55:66", "ip-address": "192.0.2.204" } ] } ], Regards, Michael
-- ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. Kea-users mailing list Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users