v0.108.0-b.31
版本发布时间: 2023-03-30 22:12:17
AdguardTeam/AdGuardHome最新发布版本:v0.108.0-b.60(2024-11-07 00:46:35)
Changes compared to the previous beta, v0.108.0-b.30. See CHANGELOG.md for all changes.
A special thanks to our open-source contributor, @Gobd, as well as to everyone who filed and inspected issues, added translations, and helped us test this release!
Full changelog
Added
-
Docker container's healthcheck (#3290).
-
The new HTTP API
POST /control/protection
, that updates protection state and adds an optional pause duration (#1333). The format of request body is described inopenapi/openapi.yaml
. The duration of this pause could also be set with the config fieldprotection_disabled_until
indns
section of the YAML configuration file. -
The ability to create a static DHCP lease from a dynamic one more easily (#3459).
-
Two new HTTP APIs,
PUT /control/stats/config/update
andGET control/stats/config
, which can be used to set and receive the query log configuration. See openapi/openapi.yaml for the full description. -
Two new HTTP APIs,
PUT /control/querylog/config/update
andGET control/querylog/config
, which can be used to set and receive the statistics configuration. See openapi/openapi.yaml for the full description. -
The ability to set custom IP for EDNS Client Subnet by using the DNS-server configuration section on the DNS settings page in the UI (#1472).
-
The ability to manage safesearch for each service by using the new
safe_search
field (#1163).
Changed
- ARPA domain names containing a subnet within private networks now also considered private, behaving closer to RFC 6761 (#5567).
Configuration Changes
In this release, the schema version has changed from 17 to 20.
-
Property
statistics.interval
, which in schema versions 19 and earlier used to be an integer number of days, is now a string with a human-readable duration:# BEFORE: 'statistics': # … 'interval': 1 # AFTER: 'statistics': # … 'interval': '24h'
To rollback this change, convert the property back into days and change the
schema_version
back to19
. -
The
dns.safesearch_enabled
field has been replaced withsafe_search
object containing per-service settings. -
The
clients.persistent.safesearch_enabled
field has been replaced withsafe_search
object containing per-service settings.# BEFORE: 'safesearch_enabled': true # AFTER: 'safe_search': 'enabled': true 'bing': true 'duckduckgo': true 'google': true 'pixabay': true 'yandex': true 'youtube': true
To rollback this change, move the value of
dns.safe_search.enabled
into thedns.safesearch_enabled
, then removedns.safe_search
field. Do the same client's specificclients.persistent.safesearch
and then change theschema_version
back to17
.
Deprecated
-
The
POST /control/safesearch/enable
HTTP API is deprecated. Use the newPUT /control/safesearch/settings
API. -
The
POST /control/safesearch/disable
HTTP API is deprecated. Use the newPUT /control/safesearch/settings
API -
The
safesearch_enabled
field is deprecated in the following HTTP APIs:-
GET /control/clients
; -
POST /control/clients/add
; -
POST /control/clients/update
; -
GET /control/clients/find?ip0=...&ip1=...&ip2=...
.
Check
openapi/openapi.yaml
for more details. -
-
The
GET /control/stats_info
HTTP API; use the newGET /control/stats/config
API instead.NOTE: If interval is custom then it will be equal to
90
days for compatibility reasons. See openapi/openapi.yaml andopenapi/CHANGELOG.md
. -
The
POST /control/stats_config
HTTP API; use the newPUT /control/stats/config/update
API instead. -
The
GET /control/querylog_info
HTTP API; use the newGET /control/querylog/config
API instead.NOTE: If interval is custom then it will be equal to
90
days for compatibility reasons. See openapi/openapi.yaml andopenapi/CHANGELOG.md
. -
The
POST /control/querylog_config
HTTP API; use the newPUT /control/querylog/config/update
API instead.
Fixed
-
Query log not showing all filtered queries when the “Filtered” log filter is selected (#5639).
-
Panic in empty hostname in the filter's URL (#5631).
-
Panic caused by empty top-level domain name label in
/etc/hosts
files (#5584).
1、 AdGuardHome_darwin_amd64.zip 9.15MB
2、 AdGuardHome_darwin_arm64.zip 8.96MB
3、 AdGuardHome_freebsd_386.tar.gz 8.63MB
4、 AdGuardHome_freebsd_amd64.tar.gz 8.89MB
5、 AdGuardHome_freebsd_arm64.tar.gz 8.33MB
6、 AdGuardHome_freebsd_armv5.tar.gz 8.56MB
7、 AdGuardHome_freebsd_armv6.tar.gz 8.55MB
8、 AdGuardHome_freebsd_armv7.tar.gz 8.54MB
9、 AdGuardHome_frontend.tar.gz 2.52MB
10、 AdGuardHome_linux_386.tar.gz 8.77MB
11、 AdGuardHome_linux_amd64.tar.gz 9.04MB
12、 AdGuardHome_linux_arm64.tar.gz 8.47MB
13、 AdGuardHome_linux_armv5.tar.gz 8.7MB
14、 AdGuardHome_linux_armv6.tar.gz 8.68MB
15、 AdGuardHome_linux_armv7.tar.gz 8.68MB
16、 AdGuardHome_linux_mips64le_softfloat.tar.gz 8.2MB
17、 AdGuardHome_linux_mips64_softfloat.tar.gz 8.26MB
18、 AdGuardHome_linux_mipsle_softfloat.tar.gz 8.37MB
19、 AdGuardHome_linux_mips_softfloat.tar.gz 8.41MB
20、 AdGuardHome_linux_ppc64le.tar.gz 8.37MB
21、 AdGuardHome_openbsd_amd64.tar.gz 8.88MB
22、 AdGuardHome_openbsd_arm64.tar.gz 8.32MB
23、 AdGuardHome_windows_386.zip 8MB
24、 AdGuardHome_windows_amd64.zip 8.1MB
25、 AdGuardHome_windows_arm64.zip 7.59MB
26、 checksums.txt 2.46KB