The DHCP problem on the new router is annoying, but at least I’m having fun while trying to figure it out.
- Returned the bedroom Logitech Squeezebox Radio to dynamic DHCP
- The two other Radios and Squeezebox Touch streamer remain static DHCP IP address assignments
- Rebooted the G3100 router
- Ran the Ethernet network connection option on the Radios and the Touch
- The Ethernet connection icons flashed red, indicating a momentary loss of IP address due to a connectivity break from the IOGEAR adapters
- Checked the router’s LAN DHCP log
- The network connection routines, as indicated by the icons, had initiated DHCP renewals
- All of the DHCP sequences succeeded
BEDROOM - DYNAMIC DHCP ---------------------- [LDHCP] DHCPACK on 192.168.1.246 to 00:04:20:26:7e:57 (SqueezeboxRadio) via br-lan 2025 Feb 14 11:26:33 [LDHCP] DHCPREQUEST for 192.168.1.246 (192.168.1.1) from 00:04:20:26:7e:57 (SqueezeboxRadio) via br-lan 2025 Feb 14 11:26:33 [LDHCP] DHCPOFFER on 192.168.1.246 to 00:04:20:26:7e:57 (SqueezeboxRadio) via br-lan 2025 Feb 14 11:26:32 [LDHCP] DHCPDISCOVER from 00:04:20:26:7e:57 (SqueezeboxRadio) via br-lan 2025 Feb 14 11:26:27 [LDHCP] DHCPRELEASE of 0.0.0.0 from 00:04:20:26:7e:57 via br-lan (not found) 2025 Feb 14 11:26:27 [LDHCP] DHCPRELEASE from 00:04:20:26:7e:57 specified requested-address. 2025 Feb 14 11:25:38 GUEST ROOM - STATIC DHCP ------------------------ [LDHCP] DHCPACK on 192.168.1.212 to 00:04:20:29:e6:b1 (SqueezeboxRadio) via br-lan 2025 Feb 14 11:25:38 [LDHCP] DHCPREQUEST for 192.168.1.212 (192.168.1.1) from 00:04:20:29:e6:b1 (SqueezeboxRadio) via br-lan 2025 Feb 14 11:25:37 [LDHCP] DHCPOFFER on 192.168.1.212 to 00:04:20:29:e6:b1 (SqueezeboxRadio) via br-lan 2025 Feb 14 11:25:37 [LDHCP] DHCPDISCOVER from 00:04:20:29:e6:b1 (SqueezeboxRadio) via br-lan 2025 Feb 14 11:25:32 [LDHCP] DHCPRELEASE of 0.0.0.0 from 00:04:20:29:e6:b1 via br-lan (not found) 2025 Feb 14 11:25:32 [LDHCP] DHCPRELEASE from 00:04:20:29:e6:b1 specified requested-address. KITCHEN - STATIC DHCP --------------------- [LDHCP] DHCPACK on 192.168.1.194 to 00:04:20:2c:84:5c (SqueezeboxRadio) via br-lan 2025 Feb 14 11:21:40 [LDHCP] DHCPREQUEST for 192.168.1.194 (192.168.1.1) from 00:04:20:2c:84:5c (SqueezeboxRadio) via br-lan 2025 Feb 14 11:21:39 [LDHCP] DHCPOFFER on 192.168.1.194 to 00:04:20:2c:84:5c (SqueezeboxRadio) via br-lan 2025 Feb 14 11:21:39 [LDHCP] DHCPDISCOVER from 00:04:20:2c:84:5c (SqueezeboxRadio) via br-lan 2025 Feb 14 11:21:35 [LDHCP] DHCPRELEASE of 0.0.0.0 from 00:04:20:2c:84:5c via br-lan (not found) 2025 Feb 14 11:21:35 [LDHCP] DHCPRELEASE from 00:04:20:2c:84:5c specified requested-address. 2025 Feb 14 11:21:07 TOUCH - STATIC DHCP ------------------- [LDHCP] DHCPACK on 192.168.1.222 to 00:04:20:22:fe:84 (SqueezeboxTouch) via br-lan 2025 Feb 14 11:16:43 [LDHCP] DHCPREQUEST for 192.168.1.222 (192.168.1.1) from 00:04:20:22:fe:84 (SqueezeboxTouch) via br-lan 2025 Feb 14 11:16:43 [LDHCP] DHCPOFFER on 192.168.1.222 to 00:04:20:22:fe:84 (SqueezeboxTouch) via br-lan 2025 Feb 14 11:16:43 [LDHCP] DHCPDISCOVER from 00:04:20:22:fe:84 (SqueezeboxTouch) via br-lan [LDHCP] DHCPRELEASE of 0.0.0.0 from 00:04:20:22:fe:84 via br-lan (not found) 2025 Feb 14 11:16:39 [LDHCP] DHCPRELEASE from 00:04:20:22:fe:84 specified requested-address.
What am I to make of this? Before I rebooted the router, DHCP lease renewal wasn’t working on these devices, whether or not the assigned private network IP addresses were static. Now I see the classic DORA stages — Discovery, Offer, Request and Acknowledgment.
Is the problem somehow now gone? All I can do is wait 24 hours to see if the Ethernet icons go red, and stay red, again. (DHCP lease timeout is 1440 minutes ÷ 60 = 24 hours)
Yep, from a router log. My theory is it fails after some number of renewals.
Where’s that detailed logging happening? Is that on the router? Or are you running a sniffer? Anyway, very handy!