Hello Kevin:
Kea is now up to version 1.3.0 with many new features added since 1.1.0
so you may wish to consider upgrading. However, Kea 1.1.0 should
function using MySQL for lease storage. Kea servers can emit a great
deal of logging detail, provided you have it enabled. With sufficient
logging enabled, you should see some sort of response from Kea to client
packets. Even if Kea elects to drop a packet, you should still it's
arrival logged and an explanation for why it was dropped.
I would suggest, as a starting point that you dial up the logging
detail. The following logger configuration will give you maximum output
to stdout (for more information on logging please see the Logging
chapter in the Kea Admin guide):
"Logging":
{
"loggers": [
{
"name": "kea-dhcp4",
"output_options": [
{
"output": "stdout"
}
],
"severity": "INFO",
"debuglevel":99
}
]
}
I have attached a log excerpt from a Kea 1.1.0 server I configured to
use MySQL lease storage so you can see what to expect.
Regards,
Thomas Markwalder
ISC Software Engineering
On 03/18/2018 06:02 PM, Kevin Olbrich wrote:
Hi,
I set the following as my lease-db:
"lease-database": {
"type": "mysql",
"name": "dc_dhcp",
"host": "192.168.30.2",
"user": "dc_dhcp",
"password": "xxxxxxxxxxxxxx"
# "type": "memfile",
# "persist": true,
# "name": "/tmp/kea-leases4.csv",
# "lfc-interval": 1800
},
If I use MySQL, no lease is ever created. The server also never
answers any DHCP request.
Changing from mysql to memfile (commented out code above), everything
works fine.
No error is logged, "it just dont work" with mysql.
root@dhcp01:~# kea-dhcp4 -v
1.1.0
Debian Stretch, main repo.
Is this a known issue?
Kind regards,
Kevin
_______________________________________________
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
2018-03-19 09:05:07.545 INFO [kea-dhcp4.dhcp4/14823] DHCP4_STARTING Kea DHCPv4 server version 1.1.0 starting
2018-03-19 09:05:07.547 INFO [kea-dhcp4.dhcpsrv/14823] DHCPSRV_CFGMGR_ADD_IFACE listening on interface eth4
2018-03-19 09:05:07.547 INFO [kea-dhcp4.dhcpsrv/14823] DHCPSRV_CFGMGR_SOCKET_TYPE_DEFAULT "dhcp-socket-type" not specified , using default socket type raw
2018-03-19 09:05:07.548 INFO [kea-dhcp4.dhcp4/14823] DHCP4_CONFIG_NEW_SUBNET a new subnet has been added to configuration: 178.16.1.0/24 with params: t1=10, t2=20, valid-lifetime=30
2018-03-19 09:05:07.548 INFO [kea-dhcp4.dhcp4/14823] DHCP4_CONFIG_COMPLETE DHCPv4 server has completed configuration: added IPv4 subnets: 1; DDNS: disabled
2018-03-19 09:05:07.548 INFO [kea-dhcp4.dhcpsrv/14823] DHCPSRV_MYSQL_DB opening MySQL lease database: host=175.16.1.30 name=test_1 password=***** type=mysql universe=4 user=keatest
2018-03-19 09:05:07.881 WARN [kea-dhcp4.dhcpsrv/14823] DHCPSRV_MULTIPLE_RAW_SOCKETS_PER_IFACE current configuration will result in opening multiple broadcast capable sockets on some interfaces and some DHCP messages may be duplicated
2018-03-19 09:05:07.894 INFO [kea-dhcp4.dhcp4/14823] DHCP4_STARTED Kea DHCPv4 server version 1.1.0 started
2018-03-19 09:05:07.894 DEBUG [kea-dhcp4.packets/14823] DHCP4_BUFFER_WAIT waiting for next DHCPv4 packet with timeout 1000 ms
2018-03-19 09:05:14.302 DEBUG [kea-dhcp4.packets/14823] DHCP4_BUFFER_RECEIVED received buffer from 178.16.1.25:68 to 255.255.255.255:67 over interface eth4
2018-03-19 09:05:14.302 DEBUG [kea-dhcp4.options/14823] DHCP4_BUFFER_UNPACK parsing buffer received from 178.16.1.25 to 255.255.255.255 over interface eth4
2018-03-19 09:05:14.303 DEBUG [kea-dhcp4.dhcpsrv/14823] DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 178.16.1.0/24 for packet received by matching address 178.16.1.30
2018-03-19 09:05:14.303 DEBUG [kea-dhcp4.packets/14823] DHCP4_SUBNET_SELECTED [hwtype=1 08:00:27:99:72:be], cid=[no info], tid=0x3b8618: the subnet with ID 1 was selected for client assignments
2018-03-19 09:05:14.303 DEBUG [kea-dhcp4.packets/14823] DHCP4_SUBNET_DATA [hwtype=1 08:00:27:99:72:be], cid=[no info], tid=0x3b8618: the selected subnet details: 178.16.1.0/24
2018-03-19 09:05:14.303 DEBUG [kea-dhcp4.packets/14823] DHCP4_PACKET_RECEIVED [hwtype=1 08:00:27:99:72:be], cid=[no info], tid=0x3b8618: DHCPDISCOVER (type 1) received from 178.16.1.25 to 255.255.255.255 on interface eth4
2018-03-19 09:05:14.303 DEBUG [kea-dhcp4.packets/14823] DHCP4_QUERY_DATA [hwtype=1 08:00:27:99:72:be], cid=[no info], tid=0x3b8618, packet details: local_address=255.255.255.255:67, remote_adress=178.16.1.25:68, msg_type=DHCPDISCOVER (1), transid=0x3b8618,
options:
type=053, len=001: 1 (uint8)
2018-03-19 09:05:14.303 DEBUG [kea-dhcp4.dhcpsrv/14823] DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet 178.16.1.0/24 for packet received by matching address 178.16.1.30
2018-03-19 09:05:14.303 DEBUG [kea-dhcp4.packets/14823] DHCP4_SUBNET_SELECTED [hwtype=1 08:00:27:99:72:be], cid=[no info], tid=0x3b8618: the subnet with ID 1 was selected for client assignments
2018-03-19 09:05:14.303 DEBUG [kea-dhcp4.packets/14823] DHCP4_SUBNET_DATA [hwtype=1 08:00:27:99:72:be], cid=[no info], tid=0x3b8618: the selected subnet details: 178.16.1.0/24
2018-03-19 09:05:14.303 DEBUG [kea-dhcp4.hosts/14823] HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation for subnet id 1, identified by hwaddr=0800279972BE
2018-03-19 09:05:14.303 DEBUG [kea-dhcp4.hosts/14823] HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using identifier: hwaddr=0800279972BE
2018-03-19 09:05:14.303 DEBUG [kea-dhcp4.hosts/14823] HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=0800279972BE, found 0 host(s)
2018-03-19 09:05:14.303 DEBUG [kea-dhcp4.hosts/14823] HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id 1 and identifier hwaddr=0800279972BE
2018-03-19 09:05:14.303 DEBUG [kea-dhcp4.ddns/14823] DHCP4_CLIENT_HOSTNAME_PROCESS [hwtype=1 08:00:27:99:72:be], cid=[no info], tid=0x3b8618: processing client's Hostname option
2018-03-19 09:05:14.304 DEBUG [kea-dhcp4.dhcpsrv/14823] DHCPSRV_MYSQL_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID 1 and hardware address hwtype=1 08:00:27:99:72:be
2018-03-19 09:05:14.304 DEBUG [kea-dhcp4.alloc-engine/14823] ALLOC_ENGINE_V4_OFFER_NEW_LEASE allocation engine will try to offer new lease to the client [hwtype=1 08:00:27:99:72:be], cid=[no info], tid=0x3b8618
2018-03-19 09:05:14.304 DEBUG [kea-dhcp4.hosts/14823] HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4 get one host with reservation for subnet id 1 and IPv4 address 178.16.1.100
2018-03-19 09:05:14.304 DEBUG [kea-dhcp4.hosts/14823] HOSTS_CFG_GET_ALL_ADDRESS4 get all hosts with reservations for IPv4 address 178.16.1.100
2018-03-19 09:05:14.304 DEBUG [kea-dhcp4.hosts/14823] HOSTS_CFG_GET_ALL_ADDRESS4_COUNT using address 178.16.1.100, found 0 host(s)
2018-03-19 09:05:14.304 DEBUG [kea-dhcp4.hosts/14823] HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4_NULL host not found using subnet id 1 and address 178.16.1.100
2018-03-19 09:05:14.304 DEBUG [kea-dhcp4.dhcpsrv/14823] DHCPSRV_MYSQL_GET_ADDR4 obtaining IPv4 lease for address 178.16.1.100
2018-03-19 09:05:14.305 DEBUG [kea-dhcp4.dhcpsrv/14823] DHCPSRV_MYSQL_GET_ADDR4 obtaining IPv4 lease for address 178.16.1.100
2018-03-19 09:05:14.305 INFO [kea-dhcp4.leases/14823] DHCP4_LEASE_ADVERT [hwtype=1 08:00:27:99:72:be], cid=[no info], tid=0x3b8618: lease 178.16.1.100 will be advertised
2018-03-19 09:05:14.305 DEBUG [kea-dhcp4.options/14823] DHCP4_PACKET_PACK [hwtype=1 08:00:27:99:72:be], cid=[no info], tid=0x3b8618: preparing on-wire format of the packet to be sent
2018-03-19 09:05:14.305 DEBUG [kea-dhcp4.packets/14823] DHCP4_PACKET_SEND [hwtype=1 08:00:27:99:72:be], cid=[no info], tid=0x3b8618: trying to send packet DHCPOFFER (type 2) from 178.16.1.30:67 to 178.16.1.100:68 on interface eth4
2018-03-19 09:05:14.305 DEBUG [kea-dhcp4.packets/14823] DHCP4_RESPONSE_DATA [hwtype=1 08:00:27:99:72:be], cid=[no info], tid=0x3b8618: responding with packet DHCPOFFER (type 2), packet details: local_address=178.16.1.30:67, remote_adress=178.16.1.100:68, msg_type=DHCPOFFER (2), transid=0x3b8618,
options:
type=001, len=004: 4294967040 (uint32)
type=051, len=004: 30 (uint32)
type=053, len=001: 2 (uint8)
type=054, len=004: 178.16.1.30
type=058, len=004: 10 (uint32)
type=059, len=004: 20 (uint32)
2018-03-19 09:05:14.305 DEBUG [kea-dhcp4.packets/14823] DHCP4_BUFFER_WAIT waiting for next DHCPv4 packet with timeout 1000 ms
_______________________________________________
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
