mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
Allow multiple IPs/CIDRs and MACs per client #739
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#739
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Bluscream on GitHub (Jun 6, 2019).
Originally assigned to: @IldarKamalov, @szolin on GitHub.
Something like
So they can share the same settings and name in the statistics
@Bluscream commented on GitHub (Jun 6, 2019):
That would allow for the stats to stay intact while something fails and the DHCP config gets messed up somehow and vice versa if some client changes/spoofs their mac the requests still count as his
@Bluscream commented on GitHub (Jun 7, 2019):
Updated issue to reflect https://github.com/AdguardTeam/AdGuardHome/issues/727#issuecomment-493659533
@alexsannikov commented on GitHub (Sep 4, 2019):
Hello AdGuard team!
Are you guys have an intention or any plans to make some kind of "Client's Profile" with client's specific settings, which may include not only "Global" settings, but also fine-tuned settings like specific DNS settings, filtering lists, logging etc.
Profiles may be created under "Group" and inherit group settings or be individual.
This was mentioned already in #435
Don't want to open another one FR as it was explained and requested many times already.
Thanks,
@ameshkov commented on GitHub (Sep 6, 2019):
@alexsannikov eventually, yes, we would like clients settings to evolve and cover all this, and that's why we're keeping #435 open
@nexeck commented on GitHub (Nov 23, 2019):
Is part of this issue: configure Client Groups with CIDR's?
Like:
IoT Group > CIDR: 172.16.10/24
Kids Group > CIDR: 172.16.20/24
@ghost commented on GitHub (Nov 23, 2019):
@nexeck Yes.