I recently upgraded my Flint 3 from 4.8.4 to 4.9.0 and kept settings. I had a couple of devices with reserverd IPs in the GL.inet interface, they all got removed on upgrade. Upon investigating the LuCI interface, I didn’t see the reservations there either.
Has the GL.inet interface the same effect as reserving in LuCI or is it using a different process? Which method is more reliable?
Anyone else had this happen? I see some older locked threads with this reported issue but no meaningful reply.
From what I have checked:
GL-iNet uses /etc/config/gl-client to track its own static properties.
However, the real static things happen in luci and in file /etc/config/dhcp, so far I think the gl-client config is only to track and show visibility on the clients page, it does not rebuild it from this file inside the dhcp file.
Maybe the static clients still exist but just not under gl-clients.
Here is how such client is defined inside this gl-client config:
config client
option mac 'redacted'
option alias 'GL-MT3600BE'
Kind of strange tho... there is not really a reason to hold a second file, especially given that OpenWrt also has a api to for each loop uci nodes.
Hi,
Thank you for reporting this.
As mentioned above, the GL.iNet interface does maintain some client-related information separately, for example client aliases in /etc/config/gl-client .
However, the actual DHCP static lease used for an IP/MAC reservation is stored in /etc/config/dhcp. Therefore, the GL.iNet interface and LuCI are not completely identical in terms of the additional fields they expose, but the IP reservation itself ultimately relies on the DHCP configuration.
Could you please SSH into the router and run the following command and check whether the previous MAC/IP reservation entries are still present there.
grep -A5 "^config host" /etc/config/dhcp
We also tested upgrading a Flint 3 from v4.8.4 to v4.9.0 locally with settings preserved, and the configured Address Reservation remained normally after the upgrade.
Hi charles2,
Thanks for your testing. I can confirm that the webGUI was reporting the same as your screenshots post upgrade, however after the lease expired, the MAC addresses in question obtained new IP addresses and the web GUI no longer showed the MACs as reserved. As a result, I reserved them in LuCI straight after as I didn’t understand why the two interfaces are not in sync.
I confirm the reservations are in the /etc/config/dhcp currently, but I don’t know whether that’s a result of me adding them manually in LuCI after the GL.inet interface failed to keep them reserved. Me adding them manually in LuCI also resulted in the GL.inet interface showing them as not reserved anymore, but they do work correctly at present.
Hi,
Thanks for the update.
The Reserved IP option in the GL.iNet interface and the Static Lease configuration in LuCI ultimately use the same DHCP reservation mechanism. The actual IP/MAC reservation is stored in /etc/config/dhcp and used by dnsmasq.
The Reserved IP status shown on the GL.iNet Clients page also relies on the GL.iNet interface's own client/reservation association.
Therefore, a Static Lease created or modified directly in LuCI may not always be reflected in the GL.iNet interface, even though the DHCP reservation itself is already working correctly.
