I configured the 2.4GHz guest WiFi to act as my IoT devices network; by adding a custom firewall rule, I was able to access the devices from LAN/main WiFi, so everything runs fine.
Now I would like to assign static IPs to my IoT devices, but I encounter some problems in the GUI:
The IoT network DHCP Settings doesn't have the Static leases section
If I try to add them using the lan's Static leases section, I got an error of IP mismatch (as it's supposed to be)
I can add them using uci CLI,
but then they show up in the lan network:
probably the fastest/easiest thing to do is to check if the assigned IP is in one of the DHCP enabled networks, but at that point it should be moved to a separate section.
The longer, but maybe more correct way, is to enable the Static lease in every network with DHCP, and filter the uci results for that network.
Obviously, if you think this is an edge case/not so useful for the most of us, you can ignore that, since I can leave with using the uci CLI.
Device Model/Firmware: DGA4132 / AGTHP_2.3.3 (Tim HUB) GUI Version: 9.6.97-7e66e3cc
DebugHelper2022-07-13-2001.tar.gz
Hi, first of all many thanks for your hard work!
I configured the 2.4GHz guest WiFi to act as my IoT devices network; by adding a custom firewall rule, I was able to access the devices from LAN/main WiFi, so everything runs fine.
Now I would like to assign static IPs to my IoT devices, but I encounter some problems in the GUI:
The IoT network DHCP Settings doesn't have the
Static leases
sectionIf I try to add them using the
lan
'sStatic leases
section, I got an error of IP mismatch (as it's supposed to be)I can add them using
uci
CLI,but then they show up in the
lan
network:probably the fastest/easiest thing to do is to check if the assigned IP is in one of the DHCP enabled networks, but at that point it should be moved to a separate section. The longer, but maybe more correct way, is to enable the Static lease in every network with DHCP, and filter the
uci
results for that network.Obviously, if you think this is an edge case/not so useful for the most of us, you can ignore that, since I can leave with using the
uci
CLI.