Repository navigation
Releases: JieMeiDev/AdGuardHome
Release list
v0.107.79.2
Tip
AdGuard Home Manager for iOS — manage your AdGuard Home servers and browse DNS queries and statistics on iPhone and iPad. Our dedicated ECH integration: an upcoming client release will display (ECH) for queries whose upstream connection actually accepted ECH. Pair it with the ECH-enabled core from this repository and enable ECH as documented.
Adds per-query ECH status to the upstream ECH support introduced in .1.
- Appends
(ECH)to the DNS server address in Response details, only when the connection used for the successful response actually accepted ECH. - Correctly attributes HTTP/2 and HTTP/3 connection reuse and the main or fallback upstream that supplied the final answer.
- Leaves cached responses, local responses, and older records without ECH metadata unmarked.
- Persists the status in an independent optional field and exposes it through the API, preserving the original upstream address.
- Adds tests for concurrent attribution, caching, fallback, persistence, older-record compatibility, and frontend display. No extra setting or detail row is added.
The Git tag, web interface, and executable all use v0.107.79.2. The earlier v0.107.79-ech.2 label was corrected without changing ECH/DNS behavior. Modified source files have been checked against the SHA-256 manifest saved for that deployment.
This is a personal modification based on official AdGuard Home v0.107.79 and dnsproxy v0.83.2. Original licenses and copyright notices are retained. It is not an official release and has not been officially accepted.
The repository includes the complete source of both modules, a Go workspace, build scripts, and a generic configuration example. Prebuilt packages include the complete web interface.
Related local race tests and real H2/H3 ECH exchanges have passed. Some upstream tests depend on public DNS services that are unreachable in the test network; a complete upstream CI pass is not claimed.
Linux / OpenWrt packages
The Linux packages follow the 12-architecture matrix and naming used by official v0.107.79:
| Architecture | Package |
|---|---|
amd64 |
AdGuardHome_linux_amd64.tar.gz |
386 |
AdGuardHome_linux_386.tar.gz |
arm64 |
AdGuardHome_linux_arm64.tar.gz |
armv5 |
AdGuardHome_linux_armv5.tar.gz |
armv6 |
AdGuardHome_linux_armv6.tar.gz |
armv7 |
AdGuardHome_linux_armv7.tar.gz |
mips_softfloat |
AdGuardHome_linux_mips_softfloat.tar.gz |
mipsle_softfloat |
AdGuardHome_linux_mipsle_softfloat.tar.gz |
mips64_softfloat |
AdGuardHome_linux_mips64_softfloat.tar.gz |
mips64le_softfloat |
AdGuardHome_linux_mips64le_softfloat.tar.gz |
ppc64le |
AdGuardHome_linux_ppc64le.tar.gz |
riscv64 |
AdGuardHome_linux_riscv64.tar.gz |
AdGuardHome_darwin_amd64.tar.gz remains available for macOS Intel. SHA256SUMS and checksums.txt have identical contents and cover all 13 program archives.
The 11 additional Linux packages use the same release source commit, 9df462601cdf87514719c6fef6b9affb8789ae6a, with the full web interface and version v0.107.79.2. Cross-compilation, ELF architecture and endianness, static linkage, Go build parameters, archive contents, and SHA-256 hashes have been verified. These additional architectures have not each been tested on physical devices. The existing Linux x86_64 and macOS Intel archives and their checksums are unchanged.
OpenWrt upgrade guide
Match the CPU, firmware ABI, and endianness. Run the candidate executable's --version on the router before stopping the current service. The guides cover actual installation paths, backups, atomic replacement, DNS/ECH verification, and rollback of both the executable and configuration:
- OpenWrt guide — English
- OpenWrt guide — German
- OpenWrt guide — Japanese
- OpenWrt guide — Traditional Chinese
- OpenWrt guide — Simplified Chinese
- Linux multi-architecture build script
The additional packages include English and Chinese OpenWrt guides and build metadata. The replacement procedure preserves existing DNS ports, DHCP, service accounts, and firewall settings.
Packages contain the executable, licenses, installation instructions, source manifest, and build information. No device configuration or credentials are included. The executable version is v0.107.79.2.
v0.107.79.1
Tip
AdGuard Home Manager for iOS — manage your AdGuard Home servers and browse DNS queries and statistics on iPhone and iPad. Our dedicated ECH integration: an upcoming client release will display (ECH) for queries whose upstream connection actually accepted ECH. Pair it with the ECH-enabled core from this repository and enable ECH as documented.
Adds ECH support to outbound HTTPS/H3 upstream connections from AdGuard Home.
- Enable ECH explicitly per upstream hostname, using independent resolvers to obtain HTTPS/ECH configurations.
- Includes TTL caching, coordination of concurrent lookups, and an authenticated configuration-rotation retry.
- Retains normal certificate verification. An upstream requiring ECH does not silently downgrade on failure; the existing fallback mechanism handles the error.
- Adds no frontend toggle or background refresh process.
The Git tag is v0.107.79.1. The executable retains its original deployment version, v0.107.79-ech.1. Modified source files have been checked against the SHA-256 manifest saved for that deployment.
This is a personal modification based on official AdGuard Home v0.107.79 and dnsproxy v0.83.2. Original licenses and copyright notices are retained. It is not an official release and has not been officially accepted.
The repository includes the complete source of both modules, a Go workspace, build scripts, and a generic configuration example. Prebuilt packages include the complete web interface.
Related local race tests and real H2/H3 ECH exchanges have passed. Some upstream tests depend on public DNS services that are unreachable in the test network; a complete upstream CI pass is not claimed.
Packages
AdGuardHome_linux_amd64.tar.gz— Linux / OpenWrt x86_64.AdGuardHome_darwin_amd64.tar.gz— macOS Intel.SHA256SUMS— SHA-256 checksums for these archives.
Packages contain the executable, licenses, installation instructions, source manifest, and build information. No device configuration or credentials are included. Executables retain the historical v0.107.79-ech.1 label.