The other thing that stands out in these logs are the timestamps.
I did not reorder these logs… I cut and pasted here exactly as ordered in system log.
There is an odd interleaving of timestamps.
Jan 10 17:26:57 turris hostapd: wlan1: STA <MAC2> RADIUS: starting accounting session 7BA1B9C4C5D694B6
Jan 10 17:26:57 turris hostapd: wlan1: STA <MAC2> WPA: pairwise key handshake completed (RSN)
Jan 10 11:26:57 turris dnsmasq-dhcp[5713]: DHCPREQUEST(br-lan) 192.168.6.137 <MAC2>
Jan 10 11:26:57 turris dnsmasq-dhcp[5713]: DHCPACK(br-lan) 192.168.6.137 <MAC2> PM-11709
Jan 10 17:26:57 turris dhcp_host_domain_ng.py: DHCP update hostname [PM-11709,192.168.6.137]
Jan 10 17:26:57 turris dhcp_host_domain_ng.py: Refresh kresd leases
Is it possible that DHCP issues could result from a daemon somehow is configured for wrong time?
In the above logs, hostapd. and dnsmasq-dhcp. definetly seem to think “now” is a very different point in time.