Category: Tech

The Logitech streaming radios are working okay. I’m flummoxed why there was a problem, because knowing the G3100 wouldn’t honor IP addresses it didn’t allocate, I had reset the IOGEAR Ethernet-to-WiFi adapters (with a paperclip) to clear their original IP addresses. Then for each of them I went through the WPS process with the new router.

They ran for days without a problem, but when it hit, all of the streamers exhibited a recurring loss of connection from their adapters. Which is why I’m on the lookout for the failures returning.

All is well, for now, with the DHCP-assigned IP addresses on the Logitech radios. Why? Dunno. All I did was restart the WiFi router and manually force the lease release/renew process. The problem didn’t appear right away after switching over to the G3100 from the G1100, so perhaps it happens after some number of lease renewals. I shall wait and see.

The DHCP problem on the new router is annoying, but at least I’m having fun while trying to figure it out.

1. Returned the bedroom Logitech Squeezebox Radio to dynamic DHCP
2. The two other Radios and Squeezebox Touch streamer remain static DHCP IP address assignments
3. Rebooted the G3100 router
4. Ran the Ethernet network connection option on the Radios and the Touch
5. The Ethernet connection icons flashed red, indicating a momentary loss of IP address due to a connectivity break from the IOGEAR adapters
6. Checked the router’s LAN DHCP log
7. The network connection routines, as indicated by the icons, had initiated DHCP renewals
8. 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)

More techie trouble. The IOGEAR Ethernet-to-WiFi adapters on the Logitech radios are having trouble with their IP addresses, handed out by the new Verizon G3100 router’s DHCP server.

The process fails, they lose their IP address and don’t know where the DHCP server is. When the failure hits I have to restart the adapter to get a DHCP ACK back from the router.

A search reveals Verizon’s G3100 has a long history of DHCP trouble, with some devices being okay, while others are not. Despite my unit having the latest firmware, the trouble persists in the G3100. The G1100 never had this problem.

I’ve set the DHCP leases static for the radios to see if that helps. If it doesn’t, I’ll see if I can set DHCP exclusions in the router. If so, I’ll connect each adapter to a Windows system to manually assign them static IP addresses.

Follow-up: Argh. The DHCP problem remains, and a check of the music network shows it can’t span subnets. TCM’s HD picture quality on Fios, having previously been outstanding, is now terrible. It’s obvious even on the 15-year-old 32″ 720p set in my bedroom, when comparing Fios TV against Watch TCM on a Roku stick. I’m seriously considering going back to my old router/extender configuration, returning all of the new gear to Verizon, and cancelling Fios TV.

My home network has been on Verizon Fios for nineteen years. As was pointed out not too long ago, the speed was originally 15 Mbps, coming over a D-Link Ethernet-only router. Screaming fast for the time, but not even qualifying as broadband anymore.^* Besides my office, I wired a couple bedrooms with Ethernet.

Later, when Verizon added Fios TV, an Actiontec router showed up with MoCA networking and Wi-Fi. With that upgrade, 20 Mbps was in the house for a long time.

Later, Verizon replaced the 1st generation Optical Network Terminal in the garage. It came with the big breakthrough router, a Verizon Quantum Gateway. I ran 100 Mbps for ages, and finally kicked up to Gigabit Internet some months ago. Do I need that much speed? Nah, but I had to make Verizon justify a price increase.

I repurposed the Actiontec router as a Wi-Fi hotspot in the guest room by assigning it, and its DHCP range, a different IP subnet. The 192.168.2.0 network uplinked to the Gateway’s 192.168.1.0 network and out to the Internet from there.

Now that I have latest Verizon router, I’ve replaced the ancient Actiontec with the still-excellent Quantum Gateway, using the same subnet trick. Wi-fi performance is vastly better than it was with the Actiontec.

It would be nice if the Gateway could act as an extender on the same subnet, but it doesn’t do that. As far as I know, anyway. The only potential limitation is with products that need to discover each other with broadcasts on the same subnet. I’m looking at you, Google Chromecast.

Does this mean I’m an advanced technical user? 😉

^* My first broadband connection, in 1998, was over Roadrunner at T-I speed — 1.5 Mbps. So of course running ten times faster was considered blazing fast.