@GoodOmens 

GoodOmens wrote

It seems periodically (possibly after a reboot?) my WAN/LAN3 port tries to act like a WAN. The port is set to LAN and there is nothing plugged into the port. Disabling the port has no effect and I still get these errors. Here is an exert from the log:

 

Jul 11 11:31:37 192.168.0.2  2025-07-11 11:30:48 Central Command V2-New Blue House - - - WAN/LAN3: DHCP client sending DHCP-DISCOVERY timeout.
Jul 11 11:32:37 192.168.0.2  2025-07-11 11:31:38 Central Command V2-New Blue House - - - WAN/LAN3: DHCP client sending DHCP-DISCOVERY timeout.
Jul 11 11:32:37 192.168.0.2  2025-07-11 11:31:38 Central Command V2-New Blue House - - - [gateway:XXX] failed to obtain the IP address for WAN/LAN3 because no response from the server.

 

If I togle it from LAN->WAN->LAN the errors go away until a reboot. Rinse, repeat.

 

My router has a Fiber gateway plugged into Port 1 and a DAC cable plugged into SFP WAN/LAN7. Everything else is unplugged.

Log appears to be from the controller. Have you tried to forget it from the controller? 

Or create a new site to adopt it and test it? I suspect if this behaves so even after the port WAN/LAN3 is physically not connected and you can confirm it with eyesight, then it should be a problem with the config somehow. Could be corrupted config which makes the router think the port is connected somehow. 

And, does it only happen at this port? 

Was this port used before? 

  @Clive_A Interesting. Forget-> Adopt seems to have resolved it. There is nothing plugged into the port nor do I think it was ever used.

This gateway was a swap with ER7412-M2 that did use port 3 as a LAN for connecting to a switch (that is now done via SFP) so maybe something got corrupted along the way.