Hi all,
i recently modified my ZTE MF286D LTE CAT12 modem to install OpenWRT for just 1 basic function for my domotics: having more than 10 DHCP static leases.
I eventually managed to configure all my needed leases (about 60 IPs) but i noticed that some devices at their reboot occasionally use old leases despite static one configured.
an example below:
broadlinkIR device with configured IP 192.168.199.20
today device was rebooted due to power failure and it got different IP not shown on "active leases" section.
instead if I try to creatae new static lease i find it
it got the .119 on same subnet! of course i could create a new static lease for .119 but this would require me to modify involved configuration (read: Home Assistant etc..)
this is just an example.
very same issue is occurring with 2 additional RTSP cameras which at each reboot change their IP between old lease and static ones and thus requiring me to update HA configuration each time. Very annoying.
it this a bug or a feature?
my device information:
|Modello|ZTE MF286D|
|Architettura|ARMv7 Processor rev 5 (v7l)|
|Piattaforma di destinazione|ipq40xx/generic|
|Versione del firmware|OpenWrt 23.05.0 r23497-6637af95aa / LuCI openwrt-23.05 branch git-23.306.39416-c86c256|
|Versione del kernel|5.15.134|
Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
the device shown is wireless but i also have a LAN IP camera which has very same issue.
at first i was thinking that issue was devices-side because with original firmware they were sticking to static lease as expected.
seems these devices have a pool of "valid" IP addresses and randomly choose one among them at each boot. whenever they get not expected IP, they always have the same one.
for example, broadlink takes .119 instead of .20 and LAN camera takes .103 instead of .34.
probably, these IPs were valid with old firmware.
Broadlink was also reset to factory settings so theoretically should not have any remember of old lease.
Is it at all possible you have another DHCP server on the network? Or that these IPs are actually the 'fallback' IP addresses that are used if a DHCP server doesn't respond?
the only 2 devices acting badly were reset and paired again to wifi network and since then they only get the correct IP.
I think something related to some odd firmware behavior (eg. having a "pool of valid" IP addresses and picking one among them despite DHCP server proposal)