@Bobby1859, could be expiration of the DHCP lease. Use static IPs for stationary devices to avoid this renewal of the IP.

Bobby1859 wrote

@R1D2 

 

So my question now is: Why is the AP (or something) trying to change it’s LAN IP and mask when it is set to static?

I see this message on sites with either a flaky network or which use static MAC/IP mappings in DHCP.

I don't see such messages in stable networks with static IPs set directly in the EAP.

Bobby1859 wrote

But even if we did, why would an EAP, directly set to static AP, at least through Omada, change it's IP and mask?

Yes, Omada controller sets the IP in the EAP directly; it's stored in the EAP's flash.

Everytime the EAP is disconnected (even if it is only for a few seconds), the controller will go through the »Provisioning« and »Configuring« cycles again when the EAP is back on-line. There is a short delay until this re-configuration happens after the EAP did come back.

For example, I just disconnected my EAP from the network for 4 seconds. This is what I get in the log:

EAP3(B0-95-XX-XX-XX-XX) connected to LAN                                            2020-08-22 19:50:23

EAP3(B0-95-XX-XX-XX-XX) changed LAN IP and mask to 192.168.1.210/255.255.255.0      2020-08-22 19:49:55

Note that the EAP already had the static IP 192.168.1.210 before the short disconnect. Storing the IP in the EAP allows to still use the EAP if the connection to Omada controller drops, but the connection to the Internet router is still intact. So the EAP needs not to disconnect completely from the network, but only from the controller to cause this message to appear in the log.

Now imagine a controller running on a desktop system which goes to energy saving mode then and when ...

@Bobby1859,

yes, you will see a disconnect state after few minutes.

Does your PoE switch provide an af or an at power budget?