Hi,
You must set reservations addresses out of pool range.
Em 18/04/2021 13:45, Makhdoom Naeem escreveu:
Hi all,
According to the following configuration, Client has not received IP
address 192.168.100.125 against hardware address but received IP
address 192.168.100.121 from subnet pool.
Please guide me in this regard.
# The whole configuration starts here.
{
# DHCPv4 specific configuration starts here.
"Dhcp4": {
"interfaces-config": {
"interfaces": [ "enp10s0" ],
"dhcp-socket-type": "raw"
},
"valid-lifetime": 4000,
"renew-timer": 1000,
"rebind-timer": 2000,
"host-reservation-identifiers": [
"hw-address"
],
"subnet4": [{
"subnet": "192.168.100.0/24 <http://192.168.100.0/24>",
//"reservations-global": true,
//"reservations-in-subnet": true,
//"reservations-out-of-pool": false,
"pools": [ { "pool": "192.168.100.121-192.168.100.130" } ]
}],
"reservations": [{
"hw-address": "34:17:EB:66:A4:9D",
"ip-address": "192.168.100.125"
}],
# Now loggers are inside the DHCPv4 object.
"loggers": [{
"name": "*",
"severity": "DEBUG"
}]
# DHCPv4 configuration ends with the next line
}
# The whole configuration structure ends here.
}
--
Makhdoom Muhammad Naeem
Assistant Professor
Department of Electrical Engineering
NFC Institute of Engineering and Technology
Multan
Phone # +92619220012, Ext 2289 <tel:%2B92619220012%2C%20Ext%202231>
Email: [email protected] <mailto:[email protected]>
[email protected] <mailto:[email protected]>
_____
Note:
1. The email and any files transmitted with it will be confidential and
intended solely for the use of the *individual* or *entity* to which they
will be addressed.
2. If you are not the named *addressee*, you should not *disseminate*,
*distribute* or *copy* the e-mail. If you are not the intended recipient,
you are notified that *disclosing*, *copying*, *distributing*, or
taking any
action in reliance on the contents of the information is strictly
prohibited. Any unauthorized reproduction of the message may result in
legal and disciplinary action.
3. *NFC IET* shall not be liable for improper or incomplete or
delayed transmission of the message. *NFC IET* will not accept
liability for any errors or omissions in the contents of the message,
which arise as a result of email transmission.
4. *NFC IET* does not guarantee that the integrity of the email
has been maintained or that that communication will be free of viruses,
interceptions, or interference. Although *NFC IET* will take
reasonable precautions to ensure that no viruses will be present in the
mail, *NFC IET* cannot accept responsibility for any loss or
damage arising from the use of the email or attachments.
_______________________________________________
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
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
--
Marcos Renato da Silva Junior
Universidade Estadual Paulista - Unesp
Faculdade de Engenharia de Ilha Solteira - FEIS
Departamento de Engenharia Elétrica - DEE
15385-000 - Ilha Solteira/SP
(18) 3743-1164
_______________________________________________
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
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
