-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve the DHCP data validation on the UI #2842
Comments
Hi, I'm not 100% sure this is data validation related, but it may be part of that. I'm running Version: v0.106.0-b.1 on an RPI3 If I stop the service via sudo ./AdGuardHome -s stop and manually set DHCPv4 Options in AdGuardHome.yaml to have a secondary DNS (I'm running 2 instances of AdGuardHome for failover) e.g. DHCPv4 save the yaml, restart the service and make a change in the GUI e.g. change the DHCP lease time to any other value and click "save config" the settings I manually added to the yaml revert to DHCPv4 The GUI seems to reset the yaml and discard any manual changes. It would be better if the GUI only changes the yaml sections that are editable within the GUI. Thanks Matt |
Closes AdguardTeam#2842. Squashed commit of the following: commit 8580db9 Merge: a5d7187 ab85ad5 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Tue Apr 13 15:29:06 2021 +0300 Merge branch 'master' into 2842-dhcp-validation-ui commit a5d7187 Author: Ildar Kamalov <ik@adguard.com> Date: Tue Apr 13 15:08:28 2021 +0300 fix: revert deleted translation commit 5016926 Merge: 46adf2c 48d702f Author: Ildar Kamalov <ik@adguard.com> Date: Tue Apr 13 14:39:40 2021 +0300 Merge branch 'master' into 2842-dhcp-validation-ui commit 46adf2c Author: Ildar Kamalov <ik@adguard.com> Date: Tue Apr 13 14:13:12 2021 +0300 fix: no-bitwise commit 1afc403 Author: Ildar Kamalov <ik@adguard.com> Date: Tue Apr 13 13:57:43 2021 +0300 fix: IPv4 in CIDR validation commit 2035a3f Author: Ildar Kamalov <ik@adguard.com> Date: Tue Apr 13 11:58:03 2021 +0300 fix: translations commit 6dd455f Author: Ildar Kamalov <ik@adguard.com> Date: Tue Apr 13 11:57:27 2021 +0300 fix: MAC validation commit 281e49a Merge: 48b50ce 65553a2 Author: Ildar Kamalov <ik@adguard.com> Date: Tue Apr 6 18:12:06 2021 +0300 Merge branch 'master' into 2842-dhcp-validation-ui commit 48b50ce Author: Artem Baskal <a.baskal@adguard.com> Date: Mon Apr 5 19:04:35 2021 +0300 Add leases ip validation commit 8630f3b Author: Artem Baskal <a.baskal@adguard.com> Date: Mon Apr 5 13:59:16 2021 +0300 Add helper for subnet to bitmap mask conversion, write test commit 80dc7a8 Author: Artem Baskal <a.baskal@adguard.com> Date: Fri Apr 2 17:46:27 2021 +0300 2842 Update DHCP range validation in UI
Context: #2541, #2838.
Currently, there are at least three issues:
The frontend seems to only validate the last part of the
range_start
andrange_end
IPv4 addresses. It should instead calculate the difference properly and allow settings, for example,range_start
to1.2.3.4
andrange_end
to1.2.4.1
.The frontend should validate that the new static lease's IP address is within the subnet defined by the netmask.
The frontend seems to reject MAC addresses without colons. This seems overly strict, as
112233AABBCC
and11:22:33:AA:BB:CC
are technically the same. In fact, some hardware manufacturers use the first form instead of the second one.Note, that the frontend still should send the form with the colons to the backend.
The text was updated successfully, but these errors were encountered: