Surf SOHO running firmware 8.1 (but I have seen similar things before)
A Windows 10 laptop connects to the Surf SOHO at 11:46am as shown in the AP event log
Oct 26 11:46:12 Client 34:F3:9A:xx:xx:xx associated with SSID34
The router and the laptop are in the same room and the router shows a signal strength of -45 (very good).
DHCP server logging is enabled and, as expected, the Device Event Log (see below) shows the laptop was assigned an IP address 3 seconds later.The lease expires in a day. The laptop MAC address has a permanent DHCP reservation.
Oct 26 11:46:15 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Then, 12 minutes later, the DHCP server re-assigns the IP address 8 times in 50 seconds
Oct 26 11:59:31 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 11:59:27 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 11:59:26 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 11:59:22 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 11:59:06 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 11:58:55 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 11:58:42 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 11:58:41 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
The AP Event Log does not show that the laptop dis-associated with the AP.
A couple hours later the DHCP server goes hog wild, and re-assigns the IP address 35 times over 2 minutes.
Oct 26 14:32:05 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:32:02 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:32:00 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:31:49 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:31:46 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:31:36 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:31:34 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:31:29 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:31:27 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:31:24 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:31:23 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:31:22 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:31:21 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:31:20 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:31:15 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:31:14 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:31:08 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:31:02 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:31:00 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:30:57 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:30:55 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:30:51 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:30:47 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:30:35 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:30:30 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:30:29 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:30:27 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:30:22 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:30:21 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:30:10 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:30:09 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:30:08 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:30:00 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:29:56 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
Oct 26 14:29:49 DHCP Server: 192.168.1.1 assigned 192.168.1.222 to 34:f3:9a:xx:xx:xx, lease time 86400
The WiFi client details (AP tab → wireless client) for the Windows 10 laptop, shows 3 entries for today with a FROM time but no TO time. See below.
Anyone have a guess as to why this happens?