[Kea-users] kea hands out 2 ip addresses

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

[Kea-users] kea hands out 2 ip addresses

eacool
Hi, keadhcp is currently handing out 2 ip addresses to each client
unnecessarily in short succession.  It hands out the first ip address, it
then replaces the first ip address with a second one a few seconds later and
then eventually expires the lease on the first ip address.  Please note the
short lease time is for testing and this issue occurs when the lease is set
to an hour also.

This also occurs to clients that are windows and linux based so I am pretty
sure my client settings are not the issue either.

My expected behaviour is that keadhcp hands out a single ip address to a
client.

My client has 1 interface

1) client spins up
2) requests ip address
3) kea supplies ipaddress
4) keaddns then hands off dns name to powerdns
5) client then requests another ip address
6) kea supplies 2nd ip address, this then replaces the first ip address and
dns name on the client
7) kea then hands off 2nd dns name to powerdns.
8) lease expires on 1st ip address and is reclaimed by kea and removed from
powerdns.

DHCP config

{
  "Dhcp4": {
    "interfaces-config": {
      "interfaces": [
        "ens192"
      ],
      "dhcp-socket-type": "raw"
    },
    "lease-database": {
      "type": "mysql",
      "name": "keadhcp",
      "host": "10.172.0.30",
      "user": "keadhcp",
      "password": "password"
    },
    "expired-leases-processing": {
      "reclaim-timer-wait-time": 10,
      "flush-reclaimed-timer-wait-time": 25,
      "hold-reclaimed-time": 360,
      "max-reclaim-leases": 100,
      "max-reclaim-time": 250,
      "unwarned-reclaim-cycles": 5
    },
    "dhcp-ddns": {
      "enable-updates": true,
      "qualifying-suffix": "eu-ldn-west.compute.internal",
      "replace-client-name": "always",
      "generated-prefix": "ip"
    },
    "valid-lifetime": 300,
    "subnet4": [
      {
        "subnet": "10.172.0.0/24",
        "pools": [
          {
            "pool": "10.172.0.150 - 10.172.0.200"
          }
        ],
        "option-data": [
          {
            "name": "routers",
            "data": "10.172.0.1"
          },
          {
            "name": "domain-name-servers",
            "data": "10.172.0.42"
          }
        ]
      }
    ]
  },
 "Logging": {
      "loggers": [
          {
              "name": "kea-dhcp4",
              "output_options": [
                  {
                      "output": "/var/log/kea-dhcp4.log"
                  }
              ],
              "severity": "DEBUG",
              "debuglevel": 99
          }
      ]
  }
}

here are my logs, here you can see a client ends up requesting 2 ips in a
short space of time.


############################################################

2019-06-20 15:26:48.000 INFO  [kea-dhcp4.leases/32] DHCP4_LEASE_ADVERT
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: lease 10.172.0.150 will be advertised
2019-06-20 15:26:48.000 DEBUG [kea-dhcp4.ddns/32]
DHCP4_RESPONSE_HOSTNAME_GENERATE [hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: server has generated hostname
ip-10-172-0-150.eu-ldn-west.compute.internal for the client
2019-06-20 15:26:48.001 DEBUG [kea-dhcp4.options/32] DHCP4_PACKET_PACK
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: preparing on-wire format of the packet to be sent
2019-06-20 15:26:48.001 DEBUG [kea-dhcp4.packets/32] DHCP4_PACKET_SEND
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: trying to send packet DHCPOFFER (type 2) from 10.172.0.25:67
to 10.172.0.150:68 on interface ens192
2019-06-20 15:26:48.002 DEBUG [kea-dhcp4.packets/32] DHCP4_RESPONSE_DATA
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: responding with packet DHCPOFFER (type 2), packet details:
local_address=10.172.0.25:67, remote_address=10.172.0.150:68,
msg_type=DHCPOFFER (2), transid=0x3cfa9355,
options:
  type=001, len=004: 4294967040 (uint32)
  type=003, len=004: 10.172.0.1
  type=006, len=004: 10.172.0.42
  type=012, len=044: "ip-10-172-0-150.eu-ldn-west.compute.internal"
(string)
  type=051, len=004: 3600 (uint32)
  type=053, len=001: 2 (uint8)
  type=054, len=004: 10.172.0.25
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d
2019-06-20 15:26:48.003 DEBUG [kea-dhcp4.packets/32] DHCP4_BUFFER_RECEIVED
received buffer from 0.0.0.0:68 to 255.255.255.255:67 over interface ens192
2019-06-20 15:26:48.003 DEBUG [kea-dhcp4.options/32] DHCP4_BUFFER_UNPACK
parsing buffer received from 0.0.0.0 to 255.255.255.255 over interface
ens192
2019-06-20 15:26:48.003 DEBUG [kea-dhcp4.dhcpsrv/32]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-06-20 15:26:48.003 DEBUG [kea-dhcp4.packets/32] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: the subnet with ID 1 was selected for client assignments
2019-06-20 15:26:48.004 DEBUG [kea-dhcp4.packets/32] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: the selected subnet details: 10.172.0.0/24
2019-06-20 15:26:48.004 DEBUG [kea-dhcp4.packets/32] DHCP4_PACKET_RECEIVED
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: DHCPREQUEST (type 3) received from 0.0.0.0 to
255.255.255.255 on interface ens192
2019-06-20 15:26:48.004 DEBUG [kea-dhcp4.packets/32] DHCP4_QUERY_DATA
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355, packet details: local_address=255.255.255.255:67,
remote_address=0.0.0.0:68, msg_type=DHCPREQUEST (3), transid=0x3cfa9355,
options:
  type=050, len=004: 10.172.0.150 (ipv4-address)
  type=053, len=001: 3 (uint8)
  type=054, len=004: 10.172.0.25 (ipv4-address)
  type=055, len=009: 1(uint8) 3(uint8) 12(uint8) 15(uint8) 6(uint8)
26(uint8) 33(uint8) 121(uint8) 42(uint8)
  type=057, len=002: 576 (uint16)
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d
2019-06-20 15:26:48.005 DEBUG [kea-dhcp4.dhcpsrv/32]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-06-20 15:26:48.005 DEBUG [kea-dhcp4.packets/32] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: the subnet with ID 1 was selected for client assignments
2019-06-20 15:26:48.005 DEBUG [kea-dhcp4.packets/32] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: the selected subnet details: 10.172.0.0/24
2019-06-20 15:26:48.006 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 1, identified by hwaddr=00505695C165
2019-06-20 15:26:48.006 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: hwaddr=00505695C165
2019-06-20 15:26:48.006 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=00505695C165,
found 0 host(s)
2019-06-20 15:26:48.006 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 1
and identifier hwaddr=00505695C165
2019-06-20 15:26:48.007 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 1, identified by duid=00020000AB1160F187C05CAA916D
2019-06-20 15:26:48.007 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: duid=00020000AB1160F187C05CAA916D
2019-06-20 15:26:48.007 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier
duid=00020000AB1160F187C05CAA916D, found 0 host(s)
2019-06-20 15:26:48.008 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 1
and identifier duid=00020000AB1160F187C05CAA916D
2019-06-20 15:26:48.008 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 1, identified by
client-id=FF2D1AA13300020000AB1160F187C05CAA916D
2019-06-20 15:26:48.008 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: client-id=FF2D1AA13300020000AB1160F187C05CAA916D
2019-06-20 15:26:48.008 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier
client-id=FF2D1AA13300020000AB1160F187C05CAA916D, found 0 host(s)
2019-06-20 15:26:48.009 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 1
and identifier client-id=FF2D1AA13300020000AB1160F187C05CAA916D
2019-06-20 15:26:48.009 DEBUG [kea-dhcp4.dhcp4/32] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: client packet has been assigned to the following class(es):
UNKNOWN
2019-06-20 15:26:48.009 DEBUG [kea-dhcp4.dhcp4/32] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: client packet has been assigned to the following class(es):
ALL, UNKNOWN
2019-06-20 15:26:48.010 DEBUG [kea-dhcp4.ddns/32]
DHCP4_CLIENT_HOSTNAME_PROCESS [hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: processing client's Hostname option
2019-06-20 15:26:48.010 DEBUG [kea-dhcp4.ddns/32] DHCP4_GENERATE_FQDN
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: client did not send a FQDN or hostname; FQDN will be be
generated for the client
2019-06-20 15:26:48.010 DEBUG [kea-dhcp4.dhcpsrv/32]
DHCPSRV_MYSQL_GET_CLIENTID obtaining IPv4 leases for client ID
ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d
2019-06-20 15:26:48.011 DEBUG [kea-dhcp4.dhcpsrv/32]
DHCPSRV_MYSQL_GET_HWADDR obtaining IPv4 leases for hardware address hwtype=1
00:50:56:95:c1:65
2019-06-20 15:26:48.012 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4 get one host with reservation for
subnet id 1 and IPv4 address 10.172.0.150
2019-06-20 15:26:48.012 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_ADDRESS4 get all hosts with reservations for IPv4 address
10.172.0.150
2019-06-20 15:26:48.012 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_ADDRESS4_COUNT using address 10.172.0.150, found 0
host(s)
2019-06-20 15:26:48.013 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4_NULL host not found using subnet id 1
and address 10.172.0.150
2019-06-20 15:26:48.013 DEBUG [kea-dhcp4.dhcpsrv/32] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.150
2019-06-20 15:26:48.014 DEBUG [kea-dhcp4.alloc-engine/32]
ALLOC_ENGINE_V4_REQUEST_ALLOC_REQUESTED [hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: trying to allocate requested address 10.172.0.150
2019-06-20 15:26:48.014 DEBUG [kea-dhcp4.dhcpsrv/32] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.150
2019-06-20 15:26:48.015 DEBUG [kea-dhcp4.dhcpsrv/32] DHCPSRV_MYSQL_ADD_ADDR4
adding IPv4 lease with address 10.172.0.150
2019-06-20 15:26:48.017 INFO  [kea-dhcp4.leases/32] DHCP4_LEASE_ALLOC
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: lease 10.172.0.150 has been allocated
2019-06-20 15:26:48.017 DEBUG [kea-dhcp4.ddns/32]
DHCP4_RESPONSE_HOSTNAME_GENERATE [hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: server has generated hostname
ip-10-172-0-150.eu-ldn-west.compute.internal for the client
2019-06-20 15:26:48.018 DEBUG [kea-dhcp4.dhcpsrv/32]
DHCPSRV_MYSQL_UPDATE_ADDR4 updating IPv4 lease for address 10.172.0.150
2019-06-20 15:26:48.020 DEBUG [kea-dhcp4.ddns/32] DHCP4_NCR_CREATE [hwtype=1
00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: DDNS updates enabled, therefore sending name change
requests
2019-06-20 15:26:48.020 DEBUG [kea-dhcp4.dhcpsrv/32] DHCPSRV_QUEUE_NCR
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d]: name change
request to add DNS entry queued: Type: 0 (CHG_ADD)
Forward Change: yes
Reverse Change: yes
FQDN: [ip-10-172-0-150.eu-ldn-west.compute.internal.]
IP Address: [10.172.0.150]
DHCID:
[00010193E7B0EADDC5DD30491C0E5133815A0217BC6D051FD8259A636A5D0530FDF710]
Lease Expires On: 20190620162648
Lease Length: 3600

2019-06-20 15:26:48.021 DEBUG [kea-dhcp4.options/32] DHCP4_PACKET_PACK
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: preparing on-wire format of the packet to be sent
2019-06-20 15:26:48.021 DEBUG [kea-dhcp4.packets/32] DHCP4_PACKET_SEND
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: trying to send packet DHCPACK (type 5) from 10.172.0.25:67
to 10.172.0.150:68 on interface ens192
2019-06-20 15:26:48.021 DEBUG [kea-dhcp4.packets/32] DHCP4_RESPONSE_DATA
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d],
tid=0x3cfa9355: responding with packet DHCPACK (type 5), packet details:
local_address=10.172.0.25:67, remote_address=10.172.0.150:68,
msg_type=DHCPACK (5), transid=0x3cfa9355,
options:
  type=001, len=004: 4294967040 (uint32)
  type=003, len=004: 10.172.0.1
  type=006, len=004: 10.172.0.42
  type=012, len=044: "ip-10-172-0-150.eu-ldn-west.compute.internal"
(string)
  type=051, len=004: 3600 (uint32)
  type=053, len=001: 5 (uint8)
  type=054, len=004: 10.172.0.25
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:60:f1:87:c0:5c:aa:91:6d
2019-06-20 15:26:48.022 DEBUG [kea-dhcp4.dhcpsrv/32]
DHCPSRV_DHCP_DDNS_NCR_SENT NameChangeRequest sent to kea-dhcp-ddns: Type: 0
(CHG_ADD)
Forward Change: yes
Reverse Change: yes
FQDN: [ip-10-172-0-150.eu-ldn-west.compute.internal.]
IP Address: [10.172.0.150]
DHCID:
[00010193E7B0EADDC5DD30491C0E5133815A0217BC6D051FD8259A636A5D0530FDF710]
Lease Expires On: 20190620162648
Lease Length: 3600

2019-06-20 15:26:55.030 DEBUG [kea-dhcp4.dhcpsrv/32]
DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer:
reclaim-expired-leases
2019-06-20 15:26:55.030 DEBUG [kea-dhcp4.alloc-engine/32]
ALLOC_ENGINE_V4_LEASES_RECLAMATION_START starting reclamation of expired
leases (limit = 100 leases or 250 milliseconds)
2019-06-20 15:26:55.030 DEBUG [kea-dhcp4.dhcpsrv/32]
DHCPSRV_MYSQL_GET_EXPIRED4 obtaining maximum 101 of expired IPv4 leases
2019-06-20 15:26:55.032 DEBUG [kea-dhcp4.alloc-engine/32]
ALLOC_ENGINE_V4_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 1.570 ms
2019-06-20 15:26:55.032 DEBUG [kea-dhcp4.alloc-engine/32]
ALLOC_ENGINE_V4_NO_MORE_EXPIRED_LEASES all expired leases have been
reclaimed
2019-06-20 15:26:55.032 DEBUG [kea-dhcp4.dhcpsrv/32]
DHCPSRV_TIMERMGR_START_TIMER starting timer: reclaim-expired-leases
2019-06-20 15:26:55.277 DEBUG [kea-dhcp4.packets/32] DHCP4_BUFFER_RECEIVED
received buffer from 0.0.0.0:68 to 255.255.255.255:67 over interface ens192
2019-06-20 15:26:55.277 DEBUG [kea-dhcp4.options/32] DHCP4_BUFFER_UNPACK
parsing buffer received from 0.0.0.0 to 255.255.255.255 over interface
ens192
2019-06-20 15:26:55.278 DEBUG [kea-dhcp4.dhcpsrv/32]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-06-20 15:26:55.278 DEBUG [kea-dhcp4.packets/32] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: the subnet with ID 1 was selected for client assignments
2019-06-20 15:26:55.278 DEBUG [kea-dhcp4.packets/32] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: the selected subnet details: 10.172.0.0/24
2019-06-20 15:26:55.278 DEBUG [kea-dhcp4.packets/32] DHCP4_PACKET_RECEIVED
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: DHCPDISCOVER (type 1) received from 0.0.0.0 to
255.255.255.255 on interface ens192
2019-06-20 15:26:55.279 DEBUG [kea-dhcp4.packets/32] DHCP4_QUERY_DATA
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21, packet details: local_address=255.255.255.255:67,
remote_address=0.0.0.0:68, msg_type=DHCPDISCOVER (1), transid=0xebbcfb21,
options:
  type=053, len=001: 1 (uint8)
  type=055, len=008: 1(uint8) 3(uint8) 12(uint8) 15(uint8) 6(uint8)
33(uint8) 121(uint8) 42(uint8)
  type=057, len=002: 576 (uint16)
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00
2019-06-20 15:26:55.279 DEBUG [kea-dhcp4.dhcpsrv/32]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-06-20 15:26:55.279 DEBUG [kea-dhcp4.packets/32] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: the subnet with ID 1 was selected for client assignments
2019-06-20 15:26:55.279 DEBUG [kea-dhcp4.packets/32] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: the selected subnet details: 10.172.0.0/24
2019-06-20 15:26:55.279 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 1, identified by hwaddr=00505695C165
2019-06-20 15:26:55.279 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: hwaddr=00505695C165
2019-06-20 15:26:55.279 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=00505695C165,
found 0 host(s)
2019-06-20 15:26:55.279 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 1
and identifier hwaddr=00505695C165
2019-06-20 15:26:55.279 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 1, identified by duid=00020000AB1115934CFB579E9D00
2019-06-20 15:26:55.279 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: duid=00020000AB1115934CFB579E9D00
2019-06-20 15:26:55.279 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier
duid=00020000AB1115934CFB579E9D00, found 0 host(s)
2019-06-20 15:26:55.279 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 1
and identifier duid=00020000AB1115934CFB579E9D00
2019-06-20 15:26:55.279 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 1, identified by
client-id=FF2D1AA13300020000AB1115934CFB579E9D00
2019-06-20 15:26:55.279 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: client-id=FF2D1AA13300020000AB1115934CFB579E9D00
2019-06-20 15:26:55.280 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier
client-id=FF2D1AA13300020000AB1115934CFB579E9D00, found 0 host(s)
2019-06-20 15:26:55.280 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 1
and identifier client-id=FF2D1AA13300020000AB1115934CFB579E9D00
2019-06-20 15:26:55.280 DEBUG [kea-dhcp4.dhcp4/32] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: client packet has been assigned to the following class(es):
UNKNOWN
2019-06-20 15:26:55.280 DEBUG [kea-dhcp4.dhcp4/32] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: client packet has been assigned to the following class(es):
ALL, UNKNOWN
2019-06-20 15:26:55.280 DEBUG [kea-dhcp4.ddns/32]
DHCP4_CLIENT_HOSTNAME_PROCESS [hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: processing client's Hostname option
2019-06-20 15:26:55.280 DEBUG [kea-dhcp4.ddns/32] DHCP4_GENERATE_FQDN
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: client did not send a FQDN or hostname; FQDN will be be
generated for the client
2019-06-20 15:26:55.280 DEBUG [kea-dhcp4.dhcpsrv/32]
DHCPSRV_MYSQL_GET_CLIENTID obtaining IPv4 leases for client ID
ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00
2019-06-20 15:26:55.281 DEBUG [kea-dhcp4.dhcpsrv/32]
DHCPSRV_MYSQL_GET_HWADDR obtaining IPv4 leases for hardware address hwtype=1
00:50:56:95:c1:65
2019-06-20 15:26:55.282 DEBUG [kea-dhcp4.alloc-engine/32]
ALLOC_ENGINE_V4_OFFER_NEW_LEASE allocation engine will try to offer new
lease to the client [hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21
2019-06-20 15:26:55.282 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4 get one host with reservation for
subnet id 1 and IPv4 address 10.172.0.151
2019-06-20 15:26:55.283 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_ADDRESS4 get all hosts with reservations for IPv4 address
10.172.0.151
2019-06-20 15:26:55.283 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_ADDRESS4_COUNT using address 10.172.0.151, found 0
host(s)
2019-06-20 15:26:55.283 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4_NULL host not found using subnet id 1
and address 10.172.0.151
2019-06-20 15:26:55.283 DEBUG [kea-dhcp4.dhcpsrv/32] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.151
2019-06-20 15:26:55.284 DEBUG [kea-dhcp4.dhcpsrv/32] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.151
2019-06-20 15:26:55.285 INFO  [kea-dhcp4.leases/32] DHCP4_LEASE_ADVERT
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: lease 10.172.0.151 will be advertised
2019-06-20 15:26:55.286 DEBUG [kea-dhcp4.ddns/32]
DHCP4_RESPONSE_HOSTNAME_GENERATE [hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: server has generated hostname
ip-10-172-0-151.eu-ldn-west.compute.internal for the client
2019-06-20 15:26:55.286 DEBUG [kea-dhcp4.options/32] DHCP4_PACKET_PACK
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: preparing on-wire format of the packet to be sent
2019-06-20 15:26:55.286 DEBUG [kea-dhcp4.packets/32] DHCP4_PACKET_SEND
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: trying to send packet DHCPOFFER (type 2) from 10.172.0.25:67
to 10.172.0.151:68 on interface ens192
2019-06-20 15:26:55.287 DEBUG [kea-dhcp4.packets/32] DHCP4_RESPONSE_DATA
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: responding with packet DHCPOFFER (type 2), packet details:
local_address=10.172.0.25:67, remote_address=10.172.0.151:68,
msg_type=DHCPOFFER (2), transid=0xebbcfb21,
options:
  type=001, len=004: 4294967040 (uint32)
  type=003, len=004: 10.172.0.1
  type=006, len=004: 10.172.0.42
  type=012, len=044: "ip-10-172-0-151.eu-ldn-west.compute.internal"
(string)
  type=051, len=004: 3600 (uint32)
  type=053, len=001: 2 (uint8)
  type=054, len=004: 10.172.0.25
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00
2019-06-20 15:26:55.287 DEBUG [kea-dhcp4.packets/32] DHCP4_BUFFER_RECEIVED
received buffer from 0.0.0.0:68 to 255.255.255.255:67 over interface ens192
2019-06-20 15:26:55.288 DEBUG [kea-dhcp4.options/32] DHCP4_BUFFER_UNPACK
parsing buffer received from 0.0.0.0 to 255.255.255.255 over interface
ens192
2019-06-20 15:26:55.288 DEBUG [kea-dhcp4.dhcpsrv/32]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-06-20 15:26:55.288 DEBUG [kea-dhcp4.packets/32] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: the subnet with ID 1 was selected for client assignments
2019-06-20 15:26:55.289 DEBUG [kea-dhcp4.packets/32] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: the selected subnet details: 10.172.0.0/24
2019-06-20 15:26:55.289 DEBUG [kea-dhcp4.packets/32] DHCP4_PACKET_RECEIVED
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: DHCPREQUEST (type 3) received from 0.0.0.0 to
255.255.255.255 on interface ens192
2019-06-20 15:26:55.289 DEBUG [kea-dhcp4.packets/32] DHCP4_QUERY_DATA
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21, packet details: local_address=255.255.255.255:67,
remote_address=0.0.0.0:68, msg_type=DHCPREQUEST (3), transid=0xebbcfb21,
options:
  type=050, len=004: 10.172.0.151 (ipv4-address)
  type=053, len=001: 3 (uint8)
  type=054, len=004: 10.172.0.25 (ipv4-address)
  type=055, len=008: 1(uint8) 3(uint8) 12(uint8) 15(uint8) 6(uint8)
33(uint8) 121(uint8) 42(uint8)
  type=057, len=002: 576 (uint16)
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00
2019-06-20 15:26:55.290 DEBUG [kea-dhcp4.dhcpsrv/32]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-06-20 15:26:55.290 DEBUG [kea-dhcp4.packets/32] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: the subnet with ID 1 was selected for client assignments
2019-06-20 15:26:55.290 DEBUG [kea-dhcp4.packets/32] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: the selected subnet details: 10.172.0.0/24
2019-06-20 15:26:55.291 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 1, identified by hwaddr=00505695C165
2019-06-20 15:26:55.291 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: hwaddr=00505695C165
2019-06-20 15:26:55.291 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=00505695C165,
found 0 host(s)
2019-06-20 15:26:55.291 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 1
and identifier hwaddr=00505695C165
2019-06-20 15:26:55.292 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 1, identified by duid=00020000AB1115934CFB579E9D00
2019-06-20 15:26:55.292 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: duid=00020000AB1115934CFB579E9D00
2019-06-20 15:26:55.292 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier
duid=00020000AB1115934CFB579E9D00, found 0 host(s)
2019-06-20 15:26:55.292 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 1
and identifier duid=00020000AB1115934CFB579E9D00
2019-06-20 15:26:55.293 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 1, identified by
client-id=FF2D1AA13300020000AB1115934CFB579E9D00
2019-06-20 15:26:55.293 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: client-id=FF2D1AA13300020000AB1115934CFB579E9D00
2019-06-20 15:26:55.293 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier
client-id=FF2D1AA13300020000AB1115934CFB579E9D00, found 0 host(s)
2019-06-20 15:26:55.294 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 1
and identifier client-id=FF2D1AA13300020000AB1115934CFB579E9D00
2019-06-20 15:26:55.294 DEBUG [kea-dhcp4.dhcp4/32] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: client packet has been assigned to the following class(es):
UNKNOWN
2019-06-20 15:26:55.294 DEBUG [kea-dhcp4.dhcp4/32] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: client packet has been assigned to the following class(es):
ALL, UNKNOWN
2019-06-20 15:26:55.294 DEBUG [kea-dhcp4.ddns/32]
DHCP4_CLIENT_HOSTNAME_PROCESS [hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: processing client's Hostname option
2019-06-20 15:26:55.295 DEBUG [kea-dhcp4.ddns/32] DHCP4_GENERATE_FQDN
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: client did not send a FQDN or hostname; FQDN will be be
generated for the client
2019-06-20 15:26:55.295 DEBUG [kea-dhcp4.dhcpsrv/32]
DHCPSRV_MYSQL_GET_CLIENTID obtaining IPv4 leases for client ID
ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00
2019-06-20 15:26:55.296 DEBUG [kea-dhcp4.dhcpsrv/32]
DHCPSRV_MYSQL_GET_HWADDR obtaining IPv4 leases for hardware address hwtype=1
00:50:56:95:c1:65
2019-06-20 15:26:55.297 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4 get one host with reservation for
subnet id 1 and IPv4 address 10.172.0.151
2019-06-20 15:26:55.297 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_ADDRESS4 get all hosts with reservations for IPv4 address
10.172.0.151
2019-06-20 15:26:55.297 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ALL_ADDRESS4_COUNT using address 10.172.0.151, found 0
host(s)
2019-06-20 15:26:55.298 DEBUG [kea-dhcp4.hosts/32]
HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4_NULL host not found using subnet id 1
and address 10.172.0.151
2019-06-20 15:26:55.298 DEBUG [kea-dhcp4.dhcpsrv/32] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.151
2019-06-20 15:26:55.299 DEBUG [kea-dhcp4.alloc-engine/32]
ALLOC_ENGINE_V4_REQUEST_ALLOC_REQUESTED [hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: trying to allocate requested address 10.172.0.151
2019-06-20 15:26:55.299 DEBUG [kea-dhcp4.dhcpsrv/32] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.151
2019-06-20 15:26:55.300 DEBUG [kea-dhcp4.dhcpsrv/32] DHCPSRV_MYSQL_ADD_ADDR4
adding IPv4 lease with address 10.172.0.151
2019-06-20 15:26:55.303 INFO  [kea-dhcp4.leases/32] DHCP4_LEASE_ALLOC
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: lease 10.172.0.151 has been allocated
2019-06-20 15:26:55.303 DEBUG [kea-dhcp4.ddns/32]
DHCP4_RESPONSE_HOSTNAME_GENERATE [hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: server has generated hostname
ip-10-172-0-151.eu-ldn-west.compute.internal for the client
2019-06-20 15:26:55.303 DEBUG [kea-dhcp4.dhcpsrv/32]
DHCPSRV_MYSQL_UPDATE_ADDR4 updating IPv4 lease for address 10.172.0.151
2019-06-20 15:26:55.306 DEBUG [kea-dhcp4.ddns/32] DHCP4_NCR_CREATE [hwtype=1
00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: DDNS updates enabled, therefore sending name change
requests
2019-06-20 15:26:55.306 DEBUG [kea-dhcp4.dhcpsrv/32] DHCPSRV_QUEUE_NCR
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00]: name change
request to add DNS entry queued: Type: 0 (CHG_ADD)
Forward Change: yes
Reverse Change: yes
FQDN: [ip-10-172-0-151.eu-ldn-west.compute.internal.]
IP Address: [10.172.0.151]
DHCID:
[0001018671379D3841F260EB758036C75705D1572C79DC445091A7491A6D479C6A0D82]
Lease Expires On: 20190620162655
Lease Length: 3600

2019-06-20 15:26:55.307 DEBUG [kea-dhcp4.options/32] DHCP4_PACKET_PACK
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: preparing on-wire format of the packet to be sent
2019-06-20 15:26:55.307 DEBUG [kea-dhcp4.packets/32] DHCP4_PACKET_SEND
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: trying to send packet DHCPACK (type 5) from 10.172.0.25:67
to 10.172.0.151:68 on interface ens192
2019-06-20 15:26:55.307 DEBUG [kea-dhcp4.packets/32] DHCP4_RESPONSE_DATA
[hwtype=1 00:50:56:95:c1:65],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00],
tid=0xebbcfb21: responding with packet DHCPACK (type 5), packet details:
local_address=10.172.0.25:67, remote_address=10.172.0.151:68,
msg_type=DHCPACK (5), transid=0xebbcfb21,
options:
  type=001, len=004: 4294967040 (uint32)
  type=003, len=004: 10.172.0.1
  type=006, len=004: 10.172.0.42
  type=012, len=044: "ip-10-172-0-151.eu-ldn-west.compute.internal"
(string)
  type=051, len=004: 3600 (uint32)
  type=053, len=001: 5 (uint8)
  type=054, len=004: 10.172.0.25
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:15:93:4c:fb:57:9e:9d:00
2019-06-20 15:26:55.308 DEBUG [kea-dhcp4.dhcpsrv/32]
DHCPSRV_DHCP_DDNS_NCR_SENT NameChangeRequest sent to kea-dhcp-ddns: Type: 0
(CHG_ADD)
Forward Change: yes
Reverse Change: yes
FQDN: [ip-10-172-0-151.eu-ldn-west.compute.internal.]
IP Address: [10.172.0.151]
DHCID:
[0001018671379D3841F260EB758036C75705D1572C79DC445091A7491A6D479C6A0D82]
Lease Expires On: 20190620162655
Lease Length: 3600





--
Sent from: http://kea-users.7364.n8.nabble.com/
_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] kea hands out 2 ip addresses

Sten Carlsen
Looks to me that like the client is identified in multiple ways, by hwaddr and by client_id. These will be seen as two different hosts.

Please see below, note the difference in the green highlights:

On 25/06/2019 20.40, eacool wrote:
Hi, keadhcp is currently handing out 2 ip addresses to each client
unnecessarily in short succession.  It hands out the first ip address, it
then replaces the first ip address with a second one a few seconds later and
then eventually expires the lease on the first ip address.  Please note the
short lease time is for testing and this issue occurs when the lease is set
to an hour also.

This also occurs to clients that are windows and linux based so I am pretty
sure my client settings are not the issue either.

My expected behaviour is that keadhcp hands out a single ip address to a
client.

My client has 1 interface 

1) client spins up 
2) requests ip address 
3) kea supplies ipaddress 
4) keaddns then hands off dns name to powerdns 
5) client then requests another ip address 
6) kea supplies 2nd ip address, this then replaces the first ip address and
dns name on the client 
7) kea then hands off 2nd dns name to powerdns. 
8) lease expires on 1st ip address and is reclaimed by kea and removed from
powerdns. 


for subnet id 1, identified by hwaddr=00505695C165 

for subnet id 1, identified by duid=00020000AB1160F187C05CAA916D 

for subnet id 1, identified by client-id=FF2D1AA13300020000AB1160F187C05CAA916D 



for subnet id 1, identified by hwaddr=00505695C165 

for subnet id 1, identified by duid=00020000AB1115934CFB579E9D00 

for subnet id 1, identified by client-id=FF2D1AA13300020000AB1115934CFB579E9D00 



for subnet id 1, identified by hwaddr=00505695C165 

for subnet id 1, identified by duid=00020000AB1115934CFB579E9D00 

for subnet id 1, identified by client-id=FF2D1AA13300020000AB1115934CFB579E9D00 






--
Sent from: http://kea-users.7364.n8.nabble.com/
_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users


_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] kea hands out 2 ip addresses

eacool
Thanks Sten, is there is there any way I can force it to only identify the
client in a single consistent way so that it is seen as a single host?







--
Sent from: http://kea-users.7364.n8.nabble.com/
_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] kea hands out 2 ip addresses

Sten Carlsen

On 26-06-2019 08.50, eacool wrote:
> Thanks Sten, is there is there any way I can force it to only identify the
> client in a single consistent way so that it is seen as a single host?

I believe there is, I don't use KEA, so I am not certain what the exact
command is. I expect others can supply that.

What you want is to use the hwaddr as the key. I assume the man will
provide the answer.

>
>
>
>
>
>
>
> --
> Sent from: http://kea-users.7364.n8.nabble.com/
> _______________________________________________
> Kea-users mailing list
> [hidden email]
> https://lists.isc.org/mailman/listinfo/kea-users

--
Best regards

Sten Carlsen

No improvements come from shouting:

"MALE BOVINE MANURE!!!"

_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] kea hands out 2 ip addresses

Anders Löwinger
In reply to this post by eacool
On 2019-06-26 08:50, eacool wrote:
> Thanks Sten, is there is there any way I can force it to only identify the
> client in a single consistent way so that it is seen as a single host?

check the "match-client-id" option.


--
Regards
Anders Löwinger
 

_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] kea hands out 2 ip addresses

TroYy
In reply to this post by eacool
Your solution is to add into config file this line:

"host-reservation-identifiers": [ "hw-address" ]

more detailed information is  here
<https://downloads.isc.org/isc/kea/cur/doc/kea-guide.html#reservations4-tuning>  



--
Sent from: http://kea-users.7364.n8.nabble.com/
_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] kea hands out 2 ip addresses

eacool
This post was updated on .
I have made the suggested alterations to the conf file.

However the same behaviour is happening, apologies if I have missed
something simple but I think I have followed the manual correctly.  I have
included a log snippet for the creation of a single machine which has 2 ip
addresses incorrectly assigned to it in short succession.

{
  "Dhcp4": {
    "interfaces-config": {
      "interfaces": [
        "*"
      ],
      "dhcp-socket-type": "raw"
    },
    "lease-database": {
      "type": "mysql",
      "name": "keadhcp",
      "host": "10.172.0.30",
      "user": "keadhcp",
      "password": "password"
    },
    "expired-leases-processing": {
      "reclaim-timer-wait-time": 10,
      "flush-reclaimed-timer-wait-time": 25,
      "hold-reclaimed-time": 360,
      "max-reclaim-leases": 100,
      "max-reclaim-time": 250,
      "unwarned-reclaim-cycles": 5
    },
    "dhcp-ddns": {
      "enable-updates": true,
      "qualifying-suffix": "eu-ldn-west.compute.internal",
      "replace-client-name": "always",
      "generated-prefix": "ip"
    },
    "valid-lifetime": 300,
    "host-reservation-identifiers": [ "hw-address" ],
    "subnet4": [
      {
        "subnet": "10.172.0.0/24",
        "pools": [
          {
            "pool": "10.172.0.150 - 10.172.0.200"
          }
        ],
        "option-data": [
          {
            "name": "routers",
            "data": "10.172.0.1"
          },
          {
            "name": "domain-name-servers",
            "data": "10.172.0.42"
          }
        ]
      }
    ]
  },
 "Logging": {
      "loggers": [
          {
              "name": "kea-dhcp4",
              "output_options": [
                  {
                      "output": "/var/log/kea-dhcp4.log"
                  }
              ],
              "severity": "DEBUG",
              "debuglevel": 99
          }
      ]
  }
}

############################################################

2019-07-11 11:06:16.291 DEBUG [kea-dhcp4.packets/33] DHCP4_BUFFER_RECEIVED
received buffer from 0.0.0.0:68 to 255.255.255.255:67 over interface ens192
2019-07-11 11:06:16.292 DEBUG [kea-dhcp4.options/33] DHCP4_BUFFER_UNPACK
parsing buffer received from 0.0.0.0 to 255.255.255.255 over interface
ens192
2019-07-11 11:06:16.292 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-07-11 11:06:16.293 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: the subnet with ID 1 was selected for client assignments
2019-07-11 11:06:16.293 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: the selected subnet details: 10.172.0.0/24
2019-07-11 11:06:16.293 DEBUG [kea-dhcp4.packets/33] DHCP4_PACKET_RECEIVED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: DHCPDISCOVER (type 1) received from 0.0.0.0 to
255.255.255.255 on interface ens192
2019-07-11 11:06:16.294 DEBUG [kea-dhcp4.packets/33] DHCP4_QUERY_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a, packet details: local_address=255.255.255.255:67,
remote_address=0.0.0.0:68, msg_type=DHCPDISCOVER (1), transid=0xefbdc39a,
options:
  type=053, len=001: 1 (uint8)
  type=055, len=009: 1(uint8) 3(uint8) 12(uint8) 15(uint8) 6(uint8)
26(uint8) 33(uint8) 121(uint8) 42(uint8)
  type=057, len=002: 576 (uint16)
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29
2019-07-11 11:06:16.294 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-07-11 11:06:16.294 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: the subnet with ID 1 was selected for client assignments
2019-07-11 11:06:16.295 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: the selected subnet details: 10.172.0.0/24
2019-07-11 11:06:16.295 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 0, identified by hwaddr=005056955CE5
2019-07-11 11:06:16.295 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: hwaddr=005056955CE5
2019-07-11 11:06:16.296 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=005056955CE5,
found 0 host(s)
2019-07-11 11:06:16.296 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 0
and identifier hwaddr=005056955CE5
2019-07-11 11:06:16.296 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 1, identified by hwaddr=005056955CE5
2019-07-11 11:06:16.296 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: hwaddr=005056955CE5
2019-07-11 11:06:16.297 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=005056955CE5,
found 0 host(s)
2019-07-11 11:06:16.297 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 1
and identifier hwaddr=005056955CE5
2019-07-11 11:06:16.297 DEBUG [kea-dhcp4.dhcp4/33] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: client packet has been assigned to the following class(es):
UNKNOWN
2019-07-11 11:06:16.298 DEBUG [kea-dhcp4.dhcp4/33] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: client packet has been assigned to the following class(es):
ALL, UNKNOWN
2019-07-11 11:06:16.298 DEBUG [kea-dhcp4.ddns/33]
DHCP4_CLIENT_HOSTNAME_PROCESS [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: processing client's Hostname option
2019-07-11 11:06:16.298 DEBUG [kea-dhcp4.ddns/33] DHCP4_GENERATE_FQDN
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: client did not send a FQDN or hostname; FQDN will be be
generated for the client
2019-07-11 11:06:16.299 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_GET_CLIENTID obtaining IPv4 leases for client ID
ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29
2019-07-11 11:06:16.300 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_GET_HWADDR obtaining IPv4 leases for hardware address hwtype=1
00:50:56:95:5c:e5
2019-07-11 11:06:16.301 DEBUG [kea-dhcp4.alloc-engine/33]
ALLOC_ENGINE_V4_OFFER_NEW_LEASE allocation engine will try to offer new
lease to the client [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a
2019-07-11 11:06:16.301 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.166
2019-07-11 11:06:16.302 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.166
2019-07-11 11:06:16.303 INFO  [kea-dhcp4.leases/33] DHCP4_LEASE_ADVERT
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: lease 10.172.0.166 will be advertised
2019-07-11 11:06:16.303 DEBUG [kea-dhcp4.ddns/33]
DHCP4_RESPONSE_HOSTNAME_GENERATE [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: server has generated hostname
ip-10-172-0-166.eu-ldn-west.compute.internal for the client
2019-07-11 11:06:16.304 DEBUG [kea-dhcp4.options/33] DHCP4_PACKET_PACK
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: preparing on-wire format of the packet to be sent
2019-07-11 11:06:16.304 DEBUG [kea-dhcp4.packets/33] DHCP4_PACKET_SEND
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: trying to send packet DHCPOFFER (type 2) from 10.172.0.25:67
to 10.172.0.166:68 on interface ens192
2019-07-11 11:06:16.305 DEBUG [kea-dhcp4.packets/33] DHCP4_RESPONSE_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: responding with packet DHCPOFFER (type 2), packet details:
local_address=10.172.0.25:67, remote_address=10.172.0.166:68,
msg_type=DHCPOFFER (2), transid=0xefbdc39a,
options:
  type=001, len=004: 4294967040 (uint32)
  type=003, len=004: 10.172.0.1
  type=006, len=004: 10.172.0.42
  type=012, len=044: "ip-10-172-0-166.eu-ldn-west.compute.internal" (string)
  type=051, len=004: 300 (uint32)
  type=053, len=001: 2 (uint8)
  type=054, len=004: 10.172.0.25
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29
2019-07-11 11:06:16.305 DEBUG [kea-dhcp4.packets/33] DHCP4_BUFFER_RECEIVED
received buffer from 0.0.0.0:68 to 255.255.255.255:67 over interface ens192
2019-07-11 11:06:16.306 DEBUG [kea-dhcp4.options/33] DHCP4_BUFFER_UNPACK
parsing buffer received from 0.0.0.0 to 255.255.255.255 over interface
ens192
2019-07-11 11:06:16.306 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-07-11 11:06:16.306 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: the subnet with ID 1 was selected for client assignments
2019-07-11 11:06:16.307 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: the selected subnet details: 10.172.0.0/24
2019-07-11 11:06:16.307 DEBUG [kea-dhcp4.packets/33] DHCP4_PACKET_RECEIVED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: DHCPREQUEST (type 3) received from 0.0.0.0 to
255.255.255.255 on interface ens192
2019-07-11 11:06:16.307 DEBUG [kea-dhcp4.packets/33] DHCP4_QUERY_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a, packet details: local_address=255.255.255.255:67,
remote_address=0.0.0.0:68, msg_type=DHCPREQUEST (3), transid=0xefbdc39a,
options:
  type=050, len=004: 10.172.0.166 (ipv4-address)
  type=053, len=001: 3 (uint8)
  type=054, len=004: 10.172.0.25 (ipv4-address)
  type=055, len=009: 1(uint8) 3(uint8) 12(uint8) 15(uint8) 6(uint8)
26(uint8) 33(uint8) 121(uint8) 42(uint8)
  type=057, len=002: 576 (uint16)
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29
2019-07-11 11:06:16.308 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-07-11 11:06:16.308 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: the subnet with ID 1 was selected for client assignments
2019-07-11 11:06:16.308 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: the selected subnet details: 10.172.0.0/24
2019-07-11 11:06:16.309 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 0, identified by hwaddr=005056955CE5
2019-07-11 11:06:16.309 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: hwaddr=005056955CE5
2019-07-11 11:06:16.309 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=005056955CE5,
found 0 host(s)
2019-07-11 11:06:16.310 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 0
and identifier hwaddr=005056955CE5
2019-07-11 11:06:16.310 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 1, identified by hwaddr=005056955CE5
2019-07-11 11:06:16.310 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: hwaddr=005056955CE5
2019-07-11 11:06:16.310 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=005056955CE5,
found 0 host(s)
2019-07-11 11:06:16.311 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 1
and identifier hwaddr=005056955CE5
2019-07-11 11:06:16.312 DEBUG [kea-dhcp4.dhcp4/33] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: client packet has been assigned to the following class(es):
UNKNOWN
2019-07-11 11:06:16.312 DEBUG [kea-dhcp4.dhcp4/33] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: client packet has been assigned to the following class(es):
ALL, UNKNOWN
2019-07-11 11:06:16.312 DEBUG [kea-dhcp4.ddns/33]
DHCP4_CLIENT_HOSTNAME_PROCESS [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: processing client's Hostname option
2019-07-11 11:06:16.313 DEBUG [kea-dhcp4.ddns/33] DHCP4_GENERATE_FQDN
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: client did not send a FQDN or hostname; FQDN will be be
generated for the client
2019-07-11 11:06:16.313 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_GET_CLIENTID obtaining IPv4 leases for client ID
ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29
2019-07-11 11:06:16.314 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_GET_HWADDR obtaining IPv4 leases for hardware address hwtype=1
00:50:56:95:5c:e5
2019-07-11 11:06:16.315 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.166
2019-07-11 11:06:16.316 DEBUG [kea-dhcp4.alloc-engine/33]
ALLOC_ENGINE_V4_REQUEST_ALLOC_REQUESTED [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: trying to allocate requested address 10.172.0.166
2019-07-11 11:06:16.316 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.166
2019-07-11 11:06:16.317 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_MYSQL_ADD_ADDR4
adding IPv4 lease with address 10.172.0.166
2019-07-11 11:06:16.320 INFO  [kea-dhcp4.leases/33] DHCP4_LEASE_ALLOC
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: lease 10.172.0.166 has been allocated
2019-07-11 11:06:16.321 DEBUG [kea-dhcp4.ddns/33]
DHCP4_RESPONSE_HOSTNAME_GENERATE [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: server has generated hostname
ip-10-172-0-166.eu-ldn-west.compute.internal for the client
2019-07-11 11:06:16.321 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_UPDATE_ADDR4 updating IPv4 lease for address 10.172.0.166
2019-07-11 11:06:16.324 DEBUG [kea-dhcp4.ddns/33] DHCP4_NCR_CREATE [hwtype=1
00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: DDNS updates enabled, therefore sending name change requests
2019-07-11 11:06:16.324 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_QUEUE_NCR
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29]: name change
request to add DNS entry queued: Type: 0 (CHG_ADD)
Forward Change: yes
Reverse Change: yes
FQDN: [ip-10-172-0-166.eu-ldn-west.compute.internal.]
IP Address: [10.172.0.166]
DHCID:
[0001018F0CD741AADEFE6F93552FB712475482E6A9BFA02258757BD52E59D7661C0706]
Lease Expires On: 20190711111116
Lease Length: 300

2019-07-11 11:06:16.326 DEBUG [kea-dhcp4.options/33] DHCP4_PACKET_PACK
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: preparing on-wire format of the packet to be sent
2019-07-11 11:06:16.326 DEBUG [kea-dhcp4.packets/33] DHCP4_PACKET_SEND
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: trying to send packet DHCPACK (type 5) from 10.172.0.25:67
to 10.172.0.166:68 on interface ens192
2019-07-11 11:06:16.327 DEBUG [kea-dhcp4.packets/33] DHCP4_RESPONSE_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: responding with packet DHCPACK (type 5), packet details:
local_address=10.172.0.25:67, remote_address=10.172.0.166:68,
msg_type=DHCPACK (5), transid=0xefbdc39a,
options:
  type=001, len=004: 4294967040 (uint32)
  type=003, len=004: 10.172.0.1
  type=006, len=004: 10.172.0.42
  type=012, len=044: "ip-10-172-0-166.eu-ldn-west.compute.internal" (string)
  type=051, len=004: 300 (uint32)
  type=053, len=001: 5 (uint8)
  type=054, len=004: 10.172.0.25
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29
2019-07-11 11:06:16.327 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_DHCP_DDNS_NCR_SENT NameChangeRequest sent to kea-dhcp-ddns: Type: 0
(CHG_ADD)
Forward Change: yes
Reverse Change: yes
FQDN: [ip-10-172-0-166.eu-ldn-west.compute.internal.]
IP Address: [10.172.0.166]
DHCID:
[0001018F0CD741AADEFE6F93552FB712475482E6A9BFA02258757BD52E59D7661C0706]
Lease Expires On: 20190711111116
Lease Length: 300

2019-07-11 11:06:23.336 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer:
flush-reclaimed-leases
2019-07-11 11:06:23.336 DEBUG [kea-dhcp4.alloc-engine/33]
ALLOC_ENGINE_V4_RECLAIMED_LEASES_DELETE begin deletion of reclaimed leases
expired more than 360 seconds ago
2019-07-11 11:06:23.336 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_DELETE_EXPIRED_RECLAIMED4 deleting reclaimed IPv4 leases that
expired more than 360 seconds ago
2019-07-11 11:06:23.338 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_DELETED_EXPIRED_RECLAIMED deleted 0 reclaimed leases from the
database
2019-07-11 11:06:23.338 DEBUG [kea-dhcp4.alloc-engine/33]
ALLOC_ENGINE_V4_RECLAIMED_LEASES_DELETE_COMPLETE successfully deleted 0
expired-reclaimed leases
2019-07-11 11:06:23.338 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_TIMERMGR_START_TIMER starting timer: flush-reclaimed-leases
2019-07-11 11:06:23.804 DEBUG [kea-dhcp4.packets/33] DHCP4_BUFFER_RECEIVED
received buffer from 0.0.0.0:68 to 255.255.255.255:67 over interface ens192
2019-07-11 11:06:23.804 DEBUG [kea-dhcp4.options/33] DHCP4_BUFFER_UNPACK
parsing buffer received from 0.0.0.0 to 255.255.255.255 over interface
ens192
2019-07-11 11:06:23.804 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-07-11 11:06:23.804 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: the subnet with ID 1 was selected for client assignments
2019-07-11 11:06:23.805 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: the selected subnet details: 10.172.0.0/24
2019-07-11 11:06:23.805 DEBUG [kea-dhcp4.packets/33] DHCP4_PACKET_RECEIVED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: DHCPDISCOVER (type 1) received from 0.0.0.0 to
255.255.255.255 on interface ens192
2019-07-11 11:06:23.805 DEBUG [kea-dhcp4.packets/33] DHCP4_QUERY_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d, packet details: local_address=255.255.255.255:67,
remote_address=0.0.0.0:68, msg_type=DHCPDISCOVER (1), transid=0x8181914d,
options:
  type=053, len=001: 1 (uint8)
  type=055, len=008: 1(uint8) 3(uint8) 12(uint8) 15(uint8) 6(uint8)
33(uint8) 121(uint8) 42(uint8)
  type=057, len=002: 576 (uint16)
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c
2019-07-11 11:06:23.806 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-07-11 11:06:23.806 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: the subnet with ID 1 was selected for client assignments
2019-07-11 11:06:23.806 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: the selected subnet details: 10.172.0.0/24
2019-07-11 11:06:23.806 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 0, identified by hwaddr=005056955CE5
2019-07-11 11:06:23.806 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: hwaddr=005056955CE5
2019-07-11 11:06:23.806 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=005056955CE5,
found 0 host(s)
2019-07-11 11:06:23.806 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 0
and identifier hwaddr=005056955CE5
2019-07-11 11:06:23.807 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 1, identified by hwaddr=005056955CE5
2019-07-11 11:06:23.807 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: hwaddr=005056955CE5
2019-07-11 11:06:23.807 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=005056955CE5,
found 0 host(s)
2019-07-11 11:06:23.807 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 1
and identifier hwaddr=005056955CE5
2019-07-11 11:06:23.808 DEBUG [kea-dhcp4.dhcp4/33] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: client packet has been assigned to the following class(es):
UNKNOWN
2019-07-11 11:06:23.808 DEBUG [kea-dhcp4.dhcp4/33] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: client packet has been assigned to the following class(es):
ALL, UNKNOWN
2019-07-11 11:06:23.808 DEBUG [kea-dhcp4.ddns/33]
DHCP4_CLIENT_HOSTNAME_PROCESS [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: processing client's Hostname option
2019-07-11 11:06:23.809 DEBUG [kea-dhcp4.ddns/33] DHCP4_GENERATE_FQDN
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: client did not send a FQDN or hostname; FQDN will be be
generated for the client
2019-07-11 11:06:23.809 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_GET_CLIENTID obtaining IPv4 leases for client ID
ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c
2019-07-11 11:06:23.811 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_GET_HWADDR obtaining IPv4 leases for hardware address hwtype=1
00:50:56:95:5c:e5
2019-07-11 11:06:23.812 DEBUG [kea-dhcp4.alloc-engine/33]
ALLOC_ENGINE_V4_OFFER_NEW_LEASE allocation engine will try to offer new
lease to the client [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d
2019-07-11 11:06:23.813 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.167
2019-07-11 11:06:23.813 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.167
2019-07-11 11:06:23.814 INFO  [kea-dhcp4.leases/33] DHCP4_LEASE_ADVERT
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: lease 10.172.0.167 will be advertised
2019-07-11 11:06:23.815 DEBUG [kea-dhcp4.ddns/33]
DHCP4_RESPONSE_HOSTNAME_GENERATE [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: server has generated hostname
ip-10-172-0-167.eu-ldn-west.compute.internal for the client
2019-07-11 11:06:23.815 DEBUG [kea-dhcp4.options/33] DHCP4_PACKET_PACK
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: preparing on-wire format of the packet to be sent
2019-07-11 11:06:23.815 DEBUG [kea-dhcp4.packets/33] DHCP4_PACKET_SEND
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: trying to send packet DHCPOFFER (type 2) from 10.172.0.25:67
to 10.172.0.167:68 on interface ens192
2019-07-11 11:06:23.816 DEBUG [kea-dhcp4.packets/33] DHCP4_RESPONSE_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: responding with packet DHCPOFFER (type 2), packet details:
local_address=10.172.0.25:67, remote_address=10.172.0.167:68,
msg_type=DHCPOFFER (2), transid=0x8181914d,
options:
  type=001, len=004: 4294967040 (uint32)
  type=003, len=004: 10.172.0.1
  type=006, len=004: 10.172.0.42
  type=012, len=044: "ip-10-172-0-167.eu-ldn-west.compute.internal" (string)
  type=051, len=004: 300 (uint32)
  type=053, len=001: 2 (uint8)
  type=054, len=004: 10.172.0.25
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c
2019-07-11 11:06:23.816 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer:
reclaim-expired-leases
2019-07-11 11:06:23.817 DEBUG [kea-dhcp4.alloc-engine/33]
ALLOC_ENGINE_V4_LEASES_RECLAMATION_START starting reclamation of expired
leases (limit = 100 leases or 250 milliseconds)
2019-07-11 11:06:23.817 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_GET_EXPIRED4 obtaining maximum 101 of expired IPv4 leases
2019-07-11 11:06:23.818 DEBUG [kea-dhcp4.alloc-engine/33]
ALLOC_ENGINE_V4_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 1.094 ms
2019-07-11 11:06:23.818 DEBUG [kea-dhcp4.alloc-engine/33]
ALLOC_ENGINE_V4_NO_MORE_EXPIRED_LEASES all expired leases have been
reclaimed
2019-07-11 11:06:23.819 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_TIMERMGR_START_TIMER starting timer: reclaim-expired-leases
2019-07-11 11:06:23.819 DEBUG [kea-dhcp4.packets/33] DHCP4_BUFFER_RECEIVED
received buffer from 0.0.0.0:68 to 255.255.255.255:67 over interface ens192
2019-07-11 11:06:23.819 DEBUG [kea-dhcp4.options/33] DHCP4_BUFFER_UNPACK
parsing buffer received from 0.0.0.0 to 255.255.255.255 over interface
ens192
2019-07-11 11:06:23.820 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-07-11 11:06:23.820 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: the subnet with ID 1 was selected for client assignments
2019-07-11 11:06:23.821 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: the selected subnet details: 10.172.0.0/24
2019-07-11 11:06:23.821 DEBUG [kea-dhcp4.packets/33] DHCP4_PACKET_RECEIVED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: DHCPREQUEST (type 3) received from 0.0.0.0 to
255.255.255.255 on interface ens192
2019-07-11 11:06:23.821 DEBUG [kea-dhcp4.packets/33] DHCP4_QUERY_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d, packet details: local_address=255.255.255.255:67,
remote_address=0.0.0.0:68, msg_type=DHCPREQUEST (3), transid=0x8181914d,
options:
  type=050, len=004: 10.172.0.167 (ipv4-address)
  type=053, len=001: 3 (uint8)
  type=054, len=004: 10.172.0.25 (ipv4-address)
  type=055, len=008: 1(uint8) 3(uint8) 12(uint8) 15(uint8) 6(uint8)
33(uint8) 121(uint8) 42(uint8)
  type=057, len=002: 576 (uint16)
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c
2019-07-11 11:06:23.822 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-07-11 11:06:23.822 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: the subnet with ID 1 was selected for client assignments
2019-07-11 11:06:23.822 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: the selected subnet details: 10.172.0.0/24
2019-07-11 11:06:23.823 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 0, identified by hwaddr=005056955CE5
2019-07-11 11:06:23.823 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: hwaddr=005056955CE5
2019-07-11 11:06:23.823 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=005056955CE5,
found 0 host(s)
2019-07-11 11:06:23.824 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 0
and identifier hwaddr=005056955CE5
2019-07-11 11:06:23.824 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 1, identified by hwaddr=005056955CE5
2019-07-11 11:06:23.824 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: hwaddr=005056955CE5
2019-07-11 11:06:23.825 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=005056955CE5,
found 0 host(s)
2019-07-11 11:06:23.825 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 1
and identifier hwaddr=005056955CE5
2019-07-11 11:06:23.825 DEBUG [kea-dhcp4.dhcp4/33] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: client packet has been assigned to the following class(es):
UNKNOWN
2019-07-11 11:06:23.826 DEBUG [kea-dhcp4.dhcp4/33] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: client packet has been assigned to the following class(es):
ALL, UNKNOWN
2019-07-11 11:06:23.826 DEBUG [kea-dhcp4.ddns/33]
DHCP4_CLIENT_HOSTNAME_PROCESS [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: processing client's Hostname option
2019-07-11 11:06:23.826 DEBUG [kea-dhcp4.ddns/33] DHCP4_GENERATE_FQDN
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: client did not send a FQDN or hostname; FQDN will be be
generated for the client
2019-07-11 11:06:23.827 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_GET_CLIENTID obtaining IPv4 leases for client ID
ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c
2019-07-11 11:06:23.828 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_GET_HWADDR obtaining IPv4 leases for hardware address hwtype=1
00:50:56:95:5c:e5
2019-07-11 11:06:23.829 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.167
2019-07-11 11:06:23.830 DEBUG [kea-dhcp4.alloc-engine/33]
ALLOC_ENGINE_V4_REQUEST_ALLOC_REQUESTED [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: trying to allocate requested address 10.172.0.167
2019-07-11 11:06:23.830 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.167
2019-07-11 11:06:23.831 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_MYSQL_ADD_ADDR4
adding IPv4 lease with address 10.172.0.167
2019-07-11 11:06:23.834 INFO  [kea-dhcp4.leases/33] DHCP4_LEASE_ALLOC
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: lease 10.172.0.167 has been allocated
2019-07-11 11:06:23.834 DEBUG [kea-dhcp4.ddns/33]
DHCP4_RESPONSE_HOSTNAME_GENERATE [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: server has generated hostname
ip-10-172-0-167.eu-ldn-west.compute.internal for the client
2019-07-11 11:06:23.835 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_UPDATE_ADDR4 updating IPv4 lease for address 10.172.0.167
2019-07-11 11:06:23.838 DEBUG [kea-dhcp4.ddns/33] DHCP4_NCR_CREATE [hwtype=1
00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: DDNS updates enabled, therefore sending name change requests
2019-07-11 11:06:23.839 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_QUEUE_NCR
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c]: name change
request to add DNS entry queued: Type: 0 (CHG_ADD)
Forward Change: yes
Reverse Change: yes
FQDN: [ip-10-172-0-167.eu-ldn-west.compute.internal.]
IP Address: [10.172.0.167]
DHCID:
[000101303B4D06807A49E0704759F754B48892035A495551CDE3F8B3C1B45201904D53]
Lease Expires On: 20190711111123
Lease Length: 300

2019-07-11 11:06:23.840 DEBUG [kea-dhcp4.options/33] DHCP4_PACKET_PACK
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: preparing on-wire format of the packet to be sent
2019-07-11 11:06:23.841 DEBUG [kea-dhcp4.packets/33] DHCP4_PACKET_SEND
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: trying to send packet DHCPACK (type 5) from 10.172.0.25:67
to 10.172.0.167:68 on interface ens192
2019-07-11 11:06:23.841 DEBUG [kea-dhcp4.packets/33] DHCP4_RESPONSE_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: responding with packet DHCPACK (type 5), packet details:
local_address=10.172.0.25:67, remote_address=10.172.0.167:68,
msg_type=DHCPACK (5), transid=0x8181914d,
options:
  type=001, len=004: 4294967040 (uint32)
  type=003, len=004: 10.172.0.1
  type=006, len=004: 10.172.0.42
  type=012, len=044: "ip-10-172-0-167.eu-ldn-west.compute.internal" (string)
  type=051, len=004: 300 (uint32)
  type=053, len=001: 5 (uint8)
  type=054, len=004: 10.172.0.25
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c
2019-07-11 11:06:23.841 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_DHCP_DDNS_NCR_SENT NameChangeRequest sent to kea-dhcp-ddns: Type: 0
(CHG_ADD)
Forward Change: yes
Reverse Change: yes
FQDN: [ip-10-172-0-167.eu-ldn-west.compute.internal.]
IP Address: [10.172.0.167]
DHCID:
[000101303B4D06807A49E0704759F754B48892035A495551CDE3F8B3C1B45201904D53]
Lease Expires On: 20190711111123
Lease Length: 300





--
Sent from: http://kea-users.7364.n8.nabble.com/
_______________________________________________
Kea-users mailing list
Kea-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] kea hands out 2 ip addresses

Klaus Steden

On the outside chance you're using iPXE somewhere in your environment, I had a very similar problem with some of our hardware where it would solicit two separate leases by advertising two different hardware addresses (once during PXE, and once at boot, if memory serves).

I was able to work around the issue by using the kkpxe bootloader, which caches the initial lease request, thus avoiding making a second DHCPREQUEST later on.

That might do the trick, if iPXE is part of your tool chain.

cheers,
Klaus

On Thu, Jul 11, 2019 at 4:08 AM eacool <[hidden email]> wrote:
I have made the suggested alterations to the conf file.

However the same behaviour is happening, apologies if I have missed
something simple but I think I have followed the manual correctly.  I have
included a log snippet for the creation of a single machine which has 2 ip
addresses incorrectly assigned to it in short succession.

{
  "Dhcp4": {
    "interfaces-config": {
      "interfaces": [
        "*"
      ],
      "dhcp-socket-type": "raw"
    },
    "lease-database": {
      "type": "mysql",
      "name": "keadhcp",
      "host": "10.172.0.30",
      "user": "keadhcp",
      "password": "password"
    },
    "expired-leases-processing": {
      "reclaim-timer-wait-time": 10,
      "flush-reclaimed-timer-wait-time": 25,
      "hold-reclaimed-time": 360,
      "max-reclaim-leases": 100,
      "max-reclaim-time": 250,
      "unwarned-reclaim-cycles": 5
    },
    "dhcp-ddns": {
      "enable-updates": true,
      "qualifying-suffix": "eu-ldn-west.compute.internal",
      "replace-client-name": "always",
      "generated-prefix": "ip"
    },
    "valid-lifetime": 300,
*    "host-reservation-identifiers": [ "hw-address" ],*
    "subnet4": [
      {
        "subnet": "10.172.0.0/24",
        "pools": [
          {
            "pool": "10.172.0.150 - 10.172.0.200"
          }
        ],
        "option-data": [
          {
            "name": "routers",
            "data": "10.172.0.1"
          },
          {
            "name": "domain-name-servers",
            "data": "10.172.0.42"
          }
        ]
      }
    ]
  },
 "Logging": {
      "loggers": [
          {
              "name": "kea-dhcp4",
              "output_options": [
                  {
                      "output": "/var/log/kea-dhcp4.log"
                  }
              ],
              "severity": "DEBUG",
              "debuglevel": 99
          }
      ]
  }
}

############################################################

2019-07-11 11:06:16.291 DEBUG [kea-dhcp4.packets/33] DHCP4_BUFFER_RECEIVED
received buffer from 0.0.0.0:68 to 255.255.255.255:67 over interface ens192
2019-07-11 11:06:16.292 DEBUG [kea-dhcp4.options/33] DHCP4_BUFFER_UNPACK
parsing buffer received from 0.0.0.0 to 255.255.255.255 over interface
ens192
2019-07-11 11:06:16.292 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-07-11 11:06:16.293 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: the subnet with ID 1 was selected for client assignments
2019-07-11 11:06:16.293 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: the selected subnet details: 10.172.0.0/24
2019-07-11 11:06:16.293 DEBUG [kea-dhcp4.packets/33] DHCP4_PACKET_RECEIVED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: DHCPDISCOVER (type 1) received from 0.0.0.0 to
255.255.255.255 on interface ens192
2019-07-11 11:06:16.294 DEBUG [kea-dhcp4.packets/33] DHCP4_QUERY_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a, packet details: local_address=255.255.255.255:67,
remote_address=0.0.0.0:68, msg_type=DHCPDISCOVER (1), transid=0xefbdc39a,
options:
  type=053, len=001: 1 (uint8)
  type=055, len=009: 1(uint8) 3(uint8) 12(uint8) 15(uint8) 6(uint8)
26(uint8) 33(uint8) 121(uint8) 42(uint8)
  type=057, len=002: 576 (uint16)
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29
2019-07-11 11:06:16.294 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-07-11 11:06:16.294 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: the subnet with ID 1 was selected for client assignments
2019-07-11 11:06:16.295 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: the selected subnet details: 10.172.0.0/24
2019-07-11 11:06:16.295 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 0, identified by hwaddr=005056955CE5
2019-07-11 11:06:16.295 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: hwaddr=005056955CE5
2019-07-11 11:06:16.296 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=005056955CE5,
found 0 host(s)
2019-07-11 11:06:16.296 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 0
and identifier hwaddr=005056955CE5
2019-07-11 11:06:16.296 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 1, identified by hwaddr=005056955CE5
2019-07-11 11:06:16.296 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: hwaddr=005056955CE5
2019-07-11 11:06:16.297 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=005056955CE5,
found 0 host(s)
2019-07-11 11:06:16.297 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 1
and identifier hwaddr=005056955CE5
2019-07-11 11:06:16.297 DEBUG [kea-dhcp4.dhcp4/33] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: client packet has been assigned to the following class(es):
UNKNOWN
2019-07-11 11:06:16.298 DEBUG [kea-dhcp4.dhcp4/33] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: client packet has been assigned to the following class(es):
ALL, UNKNOWN
2019-07-11 11:06:16.298 DEBUG [kea-dhcp4.ddns/33]
DHCP4_CLIENT_HOSTNAME_PROCESS [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: processing client's Hostname option
2019-07-11 11:06:16.298 DEBUG [kea-dhcp4.ddns/33] DHCP4_GENERATE_FQDN
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: client did not send a FQDN or hostname; FQDN will be be
generated for the client
2019-07-11 11:06:16.299 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_GET_CLIENTID obtaining IPv4 leases for client ID
ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29
2019-07-11 11:06:16.300 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_GET_HWADDR obtaining IPv4 leases for hardware address hwtype=1
00:50:56:95:5c:e5
2019-07-11 11:06:16.301 DEBUG [kea-dhcp4.alloc-engine/33]
ALLOC_ENGINE_V4_OFFER_NEW_LEASE allocation engine will try to offer new
lease to the client [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a
2019-07-11 11:06:16.301 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.166
2019-07-11 11:06:16.302 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.166
2019-07-11 11:06:16.303 INFO  [kea-dhcp4.leases/33] DHCP4_LEASE_ADVERT
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: lease 10.172.0.166 will be advertised
2019-07-11 11:06:16.303 DEBUG [kea-dhcp4.ddns/33]
DHCP4_RESPONSE_HOSTNAME_GENERATE [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: server has generated hostname
ip-10-172-0-166.eu-ldn-west.compute.internal for the client
2019-07-11 11:06:16.304 DEBUG [kea-dhcp4.options/33] DHCP4_PACKET_PACK
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: preparing on-wire format of the packet to be sent
2019-07-11 11:06:16.304 DEBUG [kea-dhcp4.packets/33] DHCP4_PACKET_SEND
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: trying to send packet DHCPOFFER (type 2) from 10.172.0.25:67
to 10.172.0.166:68 on interface ens192
2019-07-11 11:06:16.305 DEBUG [kea-dhcp4.packets/33] DHCP4_RESPONSE_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: responding with packet DHCPOFFER (type 2), packet details:
local_address=10.172.0.25:67, remote_address=10.172.0.166:68,
msg_type=DHCPOFFER (2), transid=0xefbdc39a,
options:
  type=001, len=004: 4294967040 (uint32)
  type=003, len=004: 10.172.0.1
  type=006, len=004: 10.172.0.42
  type=012, len=044: "ip-10-172-0-166.eu-ldn-west.compute.internal" (string)
  type=051, len=004: 300 (uint32)
  type=053, len=001: 2 (uint8)
  type=054, len=004: 10.172.0.25
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29
2019-07-11 11:06:16.305 DEBUG [kea-dhcp4.packets/33] DHCP4_BUFFER_RECEIVED
received buffer from 0.0.0.0:68 to 255.255.255.255:67 over interface ens192
2019-07-11 11:06:16.306 DEBUG [kea-dhcp4.options/33] DHCP4_BUFFER_UNPACK
parsing buffer received from 0.0.0.0 to 255.255.255.255 over interface
ens192
2019-07-11 11:06:16.306 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-07-11 11:06:16.306 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: the subnet with ID 1 was selected for client assignments
2019-07-11 11:06:16.307 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: the selected subnet details: 10.172.0.0/24
2019-07-11 11:06:16.307 DEBUG [kea-dhcp4.packets/33] DHCP4_PACKET_RECEIVED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: DHCPREQUEST (type 3) received from 0.0.0.0 to
255.255.255.255 on interface ens192
2019-07-11 11:06:16.307 DEBUG [kea-dhcp4.packets/33] DHCP4_QUERY_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a, packet details: local_address=255.255.255.255:67,
remote_address=0.0.0.0:68, msg_type=DHCPREQUEST (3), transid=0xefbdc39a,
options:
  type=050, len=004: 10.172.0.166 (ipv4-address)
  type=053, len=001: 3 (uint8)
  type=054, len=004: 10.172.0.25 (ipv4-address)
  type=055, len=009: 1(uint8) 3(uint8) 12(uint8) 15(uint8) 6(uint8)
26(uint8) 33(uint8) 121(uint8) 42(uint8)
  type=057, len=002: 576 (uint16)
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29
2019-07-11 11:06:16.308 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-07-11 11:06:16.308 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: the subnet with ID 1 was selected for client assignments
2019-07-11 11:06:16.308 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: the selected subnet details: 10.172.0.0/24
2019-07-11 11:06:16.309 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 0, identified by hwaddr=005056955CE5
2019-07-11 11:06:16.309 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: hwaddr=005056955CE5
2019-07-11 11:06:16.309 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=005056955CE5,
found 0 host(s)
2019-07-11 11:06:16.310 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 0
and identifier hwaddr=005056955CE5
2019-07-11 11:06:16.310 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 1, identified by hwaddr=005056955CE5
2019-07-11 11:06:16.310 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: hwaddr=005056955CE5
2019-07-11 11:06:16.310 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=005056955CE5,
found 0 host(s)
2019-07-11 11:06:16.311 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 1
and identifier hwaddr=005056955CE5
2019-07-11 11:06:16.312 DEBUG [kea-dhcp4.dhcp4/33] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: client packet has been assigned to the following class(es):
UNKNOWN
2019-07-11 11:06:16.312 DEBUG [kea-dhcp4.dhcp4/33] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: client packet has been assigned to the following class(es):
ALL, UNKNOWN
2019-07-11 11:06:16.312 DEBUG [kea-dhcp4.ddns/33]
DHCP4_CLIENT_HOSTNAME_PROCESS [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: processing client's Hostname option
2019-07-11 11:06:16.313 DEBUG [kea-dhcp4.ddns/33] DHCP4_GENERATE_FQDN
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: client did not send a FQDN or hostname; FQDN will be be
generated for the client
2019-07-11 11:06:16.313 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_GET_CLIENTID obtaining IPv4 leases for client ID
ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29
2019-07-11 11:06:16.314 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_GET_HWADDR obtaining IPv4 leases for hardware address hwtype=1
00:50:56:95:5c:e5
2019-07-11 11:06:16.315 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.166
2019-07-11 11:06:16.316 DEBUG [kea-dhcp4.alloc-engine/33]
ALLOC_ENGINE_V4_REQUEST_ALLOC_REQUESTED [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: trying to allocate requested address 10.172.0.166
2019-07-11 11:06:16.316 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.166
2019-07-11 11:06:16.317 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_MYSQL_ADD_ADDR4
adding IPv4 lease with address 10.172.0.166
2019-07-11 11:06:16.320 INFO  [kea-dhcp4.leases/33] DHCP4_LEASE_ALLOC
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: lease 10.172.0.166 has been allocated
2019-07-11 11:06:16.321 DEBUG [kea-dhcp4.ddns/33]
DHCP4_RESPONSE_HOSTNAME_GENERATE [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: server has generated hostname
ip-10-172-0-166.eu-ldn-west.compute.internal for the client
2019-07-11 11:06:16.321 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_UPDATE_ADDR4 updating IPv4 lease for address 10.172.0.166
2019-07-11 11:06:16.324 DEBUG [kea-dhcp4.ddns/33] DHCP4_NCR_CREATE [hwtype=1
00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: DDNS updates enabled, therefore sending name change requests
2019-07-11 11:06:16.324 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_QUEUE_NCR
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29]: name change
request to add DNS entry queued: Type: 0 (CHG_ADD)
Forward Change: yes
Reverse Change: yes
FQDN: [ip-10-172-0-166.eu-ldn-west.compute.internal.]
IP Address: [10.172.0.166]
DHCID:
[0001018F0CD741AADEFE6F93552FB712475482E6A9BFA02258757BD52E59D7661C0706]
Lease Expires On: 20190711111116
Lease Length: 300

2019-07-11 11:06:16.326 DEBUG [kea-dhcp4.options/33] DHCP4_PACKET_PACK
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: preparing on-wire format of the packet to be sent
2019-07-11 11:06:16.326 DEBUG [kea-dhcp4.packets/33] DHCP4_PACKET_SEND
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: trying to send packet DHCPACK (type 5) from 10.172.0.25:67
to 10.172.0.166:68 on interface ens192
2019-07-11 11:06:16.327 DEBUG [kea-dhcp4.packets/33] DHCP4_RESPONSE_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29],
tid=0xefbdc39a: responding with packet DHCPACK (type 5), packet details:
local_address=10.172.0.25:67, remote_address=10.172.0.166:68,
msg_type=DHCPACK (5), transid=0xefbdc39a,
options:
  type=001, len=004: 4294967040 (uint32)
  type=003, len=004: 10.172.0.1
  type=006, len=004: 10.172.0.42
  type=012, len=044: "ip-10-172-0-166.eu-ldn-west.compute.internal" (string)
  type=051, len=004: 300 (uint32)
  type=053, len=001: 5 (uint8)
  type=054, len=004: 10.172.0.25
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29
2019-07-11 11:06:16.327 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_DHCP_DDNS_NCR_SENT NameChangeRequest sent to kea-dhcp-ddns: Type: 0
(CHG_ADD)
Forward Change: yes
Reverse Change: yes
FQDN: [ip-10-172-0-166.eu-ldn-west.compute.internal.]
IP Address: [10.172.0.166]
DHCID:
[0001018F0CD741AADEFE6F93552FB712475482E6A9BFA02258757BD52E59D7661C0706]
Lease Expires On: 20190711111116
Lease Length: 300

2019-07-11 11:06:23.336 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer:
flush-reclaimed-leases
2019-07-11 11:06:23.336 DEBUG [kea-dhcp4.alloc-engine/33]
ALLOC_ENGINE_V4_RECLAIMED_LEASES_DELETE begin deletion of reclaimed leases
expired more than 360 seconds ago
2019-07-11 11:06:23.336 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_DELETE_EXPIRED_RECLAIMED4 deleting reclaimed IPv4 leases that
expired more than 360 seconds ago
2019-07-11 11:06:23.338 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_DELETED_EXPIRED_RECLAIMED deleted 0 reclaimed leases from the
database
2019-07-11 11:06:23.338 DEBUG [kea-dhcp4.alloc-engine/33]
ALLOC_ENGINE_V4_RECLAIMED_LEASES_DELETE_COMPLETE successfully deleted 0
expired-reclaimed leases
2019-07-11 11:06:23.338 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_TIMERMGR_START_TIMER starting timer: flush-reclaimed-leases
2019-07-11 11:06:23.804 DEBUG [kea-dhcp4.packets/33] DHCP4_BUFFER_RECEIVED
received buffer from 0.0.0.0:68 to 255.255.255.255:67 over interface ens192
2019-07-11 11:06:23.804 DEBUG [kea-dhcp4.options/33] DHCP4_BUFFER_UNPACK
parsing buffer received from 0.0.0.0 to 255.255.255.255 over interface
ens192
2019-07-11 11:06:23.804 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-07-11 11:06:23.804 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: the subnet with ID 1 was selected for client assignments
2019-07-11 11:06:23.805 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: the selected subnet details: 10.172.0.0/24
2019-07-11 11:06:23.805 DEBUG [kea-dhcp4.packets/33] DHCP4_PACKET_RECEIVED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: DHCPDISCOVER (type 1) received from 0.0.0.0 to
255.255.255.255 on interface ens192
2019-07-11 11:06:23.805 DEBUG [kea-dhcp4.packets/33] DHCP4_QUERY_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d, packet details: local_address=255.255.255.255:67,
remote_address=0.0.0.0:68, msg_type=DHCPDISCOVER (1), transid=0x8181914d,
options:
  type=053, len=001: 1 (uint8)
  type=055, len=008: 1(uint8) 3(uint8) 12(uint8) 15(uint8) 6(uint8)
33(uint8) 121(uint8) 42(uint8)
  type=057, len=002: 576 (uint16)
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c
2019-07-11 11:06:23.806 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-07-11 11:06:23.806 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: the subnet with ID 1 was selected for client assignments
2019-07-11 11:06:23.806 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: the selected subnet details: 10.172.0.0/24
2019-07-11 11:06:23.806 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 0, identified by hwaddr=005056955CE5
2019-07-11 11:06:23.806 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: hwaddr=005056955CE5
2019-07-11 11:06:23.806 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=005056955CE5,
found 0 host(s)
2019-07-11 11:06:23.806 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 0
and identifier hwaddr=005056955CE5
2019-07-11 11:06:23.807 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 1, identified by hwaddr=005056955CE5
2019-07-11 11:06:23.807 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: hwaddr=005056955CE5
2019-07-11 11:06:23.807 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=005056955CE5,
found 0 host(s)
2019-07-11 11:06:23.807 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 1
and identifier hwaddr=005056955CE5
2019-07-11 11:06:23.808 DEBUG [kea-dhcp4.dhcp4/33] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: client packet has been assigned to the following class(es):
UNKNOWN
2019-07-11 11:06:23.808 DEBUG [kea-dhcp4.dhcp4/33] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: client packet has been assigned to the following class(es):
ALL, UNKNOWN
2019-07-11 11:06:23.808 DEBUG [kea-dhcp4.ddns/33]
DHCP4_CLIENT_HOSTNAME_PROCESS [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: processing client's Hostname option
2019-07-11 11:06:23.809 DEBUG [kea-dhcp4.ddns/33] DHCP4_GENERATE_FQDN
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: client did not send a FQDN or hostname; FQDN will be be
generated for the client
2019-07-11 11:06:23.809 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_GET_CLIENTID obtaining IPv4 leases for client ID
ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c
2019-07-11 11:06:23.811 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_GET_HWADDR obtaining IPv4 leases for hardware address hwtype=1
00:50:56:95:5c:e5
2019-07-11 11:06:23.812 DEBUG [kea-dhcp4.alloc-engine/33]
ALLOC_ENGINE_V4_OFFER_NEW_LEASE allocation engine will try to offer new
lease to the client [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d
2019-07-11 11:06:23.813 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.167
2019-07-11 11:06:23.813 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.167
2019-07-11 11:06:23.814 INFO  [kea-dhcp4.leases/33] DHCP4_LEASE_ADVERT
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: lease 10.172.0.167 will be advertised
2019-07-11 11:06:23.815 DEBUG [kea-dhcp4.ddns/33]
DHCP4_RESPONSE_HOSTNAME_GENERATE [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: server has generated hostname
ip-10-172-0-167.eu-ldn-west.compute.internal for the client
2019-07-11 11:06:23.815 DEBUG [kea-dhcp4.options/33] DHCP4_PACKET_PACK
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: preparing on-wire format of the packet to be sent
2019-07-11 11:06:23.815 DEBUG [kea-dhcp4.packets/33] DHCP4_PACKET_SEND
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: trying to send packet DHCPOFFER (type 2) from 10.172.0.25:67
to 10.172.0.167:68 on interface ens192
2019-07-11 11:06:23.816 DEBUG [kea-dhcp4.packets/33] DHCP4_RESPONSE_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: responding with packet DHCPOFFER (type 2), packet details:
local_address=10.172.0.25:67, remote_address=10.172.0.167:68,
msg_type=DHCPOFFER (2), transid=0x8181914d,
options:
  type=001, len=004: 4294967040 (uint32)
  type=003, len=004: 10.172.0.1
  type=006, len=004: 10.172.0.42
  type=012, len=044: "ip-10-172-0-167.eu-ldn-west.compute.internal" (string)
  type=051, len=004: 300 (uint32)
  type=053, len=001: 2 (uint8)
  type=054, len=004: 10.172.0.25
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c
2019-07-11 11:06:23.816 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer:
reclaim-expired-leases
2019-07-11 11:06:23.817 DEBUG [kea-dhcp4.alloc-engine/33]
ALLOC_ENGINE_V4_LEASES_RECLAMATION_START starting reclamation of expired
leases (limit = 100 leases or 250 milliseconds)
2019-07-11 11:06:23.817 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_GET_EXPIRED4 obtaining maximum 101 of expired IPv4 leases
2019-07-11 11:06:23.818 DEBUG [kea-dhcp4.alloc-engine/33]
ALLOC_ENGINE_V4_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 1.094 ms
2019-07-11 11:06:23.818 DEBUG [kea-dhcp4.alloc-engine/33]
ALLOC_ENGINE_V4_NO_MORE_EXPIRED_LEASES all expired leases have been
reclaimed
2019-07-11 11:06:23.819 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_TIMERMGR_START_TIMER starting timer: reclaim-expired-leases
2019-07-11 11:06:23.819 DEBUG [kea-dhcp4.packets/33] DHCP4_BUFFER_RECEIVED
received buffer from 0.0.0.0:68 to 255.255.255.255:67 over interface ens192
2019-07-11 11:06:23.819 DEBUG [kea-dhcp4.options/33] DHCP4_BUFFER_UNPACK
parsing buffer received from 0.0.0.0 to 255.255.255.255 over interface
ens192
2019-07-11 11:06:23.820 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-07-11 11:06:23.820 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: the subnet with ID 1 was selected for client assignments
2019-07-11 11:06:23.821 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: the selected subnet details: 10.172.0.0/24
2019-07-11 11:06:23.821 DEBUG [kea-dhcp4.packets/33] DHCP4_PACKET_RECEIVED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: DHCPREQUEST (type 3) received from 0.0.0.0 to
255.255.255.255 on interface ens192
2019-07-11 11:06:23.821 DEBUG [kea-dhcp4.packets/33] DHCP4_QUERY_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d, packet details: local_address=255.255.255.255:67,
remote_address=0.0.0.0:68, msg_type=DHCPREQUEST (3), transid=0x8181914d,
options:
  type=050, len=004: 10.172.0.167 (ipv4-address)
  type=053, len=001: 3 (uint8)
  type=054, len=004: 10.172.0.25 (ipv4-address)
  type=055, len=008: 1(uint8) 3(uint8) 12(uint8) 15(uint8) 6(uint8)
33(uint8) 121(uint8) 42(uint8)
  type=057, len=002: 576 (uint16)
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c
2019-07-11 11:06:23.822 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 10.172.0.0/24 for packet
received by matching address 10.172.0.25
2019-07-11 11:06:23.822 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_SELECTED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: the subnet with ID 1 was selected for client assignments
2019-07-11 11:06:23.822 DEBUG [kea-dhcp4.packets/33] DHCP4_SUBNET_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: the selected subnet details: 10.172.0.0/24
2019-07-11 11:06:23.823 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 0, identified by hwaddr=005056955CE5
2019-07-11 11:06:23.823 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: hwaddr=005056955CE5
2019-07-11 11:06:23.823 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=005056955CE5,
found 0 host(s)
2019-07-11 11:06:23.824 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 0
and identifier hwaddr=005056955CE5
2019-07-11 11:06:23.824 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation
for subnet id 1, identified by hwaddr=005056955CE5
2019-07-11 11:06:23.824 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
identifier: hwaddr=005056955CE5
2019-07-11 11:06:23.825 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=005056955CE5,
found 0 host(s)
2019-07-11 11:06:23.825 DEBUG [kea-dhcp4.hosts/33]
HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 1
and identifier hwaddr=005056955CE5
2019-07-11 11:06:23.825 DEBUG [kea-dhcp4.dhcp4/33] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: client packet has been assigned to the following class(es):
UNKNOWN
2019-07-11 11:06:23.826 DEBUG [kea-dhcp4.dhcp4/33] DHCP4_CLASS_ASSIGNED
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: client packet has been assigned to the following class(es):
ALL, UNKNOWN
2019-07-11 11:06:23.826 DEBUG [kea-dhcp4.ddns/33]
DHCP4_CLIENT_HOSTNAME_PROCESS [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: processing client's Hostname option
2019-07-11 11:06:23.826 DEBUG [kea-dhcp4.ddns/33] DHCP4_GENERATE_FQDN
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: client did not send a FQDN or hostname; FQDN will be be
generated for the client
2019-07-11 11:06:23.827 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_GET_CLIENTID obtaining IPv4 leases for client ID
ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c
2019-07-11 11:06:23.828 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_GET_HWADDR obtaining IPv4 leases for hardware address hwtype=1
00:50:56:95:5c:e5
2019-07-11 11:06:23.829 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.167
2019-07-11 11:06:23.830 DEBUG [kea-dhcp4.alloc-engine/33]
ALLOC_ENGINE_V4_REQUEST_ALLOC_REQUESTED [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: trying to allocate requested address 10.172.0.167
2019-07-11 11:06:23.830 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_MYSQL_GET_ADDR4
obtaining IPv4 lease for address 10.172.0.167
2019-07-11 11:06:23.831 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_MYSQL_ADD_ADDR4
adding IPv4 lease with address 10.172.0.167
2019-07-11 11:06:23.834 INFO  [kea-dhcp4.leases/33] DHCP4_LEASE_ALLOC
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: lease 10.172.0.167 has been allocated
2019-07-11 11:06:23.834 DEBUG [kea-dhcp4.ddns/33]
DHCP4_RESPONSE_HOSTNAME_GENERATE [hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: server has generated hostname
ip-10-172-0-167.eu-ldn-west.compute.internal for the client
2019-07-11 11:06:23.835 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_MYSQL_UPDATE_ADDR4 updating IPv4 lease for address 10.172.0.167
2019-07-11 11:06:23.838 DEBUG [kea-dhcp4.ddns/33] DHCP4_NCR_CREATE [hwtype=1
00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: DDNS updates enabled, therefore sending name change requests
2019-07-11 11:06:23.839 DEBUG [kea-dhcp4.dhcpsrv/33] DHCPSRV_QUEUE_NCR
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c]: name change
request to add DNS entry queued: Type: 0 (CHG_ADD)
Forward Change: yes
Reverse Change: yes
FQDN: [ip-10-172-0-167.eu-ldn-west.compute.internal.]
IP Address: [10.172.0.167]
DHCID:
[000101303B4D06807A49E0704759F754B48892035A495551CDE3F8B3C1B45201904D53]
Lease Expires On: 20190711111123
Lease Length: 300

2019-07-11 11:06:23.840 DEBUG [kea-dhcp4.options/33] DHCP4_PACKET_PACK
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: preparing on-wire format of the packet to be sent
2019-07-11 11:06:23.841 DEBUG [kea-dhcp4.packets/33] DHCP4_PACKET_SEND
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: trying to send packet DHCPACK (type 5) from 10.172.0.25:67
to 10.172.0.167:68 on interface ens192
2019-07-11 11:06:23.841 DEBUG [kea-dhcp4.packets/33] DHCP4_RESPONSE_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],
tid=0x8181914d: responding with packet DHCPACK (type 5), packet details:
local_address=10.172.0.25:67, remote_address=10.172.0.167:68,
msg_type=DHCPACK (5), transid=0x8181914d,
options:
  type=001, len=004: 4294967040 (uint32)
  type=003, len=004: 10.172.0.1
  type=006, len=004: 10.172.0.42
  type=012, len=044: "ip-10-172-0-167.eu-ldn-west.compute.internal" (string)
  type=051, len=004: 300 (uint32)
  type=053, len=001: 5 (uint8)
  type=054, len=004: 10.172.0.25
  type=061, len=019:
ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c
2019-07-11 11:06:23.841 DEBUG [kea-dhcp4.dhcpsrv/33]
DHCPSRV_DHCP_DDNS_NCR_SENT NameChangeRequest sent to kea-dhcp-ddns: Type: 0
(CHG_ADD)
Forward Change: yes
Reverse Change: yes
FQDN: [ip-10-172-0-167.eu-ldn-west.compute.internal.]
IP Address: [10.172.0.167]
DHCID:
[000101303B4D06807A49E0704759F754B48892035A495551CDE3F8B3C1B45201904D53]
Lease Expires On: 20190711111123
Lease Length: 300





--
Sent from: http://kea-users.7364.n8.nabble.com/
_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users

_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] kea hands out 2 ip addresses

eacool
Thats interesting, so PXE is not part of the tool chain unfortunately so I do
not think a PXE environment directly causes this.

Thanks, Ehsan



--
Sent from: http://kea-users.7364.n8.nabble.com/
_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] kea hands out 2 ip addresses

TroYy
In reply to this post by eacool
So reading your last logs closely, here what I've found:

first discover from client
2019-07-11 11:06:16.294 DEBUG [kea-dhcp4.packets/33] DHCP4_QUERY_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:f3:96:b3:e8:1c:16:57:29]

second discover
2019-07-11 11:06:23.805 DEBUG [kea-dhcp4.packets/33] DHCP4_QUERY_DATA
[hwtype=1 00:50:56:95:5c:e5],
cid=[ff:2d:1a:a1:33:00:02:00:00:ab:11:6b:fe:90:d5:2d:fa:ec:1c],

according to manual, chapter 8.2.20

However, if the lease contains a "client identifier" which is different from
the "client identifier" used by the client, the lease will be assumed to
belong to another client and the new lease will be allocated.

Default value of option "match-client-id" is "true" so when creating lease
for the first DORA it still ctores client-id in lease record.
So even if client has the same hwaddr in both requests, but cid is different
and server decides that clients are different aswell.
Placing in your global config Dhcp4 settings
"match-client-id": false,
will force the server to store leases without cid and only with hwaddr
instead.

After first ACK it will store lease and will match it second time because of
hwaddr is the same and will offer second time the same IP as the first time.

Good luck, hope it helps.



--
Sent from: http://kea-users.7364.n8.nabble.com/
_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users