Re: [Kea-users] dhcp4 server stops responding to a device
I was using isc-dhcp and had this behaviour too:
https://gitlab.isc.org/isc-projects/dhcp/-/issues/177
I switched to kea-dhcp4 and it fixed it.
I've since done a distro upgrade and it's gone flaky again.
I've no idea how to diagnose signal quality from the data I can get from the
wiser (there's a rest endpoint) but this isn't available when it gets
unaddressed.
-Original Message-
From: Kea-users On Behalf Of Andrew Rowson
via Kea-users
Sent: 16 January 2024 18:25
To: kea-users@lists.isc.org
Cc: Andrew Rowson
Subject: Re: [Kea-users] dhcp4 server stops responding to a device
For what it's worth, I also have a wiser thermostat and hand out a static IP
with kea. No issues here.
No bootp as far as I know, and any historical unreliability has been
signal-related.
Happy to replicate any tests (dhcpdump etc.) on my sort-of-working environment.
Andrew
On Tue, 16 Jan 2024, at 5:38 PM, Gavin Davenport wrote:
> I wonder, if this was the case, would it work at all ?
>
> This started misbehaving (having worked reliably) on 01/01/2024 – and
> has been steadily getting more unreliable.
>
>
> *From:* Kea-users *On Behalf Of *Dan
> Oachs
> *Sent:* 16 January 2024 14:59
> *To:* Kea user's list
> *Subject:* Re: [Kea-users] dhcp4 server stops responding to a device
>
> Is that device using BOOTP instead of DHCP by any chance? If so, you
> might need the Bootp kea hook library. But that's just a guess.
>
> --Dan
>
>
> On Tue, Jan 16, 2024 at 6:08 AM Gavin Davenport wrote:
>> I have a “Wiser smart hub”
>> https://wiser.draytoncontrols.co.uk/smart-heating-kits
>>
>> This is basically a central heating timer with a wifi adapter.
>>
>> I can’t set a static IP on it so it is dependent on working DHCP (and wifi)
>> to stay connected to the network.
>>
>> I’m seeing the kea-dhcp server not respond to its dhcprequests and
>> restarting the wifi and restarting the dhcp server do not seem to help.
>>
>> Config file has a reservation for it’s address: (fc:fe:c2:05:3e:b7)
>>
>> {
>> "Dhcp4": {
>> "interfaces-config": {
>> "interfaces": [
>> "enp2s0"
>> ]
>> },
>>
>> "control-socket": {
>> "socket-type": "unix",
>> "socket-name": "/tmp/kea4-ctrl-socket"
>> },
>>
>> "lease-database": {
>> "type": "memfile",
>> "lfc-interval": 3600
>> },
>>
>>
>> "expired-leases-processing": {
>> "reclaim-timer-wait-time": 10,
>> "flush-reclaimed-timer-wait-time": 25,
>> "hold-reclaimed-time": 3600,
>> "max-reclaim-leases": 100,
>> "max-reclaim-time": 250,
>> "unwarned-reclaim-cycles": 5
>> },
>>
>> "renew-timer": 900,
>> "rebind-timer": 1800,
>> "valid-lifetime": 43200,
>>
>> "option-data": [
>> {
>> "name": "domain-name-servers",
>> "data": "10.99.99.119, 10.99.99.111"
>> },
>> {
>> "name": "domain-name",
>> "data": "ad.domain.net"
>> },
>> {
>> "name": "domain-search",
>> "data": "ad.domain.net, domain.net"
>> },
>> {
>> "name": "default-ip-ttl",
>> "data": "0xf0"
>> }
>> ],
>>
>>
>> "subnet4": [
>> {
>> "subnet": "10.99.99.0/24",
>> "pools": [ { "pool": "10.99.99.2 - 10.99.99.63" } ],
>> "reservations": [
>> {
>> "hw-address": "fc:fe:c2:05:3e:b7",
>> "ip-address": "10.99.99.3"
>> }
>> ],
>> "option-data": [
>> {
>> "name": "routers",
>> "data": "10.99.99.1"
>> }
>> ]
>> }
>> ],
>>
>>
>> "loggers": [
>> {
>> "name": "kea-dhcp4",
>> "output_options": [
>> {
>> "output": "/var/log/kea-dhcp4.log"
>> }
>> ],
>> "severity": "DEBUG",
>> "debuglevel": 7
>> }
>> ]
>> }
>> }
>>
>> So I reserve 10.99.99.3 for the wiser device.
>>
>> For quite long periods of time I get this logged
>> 2024-01-16 11:51:22.170 INFO
>> [kea-dhcp4.leases/1112259.140235902645952] DHCP4_LEASE_ADVERT
>> [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0x25eeba9a: lease
>> 10.99.99.3 will be advertised
>> 2024-01-16 11:51:37.918 INFO
>> [kea-dhcp4.leases/1112259.140235894253248] DHCP4_LEASE_ADVERT
>> [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0x25eeba9a: lease
>> 10.99.99.3 will be advertised
>> 2024-01-16 11:51:53.681 INFO
>> [kea-dhcp4.leases/1112259.140235885860544] DHCP4_LEASE_ADVERT
>> [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0x25eeba9a: lease
>> 10.99.99.3 will be advertised
>> 2024-01-16 11:52:04.033 INFO
>> [kea-dhcp4.leases/1112259.140235911038656] DHCP4_LEASE_ADVERT
>> [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xcf035c28: lease
>>
Re: [Kea-users] dhcp4 server stops responding to a device
For what it's worth, I also have a wiser thermostat and hand out a static IP
with kea. No issues here.
No bootp as far as I know, and any historical unreliability has been
signal-related.
Happy to replicate any tests (dhcpdump etc.) on my sort-of-working environment.
Andrew
On Tue, 16 Jan 2024, at 5:38 PM, Gavin Davenport wrote:
> I wonder, if this was the case, would it work at all ?
>
> This started misbehaving (having worked reliably) on 01/01/2024 – and
> has been steadily getting more unreliable.
>
>
> *From:* Kea-users *On Behalf Of *Dan Oachs
> *Sent:* 16 January 2024 14:59
> *To:* Kea user's list
> *Subject:* Re: [Kea-users] dhcp4 server stops responding to a device
>
> Is that device using BOOTP instead of DHCP by any chance? If so, you
> might need the Bootp kea hook library. But that's just a guess.
>
> --Dan
>
>
> On Tue, Jan 16, 2024 at 6:08 AM Gavin Davenport wrote:
>> I have a “Wiser smart hub”
>> https://wiser.draytoncontrols.co.uk/smart-heating-kits
>>
>> This is basically a central heating timer with a wifi adapter.
>>
>> I can’t set a static IP on it so it is dependent on working DHCP (and wifi)
>> to stay connected to the network.
>>
>> I’m seeing the kea-dhcp server not respond to its dhcprequests and
>> restarting the wifi and restarting the dhcp server do not seem to help.
>>
>> Config file has a reservation for it’s address: (fc:fe:c2:05:3e:b7)
>>
>> {
>> "Dhcp4": {
>> "interfaces-config": {
>> "interfaces": [
>> "enp2s0"
>> ]
>> },
>>
>> "control-socket": {
>> "socket-type": "unix",
>> "socket-name": "/tmp/kea4-ctrl-socket"
>> },
>>
>> "lease-database": {
>> "type": "memfile",
>> "lfc-interval": 3600
>> },
>>
>>
>> "expired-leases-processing": {
>> "reclaim-timer-wait-time": 10,
>> "flush-reclaimed-timer-wait-time": 25,
>> "hold-reclaimed-time": 3600,
>> "max-reclaim-leases": 100,
>> "max-reclaim-time": 250,
>> "unwarned-reclaim-cycles": 5
>> },
>>
>> "renew-timer": 900,
>> "rebind-timer": 1800,
>> "valid-lifetime": 43200,
>>
>> "option-data": [
>> {
>> "name": "domain-name-servers",
>> "data": "10.99.99.119, 10.99.99.111"
>> },
>> {
>> "name": "domain-name",
>> "data": "ad.domain.net"
>> },
>> {
>> "name": "domain-search",
>> "data": "ad.domain.net, domain.net"
>> },
>> {
>> "name": "default-ip-ttl",
>> "data": "0xf0"
>> }
>> ],
>>
>>
>> "subnet4": [
>> {
>> "subnet": "10.99.99.0/24",
>> "pools": [ { "pool": "10.99.99.2 - 10.99.99.63" } ],
>> "reservations": [
>> {
>> "hw-address": "fc:fe:c2:05:3e:b7",
>> "ip-address": "10.99.99.3"
>> }
>> ],
>> "option-data": [
>> {
>> "name": "routers",
>> "data": "10.99.99.1"
>> }
>> ]
>> }
>> ],
>>
>>
>> "loggers": [
>> {
>> "name": "kea-dhcp4",
>> "output_options": [
>> {
>> "output": "/var/log/kea-dhcp4.log"
>> }
>> ],
>> "severity": "DEBUG",
>> "debuglevel": 7
>> }
>> ]
>> }
>> }
>>
>> So I reserve 10.99.99.3 for the wiser device.
>>
>> For quite long periods of time I get this logged
>> 2024-01-16 11:51:22.170 INFO [kea-dhcp4.leases/1112259.140235902645952]
>> DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info],
>> tid=0x25eeba9a: lease 10.99.99.3 will be advertised
>> 2024-01-16 11:51:37.918 INFO [kea-dhcp4.leases/1112259.140235894253248]
>> DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info],
>> tid=0x25eeba9a: lease 10.99.99.3 will be advertised
>> 2024-01-16 11:51:53.681 INFO [kea-dhcp4.leases/1112259.140235885860544]
>> DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info],
>> tid=0x25eeba9a: lease 10.99.99.3 will be advertised
>> 2024-01-16 11:52:04.033 INFO [kea-dhcp4.leases/1112259.140235911038656]
>> DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info],
>> tid=0xcf035c28: lease 10.99.99.3 will be advertised
>>
>> And when I tcpdump I see this (tcpdump -v -n -A -i enp2s0 ether host
>> fc:fe:c2:05:3e:b7)
>>
>> 11:50:49.034748 IP (tos 0x0, ttl 64, id 17, offset 0, flags [none], proto
>> UDP (17), length 328)
>> 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from
>> fc:fe:c2:05:3e:b7, length 300, xid 0x25eeba9a, secs 224, Flags [Broadcast]
>> Client-Ethernet-Address fc:fe:c2:05:3e:b7
>> Vendor-rfc1048 Extensions
>> Magic Cookie 0x63825363
>> DHCP-Message (53), length 1: Discover
>> Hostname (12), length 15:
Re: [Kea-users] dhcp4 server stops responding to a device
I wonder, if this was the case, would it work at all ?
This started misbehaving (having worked reliably) on 01/01/2024 – and has been
steadily getting more unreliable.
From: Kea-users On Behalf Of Dan Oachs
Sent: 16 January 2024 14:59
To: Kea user's list
Subject: Re: [Kea-users] dhcp4 server stops responding to a device
Is that device using BOOTP instead of DHCP by any chance? If so, you might
need the Bootp kea hook library. But that's just a guess.
--Dan
On Tue, Jan 16, 2024 at 6:08 AM Gavin Davenport
mailto:gav...@gavdav.net>> wrote:
I have a “Wiser smart hub”
https://wiser.draytoncontrols.co.uk/smart-heating-kits
This is basically a central heating timer with a wifi adapter.
I can’t set a static IP on it so it is dependent on working DHCP (and wifi) to
stay connected to the network.
I’m seeing the kea-dhcp server not respond to its dhcprequests and restarting
the wifi and restarting the dhcp server do not seem to help.
Config file has a reservation for it’s address: (fc:fe:c2:05:3e:b7)
{
"Dhcp4": {
"interfaces-config": {
"interfaces": [
"enp2s0"
]
},
"control-socket": {
"socket-type": "unix",
"socket-name": "/tmp/kea4-ctrl-socket"
},
"lease-database": {
"type": "memfile",
"lfc-interval": 3600
},
"expired-leases-processing": {
"reclaim-timer-wait-time": 10,
"flush-reclaimed-timer-wait-time": 25,
"hold-reclaimed-time": 3600,
"max-reclaim-leases": 100,
"max-reclaim-time": 250,
"unwarned-reclaim-cycles": 5
},
"renew-timer": 900,
"rebind-timer": 1800,
"valid-lifetime": 43200,
"option-data": [
{
"name": "domain-name-servers",
"data": "10.99.99.119, 10.99.99.111"
},
{
"name": "domain-name",
"data": "ad.domain.net"
},
{
"name": "domain-search",
"data": "ad.domain.net,
domain.net"
},
{
"name": "default-ip-ttl",
"data": "0xf0"
}
],
"subnet4": [
{
"subnet": "10.99.99.0/24",
"pools": [ { "pool": "10.99.99.2 - 10.99.99.63" } ],
"reservations": [
{
"hw-address": "fc:fe:c2:05:3e:b7",
"ip-address": "10.99.99.3"
}
],
"option-data": [
{
"name": "routers",
"data": "10.99.99.1"
}
]
}
],
"loggers": [
{
"name": "kea-dhcp4",
"output_options": [
{
"output": "/var/log/kea-dhcp4.log"
}
],
"severity": "DEBUG",
"debuglevel": 7
}
]
}
}
So I reserve 10.99.99.3 for the wiser device.
For quite long periods of time I get this logged
2024-01-16 11:51:22.170 INFO [kea-dhcp4.leases/1112259.140235902645952]
DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0x25eeba9a:
lease 10.99.99.3 will be advertised
2024-01-16 11:51:37.918 INFO [kea-dhcp4.leases/1112259.140235894253248]
DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0x25eeba9a:
lease 10.99.99.3 will be advertised
2024-01-16 11:51:53.681 INFO [kea-dhcp4.leases/1112259.140235885860544]
DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0x25eeba9a:
lease 10.99.99.3 will be advertised
2024-01-16 11:52:04.033 INFO [kea-dhcp4.leases/1112259.140235911038656]
DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xcf035c28:
lease 10.99.99.3 will be advertised
And when I tcpdump I see this (tcpdump -v -n -A -i enp2s0 ether host
fc:fe:c2:05:3e:b7)
11:50:49.034748 IP (tos 0x0, ttl 64, id 17, offset 0, flags [none], proto UDP
(17), length 328)
0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from
fc:fe:c2:05:3e:b7, length 300, xid 0x25eeba9a, secs 224, Flags [Broadcast]
Client-Ethernet-Address fc:fe:c2:05:3e:b7
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message (53), length 1: Discover
Hostname (12), length 15: "WiserHeat053EB7"
E..H@.y..D.C.4}.%...>...c.Sc5WiserHeat053EB7
11:51:05.598448 IP
Re: [Kea-users] dhcp4 config file and ip reservation
fantastic and thanks for confirming. we have very static network and only new DT are added to our network when replaced or for a new user. this along with dhcp - using this https://gitlab.isc.org/isc-projects/kea/-/wikis/docs/editing-host-reservations - it should work. regards, michael On Tue, 16 Jan 2024 at 16:05, Dan Oachs wrote: > If I understand what you are doing correctly, yes, it will work. I am > running a kea server the same way. All the configuration is in the config > files and the host reservations are in the MySQL database. > > --Dan > > > On Tue, Jan 16, 2024 at 9:18 AM mtint hpc wrote: > >> Hi All, >> >> I am interested in utilizing mariadb as the backend for host >> reservations, without the need for a dhcp pool. The subnet and other >> relevant information will still be stored in the dhcp4 configuration file. >> I believe that using a database will not hinder kea from utilizing the >> defined subnet and other configurations specified in the config file, and >> it will only retrieve the dhcp reservations from the database. Can someone >> if this would work? >> >> Kind regards, >> >> Michael >> >> -- >> ISC funds the development of this software with paid support >> subscriptions. Contact us at https://www.isc.org/contact/ for more >> information. >> >> To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. >> >> Kea-users mailing list >> Kea-users@lists.isc.org >> https://lists.isc.org/mailman/listinfo/kea-users >> > -- > ISC funds the development of this software with paid support > subscriptions. Contact us at https://www.isc.org/contact/ for more > information. > > To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. > > Kea-users mailing list > Kea-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/kea-users > -- ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. Kea-users mailing list Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users
Re: [Kea-users] dhcp4 config file and ip reservation
If I understand what you are doing correctly, yes, it will work. I am running a kea server the same way. All the configuration is in the config files and the host reservations are in the MySQL database. --Dan On Tue, Jan 16, 2024 at 9:18 AM mtint hpc wrote: > Hi All, > > I am interested in utilizing mariadb as the backend for host reservations, > without the need for a dhcp pool. The subnet and other relevant information > will still be stored in the dhcp4 configuration file. I believe that using > a database will not hinder kea from utilizing the defined subnet and other > configurations specified in the config file, and it will only retrieve the > dhcp reservations from the database. Can someone if this would work? > > Kind regards, > > Michael > > -- > ISC funds the development of this software with paid support > subscriptions. Contact us at https://www.isc.org/contact/ for more > information. > > To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. > > Kea-users mailing list > Kea-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/kea-users > -- ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. Kea-users mailing list Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users
[Kea-users] dhcp4 config file and ip reservation
Hi All, I am interested in utilizing mariadb as the backend for host reservations, without the need for a dhcp pool. The subnet and other relevant information will still be stored in the dhcp4 configuration file. I believe that using a database will not hinder kea from utilizing the defined subnet and other configurations specified in the config file, and it will only retrieve the dhcp reservations from the database. Can someone if this would work? Kind regards, Michael -- ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. Kea-users mailing list Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users
Re: [Kea-users] dhcp4 server stops responding to a device
Is that device using BOOTP instead of DHCP by any chance? If so, you might
need the Bootp kea hook library. But that's just a guess.
--Dan
On Tue, Jan 16, 2024 at 6:08 AM Gavin Davenport wrote:
> I have a “Wiser smart hub”
> https://wiser.draytoncontrols.co.uk/smart-heating-kits
>
>
>
> This is basically a central heating timer with a wifi adapter.
>
>
>
> I can’t set a static IP on it so it is dependent on working DHCP (and
> wifi) to stay connected to the network.
>
>
>
> I’m seeing the kea-dhcp server not respond to its dhcprequests and
> restarting the wifi and restarting the dhcp server do not seem to help.
>
>
>
> Config file has a reservation for it’s address: (fc:fe:c2:05:3e:b7)
>
> {
>
> "Dhcp4": {
>
> "interfaces-config": {
>
> "interfaces": [
>
> "enp2s0"
>
> ]
>
> },
>
>
>
> "control-socket": {
>
> "socket-type": "unix",
>
> "socket-name": "/tmp/kea4-ctrl-socket"
>
> },
>
>
>
> "lease-database": {
>
> "type": "memfile",
>
> "lfc-interval": 3600
>
> },
>
>
>
>
>
> "expired-leases-processing": {
>
> "reclaim-timer-wait-time": 10,
>
> "flush-reclaimed-timer-wait-time": 25,
>
> "hold-reclaimed-time": 3600,
>
> "max-reclaim-leases": 100,
>
> "max-reclaim-time": 250,
>
> "unwarned-reclaim-cycles": 5
>
> },
>
>
>
> "renew-timer": 900,
>
> "rebind-timer": 1800,
>
> "valid-lifetime": 43200,
>
>
>
> "option-data": [
>
> {
>
> "name": "domain-name-servers",
>
> "data": "10.99.99.119, 10.99.99.111"
>
> },
>
> {
>
> "name": "domain-name",
>
> "data": "ad.domain.net"
>
> },
>
> {
>
> "name": "domain-search",
>
> "data": "ad.domain.net, domain.net"
>
> },
>
> {
>
> "name": "default-ip-ttl",
>
> "data": "0xf0"
>
> }
>
> ],
>
>
>
>
>
> "subnet4": [
>
> {
>
> "subnet": "10.99.99.0/24",
>
> "pools": [ { "pool": "10.99.99.2 - 10.99.99.63" } ],
>
> "reservations": [
>
> {
>
> "hw-address": "fc:fe:c2:05:3e:b7",
>
> "ip-address": "10.99.99.3"
>
> }
>
> ],
>
> "option-data": [
>
> {
>
> "name": "routers",
>
> "data": "10.99.99.1"
>
> }
>
> ]
>
> }
>
> ],
>
>
>
>
>
> "loggers": [
>
> {
>
> "name": "kea-dhcp4",
>
> "output_options": [
>
> {
>
> "output": "/var/log/kea-dhcp4.log"
>
> }
>
> ],
>
> "severity": "DEBUG",
>
> "debuglevel": 7
>
> }
>
> ]
>
> }
>
> }
>
>
>
> So I reserve 10.99.99.3 for the wiser device.
>
>
>
> For quite long periods of time I get this logged
> 2024-01-16 11:51:22.170 INFO [kea-dhcp4.leases/1112259.140235902645952]
> DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info],
> tid=0x25eeba9a: lease 10.99.99.3 will be advertised
>
> 2024-01-16 11:51:37.918 INFO [kea-dhcp4.leases/1112259.140235894253248]
> DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info],
> tid=0x25eeba9a: lease 10.99.99.3 will be advertised
>
> 2024-01-16 11:51:53.681 INFO [kea-dhcp4.leases/1112259.140235885860544]
> DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info],
> tid=0x25eeba9a: lease 10.99.99.3 will be advertised
>
> 2024-01-16 11:52:04.033 INFO [kea-dhcp4.leases/1112259.140235911038656]
> DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info],
> tid=0xcf035c28: lease 10.99.99.3 will be advertised
>
>
>
> And when I tcpdump I see this (tcpdump -v -n -A -i enp2s0 ether host
> fc:fe:c2:05:3e:b7)
>
>
>
> 11:50:49.034748 IP (tos 0x0, ttl 64, id 17, offset 0, flags [none], proto
> UDP (17), length 328)
>
> 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from
> fc:fe:c2:05:3e:b7, length 300, xid 0x25eeba9a, secs 224, Flags [Broadcast]
>
> Client-Ethernet-Address fc:fe:c2:05:3e:b7
>
> Vendor-rfc1048 Extensions
>
> Magic Cookie 0x63825363
>
> DHCP-Message (53), length 1: Discover
>
> Hostname (12), length 15: "WiserHeat053EB7"
>
> E..H@
> .y..D.C.4}.%...>...c.Sc5WiserHeat053EB7
>
> 11:51:05.598448 IP (tos 0x0, ttl 64, id 18, offset 0, flags [none], proto
> UDP (17), length 328)
>
> 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from
> fc:fe:c2:05:3e:b7, length 300, xid 0x25eeba9a, secs 240, Flags [Broadcast]
>
> Client-Ethernet-Address fc:fe:c2:05:3e:b7
>
>
[Kea-users] dhcp4 server stops responding to a device
I have a "Wiser smart hub"
https://wiser.draytoncontrols.co.uk/smart-heating-kits
This is basically a central heating timer with a wifi adapter.
I can't set a static IP on it so it is dependent on working DHCP (and wifi) to
stay connected to the network.
I'm seeing the kea-dhcp server not respond to its dhcprequests and restarting
the wifi and restarting the dhcp server do not seem to help.
Config file has a reservation for it's address: (fc:fe:c2:05:3e:b7)
{
"Dhcp4": {
"interfaces-config": {
"interfaces": [
"enp2s0"
]
},
"control-socket": {
"socket-type": "unix",
"socket-name": "/tmp/kea4-ctrl-socket"
},
"lease-database": {
"type": "memfile",
"lfc-interval": 3600
},
"expired-leases-processing": {
"reclaim-timer-wait-time": 10,
"flush-reclaimed-timer-wait-time": 25,
"hold-reclaimed-time": 3600,
"max-reclaim-leases": 100,
"max-reclaim-time": 250,
"unwarned-reclaim-cycles": 5
},
"renew-timer": 900,
"rebind-timer": 1800,
"valid-lifetime": 43200,
"option-data": [
{
"name": "domain-name-servers",
"data": "10.99.99.119, 10.99.99.111"
},
{
"name": "domain-name",
"data": "ad.domain.net"
},
{
"name": "domain-search",
"data": "ad.domain.net, domain.net"
},
{
"name": "default-ip-ttl",
"data": "0xf0"
}
],
"subnet4": [
{
"subnet": "10.99.99.0/24",
"pools": [ { "pool": "10.99.99.2 - 10.99.99.63" } ],
"reservations": [
{
"hw-address": "fc:fe:c2:05:3e:b7",
"ip-address": "10.99.99.3"
}
],
"option-data": [
{
"name": "routers",
"data": "10.99.99.1"
}
]
}
],
"loggers": [
{
"name": "kea-dhcp4",
"output_options": [
{
"output": "/var/log/kea-dhcp4.log"
}
],
"severity": "DEBUG",
"debuglevel": 7
}
]
}
}
So I reserve 10.99.99.3 for the wiser device.
For quite long periods of time I get this logged
2024-01-16 11:51:22.170 INFO [kea-dhcp4.leases/1112259.140235902645952]
DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0x25eeba9a:
lease 10.99.99.3 will be advertised
2024-01-16 11:51:37.918 INFO [kea-dhcp4.leases/1112259.140235894253248]
DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0x25eeba9a:
lease 10.99.99.3 will be advertised
2024-01-16 11:51:53.681 INFO [kea-dhcp4.leases/1112259.140235885860544]
DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0x25eeba9a:
lease 10.99.99.3 will be advertised
2024-01-16 11:52:04.033 INFO [kea-dhcp4.leases/1112259.140235911038656]
DHCP4_LEASE_ADVERT [hwtype=1 fc:fe:c2:05:3e:b7], cid=[no info], tid=0xcf035c28:
lease 10.99.99.3 will be advertised
And when I tcpdump I see this (tcpdump -v -n -A -i enp2s0 ether host
fc:fe:c2:05:3e:b7)
11:50:49.034748 IP (tos 0x0, ttl 64, id 17, offset 0, flags [none], proto UDP
(17), length 328)
0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from
fc:fe:c2:05:3e:b7, length 300, xid 0x25eeba9a, secs 224, Flags [Broadcast]
Client-Ethernet-Address fc:fe:c2:05:3e:b7
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message (53), length 1: Discover
Hostname (12), length 15: "WiserHeat053EB7"
E..H@.y..D.C.4}.%...>...c.Sc5WiserHeat053EB7
11:51:05.598448 IP (tos 0x0, ttl 64, id 18, offset 0, flags [none], proto UDP
(17), length 328)
0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from
fc:fe:c2:05:3e:b7, length 300, xid 0x25eeba9a, secs 240, Flags [Broadcast]
Client-Ethernet-Address fc:fe:c2:05:3e:b7
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message (53), length 1: Discover
Hostname (12), length 15: "WiserHeat053EB7"
E..H@.y..D.C.4}.%...>...c.Sc5WiserHeat053EB7
11:51:22.169853 IP (tos 0x0, ttl 64, id 19, offset 0, flags [none], proto UDP
(17), length 328)
0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from
