FYI, I've added a disclaimer on the main wiki around the build issues, to raise awareness, a good thing we have manual installation instructions otherwise you're SOL currently on master/snapshot.
I hope the developers and the package maintainer can OK the patch and we can get it fixed soon however. Not sure on the exact timelines for the 0.108.x release going stable from the AGH dev team but when that happens, I'll just update master to that version and remove the patch. I've already compile tested the latest beta and it builds fine without any issues, so shouldn't be an issue.
Go 1.17 support is technically still supported with 0.108, so 21.02 can in theory build it as well, but we'll have to see. Go dependencies absolute suck sometimes and when the OpenWrt host go version gets updated it usually causes issues, unless packages get updated in line with it.
2 Likes
Good news, the change has now been merged, on the next package build run, AdGuardHome should be back in the package feeds.
For those of you using the Opkg version? Tis fixed.
1 Like
Might be a bit of a delay until the next package build run happens though, so give it 24 hours.
1 Like
opened 02:54AM - 17 May 21 UTC
bug
P3: Medium
**Background**
I have two Raspberry Pi 4B units running the latest version of R… aspberry Pi OS. Each unit has AdGuard Home installed on it and nothing more. AdGuard Home is latest version (0.106.2) and is configured identically for each unit.
The presence of two units allows one unit to provide DNS service while the other is offline (e.g., to install software patches). The units are part of 10.0.10.0/24 and have respective IP addresses of 10.0.10.6 and 10.0.10.7. DHCP functionality is disabled for both units. (DHCP is managed by my firewall.)
**Problem**
Both units send excess PTR requests for other clients in the 10.0.10.0/24 range. The response is always SERVFAIL. For example, AdGuard Home at 10.0.10.6 may send out a PTR request of 1.10.0.10.in-addr.arpa for which the response is SERVFAIL. The unit may also query their own host names, e.g., AdGuard Home at 10.0.10.7 may send out a PTR request of 7.10.0.10.in-addr.arpa. How do I stop this behavior? Is this behavior from AdGuard Home, or could it be from the underlying Raspberry Pi OS?
**Attempted Solution**
There is a box to “Enable reverse resolving of clients’ IP addresses” under Settings --> DNS Settings. I have checked and then unchecked this box to ensure this feature is off. However, an unchecked box does not stop this behavior.
**Comments**
I did not have this problem before the recent upgrade to the version 106.x series. However, since the 106.x series has been released, I have also patched the Raspberry Pi OS a couple of times. Unfortunately, the PTR requests are so excessive that they populate the first few slots of the “Top Queried Domains”. The AdGuard Home units also occupy the first and second slots of the “Top clients”.
![2021-05-16_21-41-25](https://user-images.githubusercontent.com/70501931/118425849-a7662580-b68f-11eb-924e-6566423ee866.jpg)
committed 12:01PM - 19 Apr 22 UTC
Merge in DNS/adguard-home from 3157-excessive-ptrs to master
Updates #3157.
Sq… uashed commit of the following:
commit 6803988240dca2f147bb80a5b3f78d7749d2fa14
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Tue Apr 19 14:50:01 2022 +0300
aghnet: and again
commit 1a7f4d1dbc8fd4d3ae620349917526a75fa71b47
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Tue Apr 19 14:49:20 2022 +0300
aghnet: docs again
commit d88da1fc7135f3cd03aff10b02d9957c8ffdfd30
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Tue Apr 19 14:47:36 2022 +0300
aghnet: imp docs
commit c45dbc7800e882c6c4110aab640c32b03046f89a
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Tue Apr 19 14:41:19 2022 +0300
aghnet: keep alphabetical order
commit b61781785d096ef43f60fb4f1905a4ed3cdf7c68
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Tue Apr 19 13:50:56 2022 +0300
aghnet: imp code quality
commit 578dbd71ed2f2089c69343d7d4bf8bbc29150ace
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Tue Apr 12 17:02:38 2022 +0300
aghnet: imp arp container
looks like they fixed this in the latest edge build.
(Edit) For keeping an eye on what gets patched? https://github.com/AdguardTeam/AdGuardHome/commits/master This used to be linked off the upgrade notification but they removed it.
How to configure AdGuard as default DNS/DHCP service and remove default Openwrt DNS/DHCP packs?
Unless your network is very simple and you are using the edge builds, i don't as yet recommend it.
OpenWrt's DHCP is far superior to AGH's and AGH team have not yet refactored their IPv4 and v6 mechanisms. It is due in 109 i think? (it was 108 but got bumped) (edit) it was indeed 108.
opened 04:20PM - 16 Mar 21 UTC
enhancement
P4: Low
Now that #2541 is done, this seems more possible.
However setup your machine to have a static IP (because you will be disabling DHCP during this process) then follow the install script and when it asks you to go setup AGH via the webfrontend, you then disable openwrt's DHCP and set up AGH to be DHCP. AGH will take over as it will not detect OpenWrt's DHCP. You will need to re-setup any DHCP Statics you had in OpenWrt again.
Once you have confirmed you have AGH DHCP working then you can reset your machine to DHCP instead of a static ip.
You will also NOT need to add in the PTR to dnsmasq.
And if they ever complete this? Then we wont have to manually stop in the middle of the script.
opened 03:02PM - 25 Jan 22 UTC
feature request
(Split from #4067.)
Some users would like an ability to provide default usern… ame, password, and some other data to AdGuard Home directly, instead of launching it and going through the usual setup wizard. This is useful for users who would like to set up AGH using scripts as well as for packagers.
In case if AdGuard preinstalled by using openwrt pack and configure with default settings then should i do follow?
a) Set static IP to desktop first.
b) ssh to openwrt
c) service adguard stop
d) service odhcpd stop
e) service dnsmasq stop
f) opkg remove odhcpd
g) opkg remove dnsmasq
h) service adguard start
i) https://x.x.x.x:8080 > settings > dhcp > enable dhcp > interface br-lan
Ty.
I would just stop and disable the services, not remove them till you confirm AGH dhcp is setup and running, but that looks ok. I thought you were newly installing, not modifying an existing install.
Ok let me test with disable first. Ty.
Its partially working.
Once reboot router it didn't start service, but once manually start service it assign ip address.
root@OpenWrt:~# logread | grep -i fail && logread | grep -i err && logread | grep -i warn
Thu Apr 21 22:30:41 2022 kern.err kernel: [ 2.225098] mt7621-pci 1e140000.pcie: Parsing DT failed
Thu Apr 21 22:30:41 2022 kern.err kernel: [ 2.577939] mt7621-pci 1e140000.pcie: failed to parse bus ranges property: -22
Thu Apr 21 22:30:41 2022 kern.info kernel: [ 3.334980] pci 0000:00:00.0: BAR 0: failed to assign [mem size 0x80000000]
Thu Apr 21 22:30:41 2022 kern.info kernel: [ 3.362013] pci 0000:00:01.0: BAR 0: failed to assign [mem size 0x80000000]
Thu Apr 21 22:30:41 2022 kern.info kernel: [ 0.000000] Writing ErrCtl register=00022210
Thu Apr 21 22:30:41 2022 kern.info kernel: [ 0.000000] Readback ErrCtl register=00022210
Thu Apr 21 22:30:41 2022 kern.err kernel: [ 2.225098] mt7621-pci 1e140000.pcie: Parsing DT failed
Thu Apr 21 22:30:41 2022 kern.err kernel: [ 2.473245] rt2880-pinmux pinctrl: pcie is already enabled
Thu Apr 21 22:30:41 2022 kern.err kernel: [ 2.577939] mt7621-pci 1e140000.pcie: failed to parse bus ranges property: -22
Thu Apr 21 22:30:41 2022 kern.err kernel: [ 2.814894] mt7621-pci 1e140000.pcie: pcie2 no card, disable it (RST & CLK)
Thu Apr 21 22:30:41 2022 kern.err kernel: [ 16.660366] sd 0:0:0:0: [sda] No Caching mode page found
Thu Apr 21 22:30:41 2022 kern.err kernel: [ 16.670963] sd 0:0:0:0: [sda] Assuming drive cache: write through
Thu Apr 21 22:30:46 2022 daemon.err AdGuardHome[1461]: 2022/04/21 17:00:46.721464 [info] AdGuard Home, version v0.107.6
Thu Apr 21 22:30:47 2022 daemon.err AdGuardHome[1461]: 2022/04/21 17:00:47.007858 [info] Initializing auth module: /tmp/adguardhome/data/sessions.db
Thu Apr 21 22:30:47 2022 daemon.err AdGuardHome[1461]: 2022/04/21 17:00:47.009930 [info] auth: initialized. users:1 sessions:0
Thu Apr 21 22:30:47 2022 daemon.err AdGuardHome[1461]: 2022/04/21 17:00:47.010222 [info] Initialize web module
Thu Apr 21 22:30:47 2022 daemon.err AdGuardHome[1461]: 2022/04/21 17:00:47.074235 [error] starting dhcp server: dhcpv4: finding interface br-lan by name: route ip+net: no such network interface
Thu Apr 21 22:30:47 2022 daemon.err AdGuardHome[1461]: 2022/04/21 17:00:47.081412 [info] AdGuard Home is available at the following addresses:
Thu Apr 21 22:30:47 2022 daemon.err AdGuardHome[1461]: 2022/04/21 17:00:47.082612 [info] Go to http://192.168.1.1:8080
Thu Apr 21 22:30:47 2022 daemon.err AdGuardHome[1461]: 2022/04/21 17:00:47.089143 [info] Stopped
Thu Apr 21 22:30:47 2022 daemon.err AdGuardHome[1461]: 2022/04/21 17:00:47.090084 [fatal] listen tcp 192.168.1.1:8080: bind: cannot assign requested address
Thu Apr 21 22:30:41 2022 kern.warn kernel: [ 0.000000] MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
Thu Apr 21 22:30:41 2022 kern.warn kernel: [ 0.182649] MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
Thu Apr 21 22:30:41 2022 kern.warn kernel: [ 0.305012] MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
Thu Apr 21 22:30:41 2022 kern.warn kernel: [ 0.424195] MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
Thu Apr 21 22:30:41 2022 kern.warn kernel: [ 4.392694] This architecture does not have kernel memory protection.
Thu Apr 21 22:30:41 2022 kern.warn kernel: [ 6.004953] xhci-mtk 1e1c0000.xhci: supply vbus not found, using dummy regulator
Thu Apr 21 22:30:41 2022 kern.warn kernel: [ 6.020003] xhci-mtk 1e1c0000.xhci: supply vusb33 not found, using dummy regulator
Thu Apr 21 22:30:41 2022 kern.notice kernel: [ 21.222650] random: 7 urandom warning(s) missed due to ratelimiting
Thu Apr 21 22:30:41 2022 user.warn kernel: [ 29.367863] urandom-seed: Seeding with /etc/urandom.seed
are you running two instances? it fails to start as there is a webservice at 8080?
grep for all AGH messages and double check what is taking port 8080
logread | grep -i AGH
return no message. And 8080 only configure for AdGuard only.
Here is the log messages.
logread | grep -i AdGuard
Thu Apr 21 22:30:46 2022 daemon.err AdGuardHome[1461]: 2022/04/21 17:00:46.721464 [info] AdGuard Home, version v0.107.6
Thu Apr 21 22:30:47 2022 daemon.err AdGuardHome[1461]: 2022/04/21 17:00:47.007858 [info] Initializing auth module: /tmp/adguardhome/data/sessions.db
Thu Apr 21 22:30:47 2022 daemon.err AdGuardHome[1461]: 2022/04/21 17:00:47.009930 [info] auth: initialized. users:1 sessions:0
Thu Apr 21 22:30:47 2022 daemon.err AdGuardHome[1461]: 2022/04/21 17:00:47.010222 [info] Initialize web module
Thu Apr 21 22:30:47 2022 daemon.err AdGuardHome[1461]: 2022/04/21 17:00:47.074235 [error] starting dhcp server: dhcpv4: finding interface br-lan by name: route ip+net: no such network interface
Thu Apr 21 22:30:47 2022 daemon.err AdGuardHome[1461]: 2022/04/21 17:00:47.081412 [info] AdGuard Home is available at the following addresses:
Thu Apr 21 22:30:47 2022 daemon.err AdGuardHome[1461]: 2022/04/21 17:00:47.082612 [info] Go to http://192.168.1.1:8080
Thu Apr 21 22:30:47 2022 daemon.err AdGuardHome[1461]: 2022/04/21 17:00:47.089143 [info] Stopped
Thu Apr 21 22:30:47 2022 daemon.err AdGuardHome[1461]: 2022/04/21 17:00:47.090084 [fatal] listen tcp 192.168.1.1:8080: bind: cannot assign requested address
Thu Apr 21 22:38:01 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:01.806111 [info] AdGuard Home, version v0.107.6
Thu Apr 21 22:38:01 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:01.898028 [info] Initializing auth module: /tmp/adguardhome/data/sessions.db
Thu Apr 21 22:38:01 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:01.898793 [info] auth: initialized. users:1 sessions:0
Thu Apr 21 22:38:01 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:01.899049 [info] Initialize web module
Thu Apr 21 22:38:01 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:01.909383 [info] dhcpv4: listening
Thu Apr 21 22:38:01 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:01.912810 [info] AdGuard Home is available at the following addresses:
Thu Apr 21 22:38:01 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:01.913027 [info] Go to http://192.168.1.1:8080
Thu Apr 21 22:38:01 2022 daemon.err AdGuardHome[4222]: [dhcpv4] 2022/04/21 17:08:01 Server listening on 0.0.0.0:67
Thu Apr 21 22:38:01 2022 daemon.err AdGuardHome[4222]: [dhcpv4] 2022/04/21 17:08:01 Ready to handle requests
Thu Apr 21 22:38:01 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:01.965192 [info] Starting the DNS proxy server
Thu Apr 21 22:38:01 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:01.965414 [info] Ratelimit is enabled and set to 20 rps
Thu Apr 21 22:38:01 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:01.965527 [info] The server is configured to refuse ANY requests
Thu Apr 21 22:38:01 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:01.965632 [info] DNS cache is enabled
Thu Apr 21 22:38:01 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:01.965795 [info] MaxGoroutines is set to 300
Thu Apr 21 22:38:01 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:01.965955 [info] Creating the UDP server socket
Thu Apr 21 22:38:01 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:01.966627 [info] Listening to udp://192.168.1.1:53
Thu Apr 21 22:38:01 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:01.966774 [info] Creating a TCP server socket
Thu Apr 21 22:38:01 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:01.967107 [info] Listening to tcp://192.168.1.1:53
Thu Apr 21 22:38:01 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:01.971610 [info] Entering the tcp listener loop on 192.168.1.1:53
Thu Apr 21 22:38:01 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:01.972222 [info] Entering the UDP listener loop on 192.168.1.1:53
Thu Apr 21 22:38:03 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:03.139684 [info] saving filter 1 contents to: /tmp/adguardhome/data/filters/1.txt
Thu Apr 21 22:38:03 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:03.140164 [info] updated filter 1: 898187 bytes, 46549 rules
Thu Apr 21 22:38:03 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:03.809800 [info] saving filter 2 contents to: /tmp/adguardhome/data/filters/2.txt
Thu Apr 21 22:38:03 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:03.810273 [info] updated filter 2: 263586 bytes, 7050 rules
Thu Apr 21 22:38:04 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:04.650454 [info] saving filter 1650206064 contents to: /tmp/adguardhome/data/filters/1650206064.txt
Thu Apr 21 22:38:04 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:04.651017 [info] updated filter 1650206064: 1015361 bytes, 51802 rules
Thu Apr 21 22:38:04 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:04.840515 [info] saving filter 1650206065 contents to: /tmp/adguardhome/data/filters/1650206065.txt
Thu Apr 21 22:38:04 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:04.841286 [info] updated filter 1650206065: 10607 bytes, 154 rules
Thu Apr 21 22:38:08 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:08.351655 [info] saving filter 1650206066 contents to: /tmp/adguardhome/data/filters/1650206066.txt
Thu Apr 21 22:38:08 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:08.352179 [info] updated filter 1650206066: 295656 bytes, 10375 rules
Thu Apr 21 22:38:10 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:10.049132 [info] saving filter 1650206067 contents to: /tmp/adguardhome/data/filters/1650206067.txt
Thu Apr 21 22:38:10 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:10.049502 [info] updated filter 1650206067: 72389 bytes, 3683 rules
Thu Apr 21 22:38:10 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:10.153273 [info] saving filter 1650206068 contents to: /tmp/adguardhome/data/filters/1650206068.txt
Thu Apr 21 22:38:10 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:10.153699 [info] updated filter 1650206068: 192053 bytes, 6790 rules
Thu Apr 21 22:38:10 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:10.180836 [info] saving filter 1650206069 contents to: /tmp/adguardhome/data/filters/1650206069.txt
Thu Apr 21 22:38:10 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:10.181420 [info] updated filter 1650206069: 5758 bytes, 11 rules
Thu Apr 21 22:38:10 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:10.209094 [info] saving filter 1650206070 contents to: /tmp/adguardhome/data/filters/1650206070.txt
Thu Apr 21 22:38:10 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:10.209449 [info] updated filter 1650206070: 18544 bytes, 694 rules
Thu Apr 21 22:38:10 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:10.238350 [info] saving filter 1650206071 contents to: /tmp/adguardhome/data/filters/1650206071.txt
Thu Apr 21 22:38:10 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:10.238773 [info] updated filter 1650206071: 8219 bytes, 416 rules
Thu Apr 21 22:38:10 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:10.426319 [info] saving filter 1650206072 contents to: /tmp/adguardhome/data/filters/1650206072.txt
Thu Apr 21 22:38:10 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:10.426804 [info] updated filter 1650206072: 368556 bytes, 13822 rules
Thu Apr 21 22:38:11 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:11.428872 [info] auth: user "admin" successfully logged in from ip 192.168.1.2
Thu Apr 21 22:38:21 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:21.821983 [info] saving filter 1650206073 contents to: /tmp/adguardhome/data/filters/1650206073.txt
Thu Apr 21 22:38:21 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:21.822414 [info] updated filter 1650206073: 95898 bytes, 5228 rules
Thu Apr 21 22:38:21 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:21.848091 [info] saving filter 1650206074 contents to: /tmp/adguardhome/data/filters/1650206074.txt
Thu Apr 21 22:38:21 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:21.848461 [info] updated filter 1650206074: 13408 bytes, 378 rules
Thu Apr 21 22:38:21 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:21.848562 [info] Updated filter #1. Rules: 0 -> 46549
Thu Apr 21 22:38:21 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:21.848828 [info] Updated filter #2. Rules: 0 -> 7050
Thu Apr 21 22:38:21 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:21.848979 [info] Updated filter #1650206064. Rules: 0 -> 51802
Thu Apr 21 22:38:21 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:21.849053 [info] Updated filter #1650206065. Rules: 0 -> 154
Thu Apr 21 22:38:21 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:21.849238 [info] Updated filter #1650206066. Rules: 0 -> 10375
Thu Apr 21 22:38:21 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:21.849320 [info] Updated filter #1650206067. Rules: 0 -> 3683
Thu Apr 21 22:38:21 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:21.849390 [info] Updated filter #1650206068. Rules: 0 -> 6790
Thu Apr 21 22:38:21 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:21.849458 [info] Updated filter #1650206069. Rules: 0 -> 11
Thu Apr 21 22:38:21 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:21.849528 [info] Updated filter #1650206070. Rules: 0 -> 694
Thu Apr 21 22:38:21 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:21.849597 [info] Updated filter #1650206071. Rules: 0 -> 416
Thu Apr 21 22:38:21 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:21.849665 [info] Updated filter #1650206072. Rules: 0 -> 13822
Thu Apr 21 22:38:21 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:21.849734 [info] Updated filter #1650206073. Rules: 0 -> 5228
Thu Apr 21 22:38:21 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:08:21.849806 [info] Updated filter #1650206074. Rules: 0 -> 378
Thu Apr 21 22:40:41 2022 daemon.err AdGuardHome[4222]: [dhcpv4] 2022/04/21 17:10:41 Handling request from 0.0.0.0:68
Thu Apr 21 22:40:42 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:10:42.482759 [info] dhcp: stored 1 leases in db
Thu Apr 21 22:40:42 2022 daemon.err AdGuardHome[4222]: [dhcpv4] 2022/04/21 17:10:42 Handling request from 0.0.0.0:68
Thu Apr 21 22:40:42 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:10:42.495143 [info] dhcp: stored 1 leases in db
Thu Apr 21 22:40:49 2022 daemon.err AdGuardHome[4222]: [dhcpv4] 2022/04/21 17:10:49 Handling request from 0.0.0.0:68
Thu Apr 21 22:40:49 2022 daemon.err AdGuardHome[4222]: [dhcpv4] 2022/04/21 17:10:49 Handling request from 0.0.0.0:68
Thu Apr 21 22:40:50 2022 daemon.err AdGuardHome[4222]: [dhcpv4] 2022/04/21 17:10:50 Handling request from 0.0.0.0:68
Thu Apr 21 22:40:50 2022 daemon.err AdGuardHome[4222]: [dhcpv4] 2022/04/21 17:10:50 Handling request from 0.0.0.0:68
Thu Apr 21 22:40:50 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:10:50.792353 [info] dhcp: stored 2 leases in db
Thu Apr 21 22:40:50 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:10:50.795828 [info] dhcp: stored 2 leases in db
Thu Apr 21 22:40:50 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:10:50.799345 [info] dhcp: stored 2 leases in db
Thu Apr 21 22:40:50 2022 daemon.err AdGuardHome[4222]: [dhcpv4] 2022/04/21 17:10:50 Handling request from 0.0.0.0:68
Thu Apr 21 22:40:50 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:10:50.853724 [info] dhcp: stored 2 leases in db
Thu Apr 21 22:43:56 2022 daemon.err AdGuardHome[4222]: [dhcpv4] 2022/04/21 17:13:56 Handling request from 0.0.0.0:68
Thu Apr 21 22:43:57 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:13:57.732366 [info] dhcp: stored 3 leases in db
Thu Apr 21 22:43:57 2022 daemon.err AdGuardHome[4222]: [dhcpv4] 2022/04/21 17:13:57 Handling request from 0.0.0.0:68
Thu Apr 21 22:43:57 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:13:57.741072 [info] dhcp: stored 3 leases in db
Thu Apr 21 22:56:30 2022 daemon.err AdGuardHome[4222]: [dhcpv4] 2022/04/21 17:26:30 Handling request from 0.0.0.0:68
Thu Apr 21 22:56:30 2022 daemon.err AdGuardHome[4222]: [dhcpv4] 2022/04/21 17:26:30 Handling request from 0.0.0.0:68
Thu Apr 21 22:56:31 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:26:31.282466 [info] dhcp: stored 4 leases in db
Thu Apr 21 22:56:31 2022 daemon.err AdGuardHome[4222]: [dhcpv4] 2022/04/21 17:26:31 Handling request from 0.0.0.0:68
Thu Apr 21 22:56:31 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:26:31.332789 [info] dhcp: stored 4 leases in db
Thu Apr 21 22:56:31 2022 daemon.err AdGuardHome[4222]: [dhcpv4] 2022/04/21 17:26:31 Handling request from 0.0.0.0:68
Thu Apr 21 22:56:31 2022 daemon.err AdGuardHome[4222]: 2022/04/21 17:26:31.390094 [info] dhcp: stored 4 leases in db
how odd. i wonder if it tried to load AGH before network was ready.
The rest looks fine thou. Just be aware if you add more interfaces or vlans you will have to manually configure them in the yaml file to ensure that AGH's DHCP serves those interfaces.
But is it not bug?? Before Network interface up it start? Or we can add some delay in startup so once network interface up then it start the Adguard service??
@jamesmacwhite might be able to help here. there was something about changing the start times due to a race conditions a while back. I wonder if this is down to that. (with the opkg version)
Yes that old trick work. Thanks.
a) service adguardhome disable
b) vi /etc/init.d/adguardhome. Change Start from 21 to 99 and Stop 89 to 120.
c) service adguardhome enable
d) reboot
1 Like
Is there way to add few DHCP static leases??? I added two but once reboot it all gone!! Even I don't know how to backup DHCP static leases [MAC /IP / HOSTNAME] !!
bottom of the DHCP page
ooohhh. one sec. i just thought. the opkg version may be saving that data to /tmp
so on reboot it will be lost.
Update to the edge build (uninstall opkg version and reinstall edge version) and it will save AGH into the /opt
folder and save all your data so it is not lost on reboot. Just make sure you have enough space as you need roughly 80mb (35mb x2 for AGH binary and backup when it updates)
Edge version means that top of this manual scripts steps for install? I have 7GB USB install. Overlay is already mapped to USB stick.
1 Like