OpenWrt 24.10.0 no longer grabbing WAN/WAN6 address

[Stitch7134]

Hi, I manage 3 routers at 3 different locations and two of the three routers are having the same issue.
OpenWrt, after some amount of time (less than 24 hours it seems) will just, stop having a WAN/WAN6 address . Rebooting does not fix the issue. Router 1, is a GL.iNet MT-6000 Flint 2, and had no configuration changes between ver. 23.5.0 and 24.10.0. Router 2 is a Netgear Nighthawk XR500, which had to be completely reconfigured from scratch after updating. due to the fact that its chipset was migrated to a new configuration format. Router 3 is a GL.iNet MT-3000 BerylAx and (so far) has had no problems, and no configuration changes.

The only thing that comes to mind immediately (other than the fact that they have been upgraded) is that Router 1&2 share the same ISP, Verizon (at 2 separate locations with separate IPs& different accounts.) and Router 3 uses a local ISP with a modem, but I'm not sure where to go from here. If my configs are needed please be patient as it will take me a while to be able to grab them as I said, this is 3 seperare locations. I'm with Router 1 at the moment, and am currently posting from Mobile data. Any help is appreciated, thanks.

Edit: Seeing this in the log a lot. Not sure if it's helpful

Mon Feb 24 22:41:38 2025 daemon.notice netifd: wan (5020): udhcpc: received SIGTERM
Mon Feb 24 22:41:38 2025 daemon.notice netifd: Interface 'wan6' is now down
Mon Feb 24 22:41:38 2025 daemon.notice netifd: Interface 'wan6' is setting up now
Mon Feb 24 22:41:38 2025 daemon.notice netifd: wan (5020): udhcpc: entering released state
Mon Feb 24 22:41:38 2025 daemon.notice netifd: wan (5020): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Mon Feb 24 22:41:38 2025 daemon.notice netifd: Interface 'wan' is now down
Mon Feb 24 22:41:38 2025 daemon.notice netifd: Interface 'wan' is setting up now
Mon Feb 24 22:41:38 2025 daemon.notice netifd: wan (16346): udhcpc: started, v1.36.1
Mon Feb 24 22:41:38 2025 daemon.notice netifd: wan (16346): udhcpc: broadcasting discover

[psherman]

Typically this would be an isp issue. Possibly the modem or head-end not expecting the MAC address of your router. In some situations, the mac presented may be different after an upgrade for a number of possible reasons. Or, if your isp requires pppoe or vlan, you may not have the right configuration.

Do you have another router to use as a test? Two things you can do.

• connect a cable between the lan of another router and the wan of the router that isn’t working properly — the dhcp server of the upstream should issue an address to the device in question. If it works, there is nothing wrong with the device in question.
• connect the alternate router to the isp. Does it grab an address? If not, you have an issue with the isp side.

The solution may be as simple as rebooting your modem a few times to clear the previous Mac and allow it to learn a new one.

[Stitch7134]

At least for Router 1, leaving it unplugged for ~5 minutes and plugging it back in seemed to do it... I guess "Turn it off and back on again" should have an "and wait about 5 minutes" in between lol. Marked as solution because I feel like it'll be the same over @ Router 2. If not I guess I can always open another thread.

Thanks so much psherman, this forum can always count on you!