Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    KEA DHCP ALLOC_ENGINE_V4_DISCOVER_ADDRESS_CONFLICT

    Scheduled Pinned Locked Moved
    DHCP and DNS
    1
    1
    73
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • H
      haraldinho
      last edited by

      I migrated to pfSense 24.11, switched to KEA DHCP and I noticed the below error messages that pop up every 5 minutes. The strange thing is that there seems to be no problem. The device that is requesting the IP address gets the correct address and everything seems to work fine. The WARN messages however make me feel a bit uneasy.

      It is only one device that is generating this message. I tried removing the reservation, restarting KEA and then create the same static reservation, but that makes no difference.

      Anybody having the same issue? Anybody any ideas how to figure out why KEA is throwing this error?

      For completeness sake: I have a network setup with multiple VLANs.

      Last 500 DHCP Log Entries. (Maximum 500)
2024-12-03 21:58:30.210248+01:00	kea-dhcp4	87802	WARN [kea-dhcp4.alloc-engine.0x2847a8a16d00] ALLOC_ENGINE_V4_DISCOVER_ADDRESS_CONFLICT [hwtype=1 xx:xx:xx:xx:xx:xx], cid=[01:00:00:00:00:00:00], tid=0x919ece43: conflicting reservation for address xxx.xxx.xxx.xxx with existing lease Address: xxx.xxx.xxx.xxx Valid life: 7200 Cltt: 1733256062 Hardware addr: xx:xx:xx:xx:xx:xx Client id: 01:xx:xx:xx:xx:xx:xx Subnet ID: 5 Pool ID: 0 State: default Relay ID: (none) Remote ID: (none) User context: { "Netgate": { "option-data": { "domain-name": "mylocaldomain.lan" } } }
2024-12-03 21:53:28.892344+01:00	kea-dhcp4	87802	WARN [kea-dhcp4.alloc-engine.0x2847a8a16d00] ALLOC_ENGINE_V4_DISCOVER_ADDRESS_CONFLICT [hwtype=1 xx:xx:xx:xx:xx:xx], cid=[01:00:00:00:00:00:00], tid=0x5b276454: conflicting reservation for address xxx.xxx.xxx.xxx with existing lease Address: xxx.xxx.xxx.xxx Valid life: 7200 Cltt: 1733256062 Hardware addr: xx:xx:xx:xx:xx:xx Client id: 01:xx:xx:xx:xx:xx:xx Subnet ID: 5 Pool ID: 0 State: default Relay ID: (none) Remote ID: (none) User context: { "Netgate": { "option-data": { "domain-name": "mylocaldomain.lan" } } }
2024-12-03 21:48:27.345070+01:00	kea-dhcp4	87802	WARN [kea-dhcp4.alloc-engine.0x2847a8a16d00] ALLOC_ENGINE_V4_DISCOVER_ADDRESS_CONFLICT [hwtype=1 xx:xx:xx:xx:xx:xx], cid=[01:00:00:00:00:00:00], tid=0x88151307: conflicting reservation for address xxx.xxx.xxx.xxx with existing lease Address: xxx.xxx.xxx.xxx Valid life: 7200 Cltt: 1733256062 Hardware addr: xx:xx:xx:xx:xx:xx Client id: 01:xx:xx:xx:xx:xx:xx Subnet ID: 5 Pool ID: 0 State: default Relay ID: (none) Remote ID: (none) User context: { "Netgate": { "option-data": { "domain-name": "mylocaldomain.lan" } } }
2024-12-03 21:43:26.743518+01:00	kea-dhcp4	87802	WARN [kea-dhcp4.alloc-engine.0x2847a8a16d00] ALLOC_ENGINE_V4_DISCOVER_ADDRESS_CONFLICT [hwtype=1 xx:xx:xx:xx:xx:xx], cid=[01:00:00:00:00:00:00], tid=0x906cbd72: conflicting reservation for address xxx.xxx.xxx.xxx with existing lease Address: xxx.xxx.xxx.xxx Valid life: 7200 Cltt: 1733256062 Hardware addr: xx:xx:xx:xx:xx:xx Client id: 01:xx:xx:xx:xx:xx:xx Subnet ID: 5 Pool ID: 0 State: default Relay ID: (none) Remote ID: (none) User context: { "Netgate": { "option-data": { "domain-name": "mylocaldomain.lan" } } }
2024-12-03 21:38:25.303768+01:00	kea-dhcp4	87802	WARN [kea-dhcp4.alloc-engine.0x2847a8a17400] ALLOC_ENGINE_V4_DISCOVER_ADDRESS_CONFLICT [hwtype=1 xx:xx:xx:xx:xx:xx], cid=[01:00:00:00:00:00:00], tid=0xbb32622d: conflicting reservation for address xxx.xxx.xxx.xxx with existing lease Address: xxx.xxx.xxx.xxx Valid life: 7200 Cltt: 1733256062 Hardware addr: xx:xx:xx:xx:xx:xx Client id: 01:xx:xx:xx:xx:xx:xx Subnet ID: 5 Pool ID: 0 State: default Relay ID: (none) Remote ID: (none) User context: { "Netgate": { "option-data": { "domain-name": "mylocaldomain.lan" } } }
2024-12-03 21:33:23.919523+01:00	kea-dhcp4	87802	WARN [kea-dhcp4.alloc-engine.0x2847a8a17400] ALLOC_ENGINE_V4_DISCOVER_ADDRESS_CONFLICT [hwtype=1 xx:xx:xx:xx:xx:xx], cid=[01:00:00:00:00:00:00], tid=0x58005a22: conflicting reservation for address xxx.xxx.xxx.xxx with existing lease Address: xxx.xxx.xxx.xxx Valid life: 7200 Cltt: 1733256062 Hardware addr: xx:xx:xx:xx:xx:xx Client id: 01:xx:xx:xx:xx:xx:xx Subnet ID: 5 Pool ID: 0 State: default Relay ID: (none) Remote ID: (none) User context: { "Netgate": { "option-data": { "domain-name": "mylocaldomain.lan" } } }
2024-12-03 21:28:22.458353+01:00	kea-dhcp4	87802	WARN [kea-dhcp4.alloc-engine.0x2847a8a17400] ALLOC_ENGINE_V4_DISCOVER_ADDRESS_CONFLICT [hwtype=1 xx:xx:xx:xx:xx:xx], cid=[01:00:00:00:00:00:00], tid=0x9141b60f: conflicting reservation for address xxx.xxx.xxx.xxx with existing lease Address: xxx.xxx.xxx.xxx Valid life: 7200 Cltt: 1733256062 Hardware addr: xx:xx:xx:xx:xx:xx Client id: 01:xx:xx:xx:xx:xx:xx Subnet ID: 5 Pool ID: 0 State: default Relay ID: (none) Remote ID: (none) User context: { "Netgate": { "option-data": { "domain-name": "mylocaldomain.lan" } } }
2024-12-03 21:24:59.811955+01:00	kea-dhcp4	87802	WARN [kea-dhcp4.dhcp4.0x2847a8a12000] DHCP4_MULTI_THREADING_INFO enabled: yes, number of threads: 4, queue size: 64
2024-12-03 21:24:59.768108+01:00	kea-dhcp4	87802	WARN [kea-dhcp4.dhcp4.0x2847a8a12000] DHCP4_RESERVATIONS_LOOKUP_FIRST_ENABLED Multi-threading is enabled and host reservations lookup is always performed first.
2024-12-03 21:24:59.768005+01:00	kea-dhcp4	87802	WARN [kea-dhcp4.dhcpsrv.0x2847a8a12000] DHCPSRV_MT_DISABLED_QUEUE_CONTROL disabling dhcp queue control when multi-threading is enabled.
      1 Reply Last reply Reply Quote 0
      • First post
        Last post