AdguardTeam / AdguardTeam/AdGuardHome

Persistent Client Based Whitelist

Abierto
#7,369 4 comentarios 0 reacciones 0 asignados Ver en GitHub
feature request
Lenguaje dominante
TypeScript
Estrellas
36.9k
Forks
2.5k
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

### 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

I have added Persistent clients for our devices. For one device I have a lot of custom domains I don't want to get blocked but for every other device I do want them blocked. At the settings of the persistent client I am able to block specific services but I am not able to add specific domains to block them for the persistent client.
Atm I have to go to custom filtering rules and add them like "@@||example.com^$client=192.168.1.100". That works fine but the problem is, I already have some custom filtering rules and each time I add some, also persistent client specific ones, it gets more messy. I am now at a point I need pretty long to find specific entries to edit them if I get some problems.

### Proposed solution

It would be awesome to add persistent client domain whitelist and blocklist at the the page where you edit them. So my custom filtering rules page is only for custom rules that affect all or several clients.

### Alternatives considered and additional information

_No response_

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.