Author: DOuG pRATt

More on DHCP

The Logitech streaming radios are 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.

More on Mortgages

Another good backgrounder from CNBC. This one is about privatizing Freddie and Fannie, returning them to the way they were in the lead-up to the 2008 Financial Crisis. It’s a solution in search of a problem — a problem that privatizing would seem likely to create.

Listen to the hedge fund manager who’s looking forward to the “most pro-growth, pro-business, pro-American” administration. He’s expressing the same mindset that brought the financial markets to their interconnected knees in 2008.

The two biggest mistakes Obama made were at the very start of his first term. One of them was his failure to punish the investment banks. The other was the industrial policy called the HITECH Act, that artificially stimulated the market for medical information software.

Concession Speech

Wow… what a fawning sycophant. Every other word is praise for Trump.

How is it we’re dealing from a position of strength, when Hegseth is preemptively announcing Ukraine’s surrender to Pukey Putin? History repeats itself, with Chamberlain agreeing that Hitler could have the Sudetenland, in the interest of “peace for our time.”

Cartoon by Jack Kirby

I admit to being surprised that Trump’s bromance with Musk hasn’t soured yet. Also unexpected is that Vance is so visible. But now I see that Trump wants Musk to handle things domestically, with foreign policy seeming to be a 3-way split between Rubio, Vance, and Hegseth.

What is Trump himself doing? Clearly, he enjoys the trappings of the office, but he isn’t interested in actually doing the work of governing. Declaring the Gulf of America and taking over the Kennedy Center won’t bring down the cost of food. He’s just repeating the two things he knows. “You’re Fired!” from The Apprentice, and big talk about putting up hotels and casinos, but this time the land deal he wants is the Gaza Strip.

A DHCP Server Valentine for Clients

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)

Looking for a Handout

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.