Hi, I ma very disappointed the fact that every system update clears all my additionally installed packages.
Even if they have no impact on openwrt and have no special system dependencies, like “MC”.
Hi,
this is normal due to how OpenWrt implements upgrades.
Unfortunately, there is nothing you can do about it, but you can try to generate a backup of your opkg installed packages: HOW-TO: Script: List My OPKGs (to a file for backup)
Thanks for explanation!
I have a small request. Could you attach (or provide a link to) the gl-sdk4-adguardhome package for me, version 'git-2024.246.27243-2ec761a-1' (This is the version from the latest firmware release).
And also the same package with a version older than that, from previous release, for example.
I am experiencing very poor performance with the current version of adguard 0.107.46. The only other discussion I could find is Very slow and increasing "Average upstream response time" · Issue #6818 · AdguardTeam/AdGuardHome · GitHub.
Some people write that downgrading to *.43 helps to solve the problem.
I would be very grateful if you could send me a couple of these ipk's. Then I'll report on the results of the experiment.
(H.W.> GL-MT2500 / aarch64-corex-a53)
@Bruce Could you assist here?
I've updated to 4.7.0 (Beta) with AdGuard v0.107.52
And still the performance of DNS-resolve is very low, while AdGuard enabled.
Here are some tests:
- With AdGuard enabled:
DNS Performance Statistics:
Total domains tested: 99
Successful resolutions: 99
Failed resolutions: 0
Mean (average) resolution time: 0.4762 seconds
Median resolution time: 0.4477 seconds
Fastest resolution time: 0.0040 seconds (Domain: chinadaily.com.cn)
Slowest resolution time: 2.7638 seconds (Domain: sapo.pt)
Disabled:
DNS Performance Statistics:
Total domains tested: 99
Successful resolutions: 99
Failed resolutions: 0
Mean (average) resolution time: 0.0447 seconds
Median resolution time: 0.0073 seconds
Fastest resolution time: 0.0035 seconds (Domain: chinadaily.com.cn)
Slowest resolution time: 0.3441 seconds (Domain: corriere.it)
The timeout for a ±0.5sec significantly affects on a browser page loading (especially for a 'new' sites).
The last chance is to downgrade to version 0.107.43 or lower and test it.
(P.s. size of blacklist has only little impact on DNS request time)
There are lots of comments saying that 0.107.43 works well opposite to all newer versions. (Very slow and increasing "Average upstream response time" · Issue #6818 · AdguardTeam/AdGuardHome · GitHub)
@admon @bruce
I played with various options an my DNS Benchmark and possibly found a Bug.
I think, "Allow Custom DNS to Override VPN DNS" option (enabled) is Not work with AdGuard enabled. That means that AdGuard out DNS requests uses VPN's DNS (and VPN tunnel) instead of using non-VPN connection for DNS requests.
My VPN mode is "VPN Policy Based on the Target Domain or IP"
So, for example, steps to reproduce and results:
- VPN (wireguard) enabled. AdGuard Enabled.
- Reboot device.
- Clear cached in AdGuard.
- Benchmark DNS: Result: 0.5 sec per request.
- Disable VPN.
- Clear Cache in AdGuard.
- Benchmark DNS: Result: 0.04 sec per request.
- Enable VPN.
- Clear Cache in AdGuard.
- Benchmark DNS: Result: 0.5 sec per request. (issue occurred again).
- Disable VPN.
- Reboot device.
- Clear Cache AdGuard.
- Benchmark DNS: Result: 0.03-0.04 sec per request.
I assume the main problem is that the ping for traffic through the VPN is quite big.
The best solution would be if the traffic from the AdGuard service is not be forwarded in the VPN.
I can provide you with some information on my settings or local tests, just give me the necessary instructions on what to do.
I don't agree because it would compromise your privacy. I don't have these issues on my device - but I am only using VPN servers near me.
If ADG traffic does not forward to in the VPN, it will cause DNS leaks, so the VPN has no meaning in protecting privacy.
It doesn't make sense.
The 'Mean (average) resolution time: 0.4762 seconds' seems not bad, VPN tunnel cannot provide the same response speed and bandwidth as the WAN.