Author: DOuG pRATt

Self-Healing on the Internet

Most people are entertained by watching pets, whether their own or on YouTube videos. I get my jollies from obsessively checking my home network. Today I am amused to see the Squeezebox Touch has relinquished its self-determined IP address, and reclaimed its leased DCHP address.

[An aside to tastewar: A bit of digging revealed that Wireshark’s OUI database is incomplete. It failed to recognize the MAC address for my laptop PC, that’s running Squeezeplay, as belonging to Intel. Another database found it, and also revealed that 2e:2e:2e is still very much alive and kicking, at least in the IEEE’s listing.]

My curiosity piqued by the Touch once again working with the G3100 router’s DHCP server, I checked the log and… oh… my… God. The process has been running wild. Fine, whatever, as long as it works. If it wants to rotate between DHCP and APIPA, I won’t get in the way.

[LDHCP] DHCPACK on 192.168.1.212 to 00:04:20:29:e6:b1 (SqueezeboxRadio) via br-lan
2025 Mar 6 10:35:27
dhcpd
info
[LDHCP] DHCPREQUEST for 192.168.1.212 from 00:04:20:29:e6:b1 (SqueezeboxRadio) via br-lan
2025 Mar 6 10:29:42
dhcpd
info
[LDHCP] DHCPACK on 192.168.1.194 to 00:04:20:2c:84:5c (SqueezeboxRadio) via br-lan
2025 Mar 6 10:29:42
dhcpd
info
[LDHCP] DHCPREQUEST for 192.168.1.194 from 00:04:20:2c:84:5c (SqueezeboxRadio) via br-lan
2025 Mar 6 10:29:19
dhcpd
info
[LDHCP] DHCPACK on 192.168.1.246 to 00:04:20:26:7e:57 (SqueezeboxRadio) via br-lan
2025 Mar 6 10:28:40
dhcpd
info
[LDHCP] DHCPREQUEST for 192.168.1.246 from 00:04:20:26:7e:57 (SqueezeboxRadio) via br-lan
2025 Mar 6 10:23:04
dhcpd
info
[LDHCP] DHCPACK on 192.168.1.222 to 00:04:20:22:fe:84 (SqueezeboxTouch) via br-lan
2025 Mar 6 07:19:54
dhcpd
info
[LDHCP] DHCPREQUEST for 192.168.1.222 (192.168.1.1) from 00:04:20:22:fe:84 (SqueezeboxTouch) via br-lan
2025 Mar 6 07:19:54
dhcpd
info
[LDHCP] DHCPOFFER on 192.168.1.222 to 00:04:20:22:fe:84 (SqueezeboxTouch) via br-lan
2025 Mar 6 07:19:54
dhcpd
info
[LDHCP] DHCPDISCOVER from 00:04:20:22:fe:84 (SqueezeboxTouch) via br-lan
2025 Mar 6 07:19:51

 Continue reading Self-Healing on the Internet

Self-Satisfaction on the Internet

Nope, there’s nothing salacious being implied by the title of this post. It’s about the ongoing DHCP client problem with my Logitech streaming audio devices. As a result of the occasional failure to successfully complete the renewal of their private space IP address leases via DHCP, they have been falling off the network.

Several players are Squeezeplay programs on Windows, so they don’t have the problem, like these Logitech hardware players do.

  • The first three bytes of Media Access Control (MAC) addresses, commonly called Ethernet addresses, are registered to manufacturers through the IEEE.
  • MAC addresses starting with 00:04:20 are registered to Slim Devices, the name of the company that Logitech bought in 2006.*
  • All four devices had DHCP renewal failures with their native 802.11g WiFi implementations when using the G1100 router.
  • IOGEAR Ethernet-to-WiFi 802.11n adapters eliminated that problem.
  • The problem returned with the IOGEAR adapters on the new G3100 WiFi router. Sheesh. Go figure.
  • The Squeezebox Radios have been put back on their native 802.11g WiFi connections. So far, they are compatible with the G3100. Amazing.
  • The last firmware update apparently disabled WiFi on the Squeezebox Touch, I suspect unintentionally; so, for now, an external IOGEAR adapter must be used. That’s why signal strength does not appear in the device information.
  • The DHCP renewal problem persists on the Squeezebox Touch.

The TCP/IP software on the Squeezebox Touch supports APIPA — automatic private internet protocol addressing. I haven’t noticed if it’s also available on the radios.

Decades ago, in the age of 10 Mbps Ethernet hubs, I experimented with self-assigned IP addresses in Windows. In fact, until working on this latest problem, I believed the feature was unique to Windows.

https://learn.microsoft.com/en-us/windows-server/troubleshoot/how-to-use-automatic-tcpip-addressing-without-a-dh

Fortunately, I was wrong. With a self-assigned IP address, the Squeezebox Touch is playing nice with the Lyrion music server, the other Logitech players, and the wide world beyond. As long as everything continues to work I’m going to take the win and stop all of the fussing and futzing.

* Note to tastewar: 2e:2e:2e is no longer registered. https://www.wireshark.org/tools/oui-lookup.html