Clients can be defined in a configuration file or in a database. A configuration file could be generated manually or generated by a script accessing your configuration database. It has to be referred in general settings file with
store_file_config = /path/to/dhcpy6d/clients.conf
Clients can have these attributes:
- class (required)
- mac – more than one have to be separated by spaces
- duid – more than one have to be separated by spaces
- address – more than one have to be separated by spaces
- id (0-FFFF) – will be used for one octet of IPv6 address
It is mandatory that a client has at least the corresponding attributes the general identification relies on, e.g. if MACs are used for identification all clients should have one in configuration, otherwise they won’t be recognized.
A client configuration file should look like this:
# These are some example clients. Every section is a client. # Every client has to have a hostname, a class and optionally # one of mac or duid to be identified depending on class definition. # Available options are: # # hostname # mac # duid # id # class # address # # The option "id" can be used for address definitions of # category "id". # # The option "address" allows to add additional fixed addresses # beyond class defined addresses. Severall addresses have to # be separated by spaces. [client1] hostname = client1 mac = 01:01:01:01:01:01 class = valid_client [client2] hostname = client2 mac = 02:02:02:02:02:02 class = invalid_client [client3] hostname = client3 duid = 000100011234567890abcdef1234 class = valid_client address = 2001:cb8::babe:1 [client4] hostname = client4 mac = 04:04:04:04:04:04 id = 4 class = valid_client
Every client not listed here will be of class “default” and get its default address(es) as defined for default addresses and class in general configuration file.