mirrors/AdGuardHome
1
0
Fork 0
mirror of https://github.com/AdguardTeam/AdGuardHome.git synced 2024-11-25 06:25:44 +03:00
Code Issues Projects Releases Packages Wiki Activity
Network-wide ads & trackers blocking DNS server
2427 commits 95 branches 201 tags 51 MiB
Go 60.3%
TypeScript 24.8%
CSS 12.4%
Shell 2%
Makefile 0.2%
Other 0.2%
Find a file
Artem Baskal 06594bde8f - client: Add link to 'update_failed' error toast 
Close #2062

Squashed commit of the following:

commit a1a1d4fe74dd414f83477d972bc07062e2c890ab
Merge: 9535e109 84938c56
Author: ArtemBaskal <a.baskal@adguard.com>
Date:   Tue Sep 8 10:21:47 2020 +0300

    Merge branch 'master' into fix/2062

commit 9535e10934c57c2592df234a030bad183c0086cd
Author: ArtemBaskal <a.baskal@adguard.com>
Date:   Mon Sep 7 13:59:57 2020 +0300

    Fix translation

commit e6f912d1d2793fd008c22b4418681abcc54896d0
Author: ArtemBaskal <a.baskal@adguard.com>
Date:   Mon Sep 7 12:03:45 2020 +0300

    - client: Add link to 'update_failed' error toast
2020-09-08 13:18:19 +03:00
.githooks Setup pre-commit lint hook 2020-07-15 12:49:08 +03:00
.github Pull request #730: + client: Add Hot Module Replacement 2020-08-13 11:15:45 +03:00
client - client: Add link to 'update_failed' error toast 2020-09-08 13:18:19 +03:00
dhcpd * makefile: test: use '-race' parameter on UNIX, don't use it on Windows 2020-09-03 10:10:54 +03:00
dnsfilter - DNS: didn't process requests while updating filters 2020-08-26 18:58:21 +03:00
dnsforward + DNS: add "ipset" configuration setting 2020-09-02 14:13:45 +03:00
doc * tech doc: update architecture picture 2020-03-17 18:36:10 +03:00
home * install: don't show an error about static IP if an interface is not selected 2020-09-02 15:50:09 +03:00
isdelve -(global): fixing the installation flow on windows 2019-12-23 14:57:10 +03:00
openapi * POST /control/dhcp/find_active_dhcp: add dhcpv6 server info 2020-08-20 15:19:58 +03:00
querylog - querylog: file rotation didn't work properly; fix entry searching algorithm 2020-09-02 19:42:26 +03:00
scripts Added desktop icon for a snap 2020-07-16 20:25:39 +03:00
stats + querylog,stats: anonymize client ip: /16 2020-06-03 19:08:11 +03:00
update * updater: cut 'v' prefix when comparing SelfUpdateMinVersion 2020-07-23 12:17:20 +03:00
util + service: Adding freebsd arm support 2020-07-13 13:34:38 +03:00
.codecov.yml Added codecov, goreport 2019-01-25 20:13:57 +03:00
.dockerignore CI Revamp by @crazy-max (#1873) 2020-07-09 11:53:41 +03:00
.gitattributes fix gh language 2018-10-17 13:14:45 +03:00
.gitignore CI Revamp by @crazy-max (#1873) 2020-07-09 11:53:41 +03:00
.golangci.yml Excluded some paths from golang linter 2020-07-10 22:20:46 +03:00
.goreleaser.yml Added desktop icon for a snap 2020-07-16 20:25:39 +03:00
.twosky.json + client: Refactor DHCP settings 2020-08-20 15:19:59 +03:00
AGHTechDoc.md - querylog: file rotation didn't work properly; fix entry searching algorithm 2020-09-02 19:42:26 +03:00
changelog.config.js * (ui): fix the version check - strip the v prefix 2020-07-23 12:27:14 +03:00
Dockerfile CI revamp part 2 (#1875) 2020-07-09 19:54:53 +03:00
go.mod * urlfilter v0.12.2 2020-09-01 15:37:03 +03:00
go.sum * urlfilter v0.12.2 2020-09-01 15:37:03 +03:00
LICENSE.txt Initial commit 2018-08-30 17:25:33 +03:00
main.go CI Revamp by @crazy-max (#1873) 2020-07-09 11:53:41 +03:00
Makefile * makefile: test: use '-race' parameter on UNIX, don't use it on Windows 2020-09-03 10:10:54 +03:00
README.md Update readme 2020-08-27 23:54:48 +03:00
tools.go CI Revamp by @crazy-max (#1873) 2020-07-09 11:53:41 +03:00

README.md

 

AdGuard Home

Privacy protection center for you and your devices

Free and open source, powerful network-wide ads & trackers blocking DNS server.

AdGuard.com | Wiki | Reddit | Twitter | Telegram

Code Coverage Go Report Card Docker Pulls Docker Stars
Latest release adguard-home


AdGuard Home is a network-wide software for blocking ads & tracking. After you set it up, it'll cover ALL your home devices, and you don't need any client-side software for that.

It operates as a DNS server that re-routes tracking domains to a "black hole," thus preventing your devices from connecting to those servers. It's based on software we use for our public AdGuard DNS servers -- both share a lot of common code.

Getting Started

Please read the Getting Started article on our Wiki to learn how to install AdGuard Home, and how to configure your devices to use it.

If you're running Linux, there's a secure and easy way to install AdGuard Home - you can get it from the Snap Store.

Alternatively, you can use our official Docker image.

Guides

API

If you want to integrate with AdGuard Home, you can use our REST API. Alternatively, you can use this python client, which is used to build the AdGuard Home Hass.io Add-on.

Comparing AdGuard Home to other solutions

How is this different from public AdGuard DNS servers?

Running your own AdGuard Home server allows you to do much more than using a public DNS server. It's a completely different level. See for yourself:

  • Choose what exactly will the server block or not block.
  • Monitor your network activity.
  • Add your own custom filtering rules.
  • Most importantly, this is your own server, and you are the only one who's in control.

How does AdGuard Home compare to Pi-Hole

At this point, AdGuard Home has a lot in common with Pi-Hole. Both block ads and trackers using "DNS sinkholing" method, and both allow customizing what's blocked.

We're not going to stop here. DNS sinkholing is not a bad starting point, but this is just the beginning.

AdGuard Home provides a lot of features out-of-the-box with no need to install and configure additional software. We want it to be simple to the point when even casual users can set it up with minimal effort.

Disclaimer: some of the listed features can be added to Pi-Hole by installing additional software or by manually using SSH terminal and reconfiguring one of the utilities Pi-Hole consists of. However, in our opinion, this cannot be legitimately counted as a Pi-Hole's feature.

Feature AdGuard Home Pi-Hole
Blocking ads and trackers ✅ ✅
Customizing blocklists ✅ ✅
Built-in DHCP server ✅ ✅
HTTPS for the Admin interface ✅ Kind of, but you'll need to manually configure lighthttpd
Encrypted DNS upstream servers (DNS-over-HTTPS, DNS-over-TLS, DNSCrypt) ✅ ❌ (requires additional software)
Cross-platform ✅ ❌ (not natively, only via Docker)
Running as a DNS-over-HTTPS or DNS-over-TLS server ✅ ❌ (requires additional software)
Blocking phishing and malware domains ✅ ❌ (requires non-default blocklists)
Parental control (blocking adult domains) ✅ ❌
Force Safe search on search engines ✅ ❌
Per-client (device) configuration ✅ ✅
Access settings (choose who can use AGH DNS) ✅ ❌

How does AdGuard Home compare to traditional ad blockers

It depends.

"DNS sinkholing" is capable of blocking a big percentage of ads, but it lacks flexibility and power of traditional ad blockers. You can get a good impression about the difference between these methods by reading this article. It compares AdGuard for Android (a traditional ad blocker) to hosts-level ad blockers (which are almost identical to DNS-based blockers in their capabilities).

However, this level of protection is enough for some users. Additionally, using a DNS-based blocker can help to block ads, tracking and analytics requests on other types of devices, such as SmartTVs, smart speakers or other kinds of IoT devices (on which you can't install tradtional ad blockers).

Known limitations

Here are some examples of what cannot be blocked by a DNS-level blocker:

  • YouTube, Twitch ads
  • Facebook, Twitter, Instagram sponsored posts

Essentially, any advertising that shares a domain with content cannot be blocked by a DNS-level blocker.

Is there a chance to handle this in the future? DNS will never be enough to do this. Our only option is to use a content blocking proxy like what we do in the standalone AdGuard applications. We're going to bring this feature support to AdGuard Home in the future. Unfortunately, even in this case, there still will be cases when this won't be enough or would require quite complicated configuration.

How to build from source

Prerequisites

Run make init to prepare the development environment.

You will need this to build AdGuard Home:

  • go v1.14 or later.
  • node.js v10.16.2 or later.
  • npm v6.14 or later.

Optionally, for Go devs:

Building

Open Terminal and execute these commands:

git clone https://github.com/AdguardTeam/AdGuardHome
cd AdGuardHome
make

Check the Makefile to learn about other commands.

Building for a different platform. You can build AdGuard for any OS/ARCH just like any other Golang project. In order to do this, specify GOOS and GOARCH env variables before running make.

For example:

GOOS=linux GOARCH=arm64 make

Preparing release

You'll need this to prepare a release build:

Commands:

  • make release - builds a snapshot build (CHANNEL=edge)
  • CHANNEL=beta make release - builds beta version, tag is mandatory.
  • CHANNEL=release make release - builds release version, tag is mandatory.

Docker image

  • Run make docker to build the Docker image locally.
  • Run make docker-multi-arch to build the multi-arch Docker image (the one that we publish to Docker Hub).

Please note, that we're using Docker Buildx to build our official image.

You may need to prepare before using these builds:

  • (Linux-only) Install Qemu: docker run --rm --privileged multiarch/qemu-user-static --reset -p yes --credential yes
  • Prepare builder: docker buildx create --name buildx-builder --driver docker-container --use

Resources that we update periodically

  • scripts/translations
  • scripts/whotracksme

Contributing

You are welcome to fork this repository, make your changes and submit a pull request — https://github.com/AdguardTeam/AdGuardHome/pulls

Please note that we don't expect people to contribute to both UI and golang parts of the program simultaneously. Ideally, the golang part is implemented first, i.e. configuration, API, and the functionality itself. The UI part can be implemented later in a different pull request by a different person.

Test unstable versions

There are two update channels that you can use:

  • beta - beta version of AdGuard Home. More or less stable versions.
  • edge - the newest version of AdGuard Home. New updates are pushed to this channel daily and it is the closest to the master branch you can get.

There are three options how you can install an unstable version:

  1. Snap Store -- look for "beta" and "edge" channels there.
  2. Docker Hub -- look for "beta" and "edge" tags there.
  3. Standalone builds. Look for the available builds below.

There are three options how you can install an unstable version.

  1. You can either install AdGuard Home from "beta" or "edge" distribution channel which we update periodically. If you're already using stable version of AdGuard Home, just replace the executable file with a new one.
  2. You can use the Docker image from the edge tag, which is synced with the repo master branch.
  3. You can install AdGuard Home from beta or edge channels on the Snap Store.

Report issues

If you run into any problem or have a suggestion, head to this page and click on the New issue button.

Help with translations

If you want to help with AdGuard Home translations, please learn more about translating AdGuard products here: https://kb.adguard.com/en/general/adguard-translations

Here is a link to AdGuard Home project: https://crowdin.com/project/adguard-applications/en#/adguard-home

Other

Here's what you can also do to contribute:

  1. Look for issues marked as "help wanted".
  2. Actualize the list of Blocked services. It it can be found in dnsfilter/blocked_services.go.
  3. Actualize the list of known trackers. It it can be found in client/src/helpers/trackers/adguard.json.
  4. Actualize the list of vetted blocklists. It it can be found in client/src/helpers/filters/filters.json.

Projects that use AdGuardHome

Acknowledgments

This software wouldn't have been possible without:

You might have seen that CoreDNS was mentioned here before — we've stopped using it in AdGuardHome. While we still use it on our servers for AdGuard DNS service, it seemed like an overkill for Home as it impeded with Home features that we plan to implement.

For a full list of all node.js packages in use, please take a look at client/package.json file.