You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched other issues and found no duplicates
I want to request a feature or enhancement and not ask a question
The problem
Due to the limitation described in issue #1727, it's not possible to see the ECS (EDNS Client Subnet) as a client when using AdGuard Home with OpenWRT in forwarding mode. This makes it impossible to search the query log by client IP.
Proposed solution
I’d like to be able to search using ECS IP data that is already sent in DNS queries, to help filter client requests.
As shown in the image below, the ECS 192.168.1.38/32 appears in the request details:
However, I currently can’t find any results for 192.168.1.38 in the query log. With this feature, I would be able to locate all queries containing ECS 192.168.1.38.
Alternatives considered and additional information
N/A
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
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
Due to the limitation described in issue #1727, it's not possible to see the ECS (EDNS Client Subnet) as a client when using AdGuard Home with OpenWRT in forwarding mode. This makes it impossible to search the query log by client IP.
Proposed solution
I’d like to be able to search using ECS IP data that is already sent in DNS queries, to help filter client requests.
As shown in the image below, the ECS 192.168.1.38/32 appears in the request details:
However, I currently can’t find any results for 192.168.1.38 in the query log. With this feature, I would be able to locate all queries containing ECS 192.168.1.38.
Alternatives considered and additional information
N/A
The text was updated successfully, but these errors were encountered: