AdguardTeam / AdguardTeam/AdGuardHome

Unable to enable IPv6 in AdGuardHome v0.107.64 on Raspberry Pi (no UI option)

Abierto
#7,976 2 comentarios 0 reacciones 0 asignados Ver en GitHub
feature request waiting for data
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 am running AdGuard Home v0.107.64 on a Raspberry Pi4 and trying to filter DNS traffic from IPv6 clients in my local network.

Current setup:

Raspberry Pi IPv4: 192.168.x.x

Raspberry Pi IPv6: multiple global IPv6 addresses

AdGuard Home listens correctly on IPv4 (:53)

IPv6 clients fail to resolve DNS through AdGuard (dig @ example.com AAAA returns “connection refused”)

Adding IPv6 ("::") to bind_hosts in AdGuardHome.yaml prevents AdGuard from starting with error: cannot unmarshall !! seq into netip.addr

Observations:

IPv4 DNS requests are filtered correctly.

IPv6 requests never reach AdGuard.

Router handles IPv4/IPv6 internally.

Questions:

Is there a supported way in v0.107.64 to allow AdGuard Home to listen on IPv6 addresses?

If not, which version or configuration would enable IPv6 filtering without startup errors?

Thank you!

### Proposed solution

offering an UI configuration option for IPv6
offering a syntax for editing the bind-hosts / AdGuardHome.yaml

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