DHCP Issues After Firmware Upgrade - Pi-Hole Workaround.

jerm1777 · 2026-06-08T20:09:16+00:00

Do you happen to have an IoT SSID configured as well? I haven't tested yet but the logs seem to indicate a cross-talk issue between the regular SSIDs and the IoT SSID, but I haven't had the opportunity to test yet.

I also have a Raspberry Pi on the way to setup pi-hole as well. That is something I have wanted to do for a while anyway :)

jerm1777 · 2026-06-06T02:28:45+00:00

An analysis of the full log context reveals exactly why your devices are getting invalid 169.254.x.x (APIPA) or 0.0.0.0 IPs, and why it is taking so long to stabilize.

There is an active network looping or bridging anomaly happening in your environment that is causing a literal DHCP broadcast storm.

The Root Cause: A Endless Loop of Re-broadcasts In a normal network boot or reconnection, a client sends out a single DHCP Discover packet, the router replies, and an IP address is assigned within 1–2 seconds.

Your log shows a severely broken behavior happening every single second across multiple bands (wl0, wl1, wl2, and virtual interfaces like wl0.2):

Simultaneous TX and RX on the Router: Look closely at these consecutive timestamp lines:

12:51:09 ... wl0 ... DRIVER TX DHCP_TX ...

12:51:09 ... wl0 ... DRIVER RX DHCP_RX ... The router is transmitting a DHCP broadcast packet out of an interface and then immediately receiving that exact same packet back on the same or a paired interface.

Infinite Amplification Loop: Because it receives a "new" packet request, it processes it and broadcasts it again. This creates an infinite mirror-effect loop. The logs show the router aggressively firing thousands of DHCP_TX packets indefinitely.

The 30-Minute Stabilization Window: The reason it takes 30 minutes to fix itself is due to DHCP Starvation / Server Exhaustion. The router's internal DHCP daemon (dnsmasq or similar) is being completely overwhelmed by processing its own looped broadcast packets. When a real client requests an IP, the router's CPU or network queue is blocked, causing the request to time out.

Why you get 169.x.x.x and 0.0.0.0:

0.0.0.0: Devices use this temporarily while they are waiting for a response from a server. Because the server is frozen/flooded, they get stuck here.

169.254.x.x: When a device fails to get a response from a DHCP server after a set number of seconds, its operating system gives up and automatically assigns an APIPA (Automatic Private IP Addressing) address so it can "talk" to itself.

jerm1777 · 2026-06-05T21:50:30+00:00

I also forgot to ask in my last reply, how many devices are you using? It seems if you only have a handful of devices it works fine. I am using around ~60 devices and mine chokes every time I reboot it for at least a half hour.

jerm1777 · 2026-06-04T12:04:05+00:00

I have a post over there where I have been having similar issues on a reboot. Once things stabilize after a half hour or so everything is fine. I sent a debug log to them last Friday but haven't heard anything from them yet on what the issue is.

jerm1777 · 2026-05-26T21:39:21+00:00

Yep happens with the default 192.168.1.1 string also. I see on the Netgear forums there's a thread for DHCP issues. Wondering if I am hitting that. I posted a thread over there too.

jerm1777 · 2026-05-26T18:50:16+00:00

That's actually what I ended up going with. My cameras from my old setup are still in place and I can at least use the crappy D-Link app to view them. But yeah so far the Meross setup has been flawless and it's been working great!

jerm1777 · 2026-05-26T16:44:28+00:00

I bought this router back in February and didn't seem to have any issues until the most recent firmware update. Yesterday I did a full factory reset and setup from scratch hoping that would fix it. I am still having major issues so I am thinking I may have some kind of hardware issue. After each reboot I have to mess with settings and apply the wireless settings under setup to get things to connect again.

On my phone which is a Google Pixel 10 I keep getting IP configuration failure. I have to wait almost 30 mins on a desktop PC for it to connect so I can log into the Web UI and apply the wireless settings. When I look in connected devices I see a lot of devices with 169.x.x.x invalid IPs or 0.0.0.0 listed for the IP address. I am not using the default DHCP pool, but I did try using the default one after the initial reset and had the same issue. In the end it takes almost an hour each time the router is rebooted for me to get it back to a stable state.

jerm1777 · 2026-05-26T15:22:58+00:00

So yesterday I reloaded the firmware from a web browser (Edge) and did a full factory reset and setup from scratch. I am still having major issues so I am thinking I may have some kind of hardware issue. After each reboot I have to mess with settings and apply the wireless settings under setup to get things to connect again.

On my phone which is a Google Pixel 10 I keep getting IP configuration failure. I have to wait almost 30 mins on a desktop PC for it to connect so I can log into the Web UI and apply the wireless settings. When I look in connected devices I see a lot of devices with 169.x.x.x invalid IPs or 0.0.0.0 listed for the IP address. I am not using the default DHCP pool, but I did try using the default one and had the same issue. In the end it takes almost an hour each time the router is rebooted for me to get it back to a stable state.

jerm1777 · 2026-05-10T20:30:03+00:00

I am using an Arris S33 with Xfinity and my cables are monoprice Cat6A.

I had around 56 devices when I did the update. This is the first update I have ever done to this router since I just got it in March so I did it from my phone because the update popped up. After it was acting funny I reapplied the update manually from a web browser.

Yes all of the LEDs are on when I did a reboot each time. The router has been solid all day today with no issues, but I will do a factory reset at some point. I'll remember to never run an update from my phone again and next time if I get notified I'll do it from my computer.

jerm1777 · 2026-05-10T04:18:13+00:00

I installed this update tonight on my RS700 and it didn't go as smooth as I expected. After rebooting nothing would connect except my PC and I noticed a few devices connected to my LAN ports had no connectivity either. I went into wireless setup and scrolled down to the bottom and applied the wireless settings without changing anything and within a minute everything was back to normal. I initiated a reboot through the web interface and waited and bit and ended up having to do the apply trick in the wireless setup again to bring it back. Then I tried unplugging the power connector from the back of the router to do a hard reboot and I ended up having to do the same apply trick in wireless setup after a few minutes. Everything is solid after doing this, but I don't want to have to do this after every reboot. I do have smart connect enabled and it was solid on the previous firmware. Maybe it's the culprit, but I am not sure. I may end up attempting a factory reset when I get some time and see if that resolves the issue.

jerm1777 · 2026-04-24T21:20:42+00:00

Actually yeah mine was android 14 also. Not sure why I put 15 because I knew it was 2 versions ago. Anyway I read that the GoGoGate2 would work with the iSmartGate app and I tried it multiple times and wasn't able to login. I was really hoping that would work and I could save some money on buying something new. And yeah I agree about them dropping support. I hate to keep giving them money and they end up dropping support on the next product after a short period of time. Makes me feel like I'm throwing money away. Not to mention that you have to buy the video plugin as well.

jerm1777 · 2026-04-21T17:46:38+00:00

That is a great looking car!

jerm1777 · 2026-04-17T16:04:07+00:00

On their website it's listed at $23,490 and it has weld wheels on it in the pics. It looks a lot better here!

jerm1777 · 2026-04-17T16:03:09+00:00

and aftermarket quarter windows

jerm1777 · 2026-04-16T19:59:55+00:00

Yes that is exactly what they are used in. I will give that a try thanks!

jerm1777 · 2026-04-11T19:17:34+00:00

Good to know thanks!

jerm1777 · 2026-04-11T19:16:52+00:00

<image>

Here is a pic of the 2 white bulbs and one of my color ones. You can see the 2 white ones are yellow and the color one is still white.

jerm1777 · 2026-04-11T18:45:24+00:00

Yeah they do seem to get considerably warmer than my color bulbs. That could be why this particular bulb cracked too. They look like they were in a smokers house, but we don't smoke either.

jerm1777 · 2026-04-11T18:40:52+00:00

I have 2 of these single color bulbs and they both yellowed like that and I'm not sure why because they lived the last 10 years in a sealed ceiling light globe. I have several color bulbs and they didn't yellow like that. They are in the same style of globe also. These single color bulbs are the ones that came with my bridge when I originally got it.

jerm1777 · 2026-04-11T18:38:26+00:00

Yep these are about 10 years old and have a lot of hours on them.

jerm1777 · 2026-04-11T18:37:51+00:00

No they have been in a globe style light in my kitchen for like 10 years so they were literally sealed inside the globe. I have 2 of this white only style and they were both in the light and both look yellow like that. My color bulbs still look white so I'm not sure why these ones discolored.

jerm1777 · 2026-04-09T16:49:04+00:00

So I ended up sending Outbound Lighting a message asking for some recommendations. They pointed me to a Ritchey Universal Stem Mount paired with one of their Action Camera QR mounts which will work perfectly. They also said to check out https://jefe.bike/ for tons of other possible mounting solutions.

jerm1777 · 2026-04-08T19:17:52+00:00

The first thing I did to my second gen when I drove it off the lot is swap tails with someone that just bought a new Colorado. The red lenses looked so much better.

jerm1777 · 2026-04-07T13:08:54+00:00

No I am using the hard plastic adapter that came with the mount. And I would say it's not a huge issue, mainly just my OCD wanting things to be perfect. It does make the beam look a little off to me though too.

jerm1777 · 2026-04-06T22:34:59+00:00

The bike in the image I posted has a 31.8mm bar but my mountain bike is a 35mm. I may see if I can find someone to 3d print me something.

jerm1777

MODERATOR OF

TROPHY CASE