starred/AdGuardHome

Fork 0

mirror of https://github.com/AdguardTeam/AdGuardHome.git synced 2026-03-04 00:01:12 -05:00

Support client group #5213

New issue

Closed

opened 2026-03-04 05:55:40 -05:00 by deekerman · 3 comments

deekerman commented

2026-03-04 05:55:40 -05:00

Owner

Originally created by @Ovear on GitHub (May 22, 2024).

Prerequisites

I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to request a feature or enhancement and not ask a question

The problem

Although we can currently use subnets/multiples IPs to identify clients.

However, it overrides client name, making it more difficult to filter query logs by client, especially for dual stack network.

Proposed solution

Consider supporting client group may be good.

Alternatives considered and additional information

Add an extra field to show/filter original client identity.

Originally created by @Ovear on GitHub (May 22, 2024). ### Prerequisites - [X] I have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions) and found no answer - [X] I have searched other issues and found no duplicates - [X] I want to request a feature or enhancement and not ask a question ### The problem Although we can currently use subnets/multiples IPs to identify clients. However, it overrides client name, making it more difficult to filter query logs by client, especially for dual stack network. ### Proposed solution Consider supporting client group may be good. ### Alternatives considered and additional information Add an extra field to show/filter original client identity.

deekerman

2026-03-04 05:55:40 -05:00

closed this issue
added the
duplicate
label

deekerman commented

2026-03-04 05:55:51 -05:00

Author

Owner

@ainar-g commented on GitHub (May 22, 2024):

Duplicate of #2527 and #5143

@ainar-g commented on GitHub (May 22, 2024): Duplicate of #2527 and #5143

deekerman commented

2026-03-04 05:55:55 -05:00

Author

Owner

@Ovear commented on GitHub (May 22, 2024):

I am not sure if this is a duplicate of those issues, as they focus on "filter rules".

However, the main theme of this issue is filtering query logs, since the ctag won't work with some scenario, such as overriding upstream DNS. And we also cannot search ctag :>

Specifically, if I want to override upstream for some clients, I have to add each client individually to make hostname searches works. Otherwise, I will lose those hostnames when I am searching through query logs.

Any suggestions?

@Ovear commented on GitHub (May 22, 2024): I am not sure if this is a duplicate of those issues, as they focus on "filter rules". However, the main theme of this issue is filtering query logs, since the ctag won't work with some scenario, such as overriding upstream DNS. And we also cannot search ctag :> Specifically, if I want to override upstream for some clients, I have to add each client individually to make hostname searches works. Otherwise, I will lose those hostnames when I am searching through query logs. Any suggestions?

deekerman commented

2026-03-04 05:55:55 -05:00

Author

Owner

@ainar-g commented on GitHub (May 22, 2024):

The first issue I've mentioned seems to cover settings in general, including custom upstream settings. Searchability in the query logs would probably be implemented after that one as well.

@ainar-g commented on GitHub (May 22, 2024): The first issue I've mentioned seems to cover settings in general, including custom upstream settings. Searchability in the query logs would probably be implemented after that one as well.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/AdGuardHome#5213

No description provided.

Rows
Columns