AdguardTeam / AdguardTeam/AdguardForAndroid

Firewall blocks private DNS traffic in Automatic proxy mode

Abierto
#4,833 3 comentarios 0 reacciones 0 asignados Ver en GitHub
Bug Middle Priority: P4 TechAudit Version: arch changes
Lenguaje dominante
Sin datos de lenguaje
Estrellas
1.9k
Forks
121
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

### Please answer the following questions for yourself before submitting an issue.

- [X] I am running the latest version
- [X] I checked the documentation and found no answer
- [X] I checked to make sure that this issue has not already been filed

### AdGuard version

4.1 Nightly 10

### Environment

```markdown
- OS: Android 13
- Device: Various(Samsung, Xiaomi)
- Firmware: Various
```

### Root access

- [X] Yes, I have it.

### Issue Details
#### Prerequisites
- AdGuard DNS protection module is disabled
- Private DNS is configured in the system settings and operating
- AdGuard's operating mode is Automatic proxy
#### Steps to reproduce:

1. Turn on firewall
2. Create a global firewall rules to block all traffic
3. Allow individual app traffic with custom firewall rules (for example, Chrome)
4. Wait for 1 minute

### Expected Behavior

Chrome should be able to use the network, other applications should not be allowed to use the network

### Actual Behavior

Internet unavailable due to blocking of all DNS traffic

### Additional Information
Added by @Versty
The same setup works flawlessly if the operating mode is set to Local VPN

Original text
I basically want to block all apps from connecting to the Internet, and allow only the apps I want to connect to. So the global firewall rules blocked all connections, and the custom firewall rules allowed only some apps.

However, if a global firewall rule blocks all traffic, DNS traffic is also blocked. In AdGuard v3, DNS traffic was allowed in firewall rules. However, in v4, DNS disappeared from the app list. Therefore, DNS traffic cannot be allowed separately.

With AdGuard DNS protection, there are no DNS issues. However, since I sometimes have to turn off AdGuard, I would like to use Android Private DNS that is independent of AdGuard for minimal protection.

Since Android Private DNS is DoT, and DoT uses 853 port, the current temporary solution is to modify the range of filtering ports in low-level settings to use Android Private DNS as follows.

80..852
854..5221
5299..65535

There seems to be no problem with the use, but I don't know how it affects the actual AdGuard protection. For proper resolution, please add DNS to the custom firewall rule as before.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

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.