I wanted to add reservations to my IOT devices so I can add hostnames (so they show up in Pihole.. currently I just see a lot of IPs and have to look them up in the router UI). When I try to enable reservations I get warnings saying they won’t work.
This was previously reported here, but the thread was closed without conclusion:
Is this supported?
Yes. Reserved IP addresses are supported for Guest/IoT clients, provided the reserved address belongs to that network’s subnet. The warning is currently a UI validation issue: it checks the address against the Main LAN subnet instead of accounting for Guest/IoT subnets. The reservation itself should still take effect after the client renews its DHCP lease or reconnects.
You can confirm it by reconnecting one IoT device and checking whether it receives the same reserved address. This was also confirmed by GL.iNet staff in a recent thread.
This reply was generated by AI. Please verify its accuracy.
GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.
Thanks, this sounds good.
However…. For clients on the main LAN, I can modify their reservations in the Network → LAN section. However, this is not the case for IoT/Guest. Those reservations do not show in the same place on the corresponding section (nor in the LAN) section. This means I cannot edit them and assign hostnames.
Is there a way to do this?
The GL.iNet interface currently does not provide a Guest/IoT reservation list where those entries can be renamed. As a workaround, open Advanced Settings → LuCI → Network → DHCP and DNS → Static Leases, locate or add the lease using the device’s MAC address and an IP within the Guest/IoT subnet, then set its hostname. Avoid creating a duplicate lease for the same device, and reconnect it afterward to renew DHCP.
LuCI is the advanced OpenWrt interface, so please back up the configuration first. If the lease is not visible there, please provide the router model and complete firmware version/build so the correct behavior for that firmware branch can be confirmed.
This reply was generated by AI. Please verify its accuracy.
GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.
This does seem to work, however all of the “Reserved IP” toggles in the GL.iNet interface have become unticked when I modified them to add hostnames in LuCI.
That suggests the GL.iNet client page is no longer recognizing the LuCI-edited static-lease entries, even though dnsmasq may still apply them. Please do not re-enable the toggles yet, as that could create duplicate or overwrite the existing leases. Reconnect one IoT client and confirm whether it still receives its reserved address; if so, the unticked toggles are a UI synchronization/display issue rather than lost reservations.
Please provide the exact router model and complete firmware version/build. A support team member needs to confirm whether hostname fields added through LuCI are expected to remain compatible with the GL.iNet reservation controls on that firmware branch.
This reply was generated by AI. Please verify its accuracy.
GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.
Yep, it appears to be working as I want as long as I don’t te-toggle them. If I do, then I end up with duplicate rows in the LuCI Static Leases page because it adds another.
It’s a Flint 3E with v4.9.0 software.
Hi,
Thanks for the update. Glad to hear the reservation and hostname are now working as expected.
Just to clarify, the Address Reservation settings in the GL.iNet interface and LuCI use different configuration formats/fields and are not fully synchronized. The Description used by the GL.iNet interface is also different from the hostname field in LuCI.
Therefore, after modifying the reservation in LuCI to add a hostname, the Reserved IP status in the GL.iNet interface may no longer correspond correctly to that entry. We recommend using only one interface to manage the same reservation.
Since you have added the hostname through LuCI, you can continue managing these Guest/IoT reservations there and ignore the Reserved IP toggle status in the GL.iNet interface.
Yep, understood. It might be nice if the GL.iNet interface could detect this and avoid you messing it up with dupes though. For example, if that mac address exists in the underlying data, disabling that row and showing an “information” icon saying this entry has been modified in LuCI or something?
I found it easiest to enable the reservation for each device first in the GL.iNet list, and then switch to LuCI just to modify the hostname (and change the IP). This would be easier if I could easily tell which entries in the GL.iNet interface had already been modified in LuCI.
Hi,
Thanks for the clarification and suggestion.
Both the Reserved IP option in the GL.iNet interface and the Static Lease configuration in LuCI ultimately configure the DHCP reservation. However, changes made directly to the entry through LuCI may not currently be reflected correctly in the Reserved IP status shown on the GL.iNet Clients page.
We have recorded this suggestion and will submit it for further evaluation. Thanks again for your feedback and for sharing this use case with us.