Important or Recent Updates
|Updated guide for Container Manager and using MacVLAN||13/05/2023|
|Added a new section to ensure DSM continues having network access.||02/06/2023|
|Guide updated so you can choose between Macvlan or Bridge mode||12/08/2023|
|Added additional security option to the compose to restrict the container from gaining new privileges||25/10/2023|
What is AdGuard Home?
AdGuard Home is network-wide software for blocking ads and tracking. After you set it up, it’ll cover all your home devices it even includes a parental control solution, just like a PiHole it acts as your home network DNS server and will block advertising on any site you visit.
This guide will get you set up with AdGuard and cover some basic initial settings, I recommend checking out the documentation for all the various features available.
Macvlan or Bridge Mode?
The main benefit of Bridge Mode will be the ease of setup however you will find that all clients on your network will appear under the same IP as the Bridge 172.20.0.1. This won’t impact ad blocking, but it will mean you can apply device specific rules etc.
This gives you the benefit of AdGuard having its own IP address on your network, all clients appear with their real IP addresses allowing you to assign specific rules and give you some nicer stats. However, one downside is that your NAS will not be able to use AdGuard for DNS, due to the additional security features of Macvlan and its communication with its host. This is generally not an issue unless you wanted to use you ad blocking with Tailscale.
In order for you to successfully use this guide you will need to check that your Router allows you to change your network DNS servers, this is usually found in the DHCP settings.
Please follow the two initial guides below to get a restricted Docker user and Bridge Network set up, then come back here.
Let’s start by getting some folders set up for the container to use. Open up File Station create the following.
/docker/projects/adguard-compose /docker/adguard /docker/adguard/work /docker/adguard/conf
Next we are going to set up a ‘Project’ in Container Manager. Open up Container Manager and click on Project then on the right-hand side click ‘Create’.
In the next screen we will set up our General Settings, enter the following:
Next we are going to drop in our docker compose configuration, copy all the code in from the appropriate version of the container you want to run below and paste it into line ‘1’ just like the screenshot.
What on earth is a Docker Compose? Docker Compose allows us to define how Docker should set up one or more containers within a single configuration file. This file is yaml formatted and Container Manager uses the Projects feature to manage them.
Please note you will not be able to use Macvlan with a Bonded network connection e.g. ‘Bond0’. You will need to remove the bond in order to use this method.
services: adguardhome: image: adguard/adguardhome container_name: adguardhome volumes: - /volume1/docker/adguard/conf:/opt/adguardhome/conf - /volume1/docker/adguard/work:/opt/adguardhome/work network_mode: synobridge networks: macvlan: ipv4_address: 192.168.0.129 security_opt: - no-new-privileges:true restart: always networks: macvlan: name: macvlan driver: macvlan driver_opts: parent: eth0 ipam: config: - subnet: "192.168.0.0/24" ip_range: "192.168.0.254/24" gateway: "192.168.0.1"
services: adguardhome: image: adguard/adguardhome container_name: adguardhome volumes: - /volume1/docker/adguard/conf:/opt/adguardhome/conf - /volume1/docker/adguard/work:/opt/adguardhome/work ports: - 53:53/udp - 3000:3000 network_mode: synobridge security_opt: - no-new-privileges:true restart: always
If you are setting up the Bridge version you can now press next and jump ahead in the guide to Web portal settings for Macvlan continue on below.
Settings Amendments for the MacVLAN
OK we now need to make some edits to the compose in order for it to work on your Network.
I have broken down the edits needed in this table it includes the line numbers and an explanation of what to edit.
|Change to the IP address you want to use for the container. Make sure this is available and not in use by another device on your network.|
|This defines the network interface the container should use, I have used eth0 which will be the first Ethernet port on your NAS. If you want to use a different port change it accordingly.|
Note! If you have Virtual Machine Manager installed change this to ovs_eth0
|We need to change this in line with your networks’ subnet – in the example I have used 192.168.0.0/24. The super quick way to work out what to use is just take the IP of your NAS and change the final digit before the /24 to 0|
|This has to be changed to the highest available IP address within the range of your subnet. Again if your network is in the 192 range the final number used from the subnet above can be changed to 254 and added to this section.|
|This will be the IP address of your Router/Gateway/DHCP Server|
Once you have made the edits you can click ‘Next’
Web portal settings
You do not need to enable anything on the ‘Web portal settings’ screen click ‘Next’ again.
On the final screen click ‘Done’ which will begin the download of the container images and once downloaded they will be launched!
The image will now be downloaded and extracted. You should see ‘Code 0’ when it has finished.
You will now see your AdGuard running and should have a green status on the left-hand side.
You should now be able to access the web interface via
Macvlan = the IP you specified in the compose followed by the port 3000
Bridge = Your NAS IP followed by the port 3000
You will now do some initial setup steps
Step 1 – click ‘Get Started’
Step 2 – You will be asked to choose the network interfaces AdGuard will listen to for DNS requests and the Web Interface. Leave these set to ‘All Interfaces’ but change the Port for the Web Interface from 80 to 3000.
You will notice the IPs highlighted in Red in the screenshot will be either 127.0.0.1 or 172.20.0.1 do not use these as suggested by the UI as they will not work.
Step 3 – You will be required to set up a Username and Password to access the Web UI. Fill these in (You could follow the Vaultwarden guide to get a password manager setup if you don’t have one already)
Step 4 – Configure your devices
The DNS address to use on your device or router/dhcp server will be
Bridge Mode = IP address of your NAS
MACVLAN Mode = IP address you assigned in the compose file
The addresses shown on the final screen in Red may show different IPs use the one I suggest above.
Click on Open Dashboard and you will be taken to the login screen.
Now log in to your account.
Once your devices start to update with the new DNS server IP you will begin seeing traffic in your Dashboard. (This can take up to 24 hours)
From here you can set up some initial settings such as additional ‘Filters’ (blocklists) or define additional upstream DNS providers who handle the requests that make it past the filters in Settings > DNS Settings.
More settings can be found here
You are ready to roll 🙂
What ports does AdGuard use in Macvlan Mode?
|853||TCP||DNS over TLS|
|443||TCP||HTTPS/DNS over HTTPS|
|784||UDP||DNS over QUIC|
|8853||UDP||DNS over QUIC|
|67||IPv4 UDP||DHCP – Only used when the ipv4 DHCP server is enabled.|
|68||TCP||DHCP – Only used when the ipv4 DHCP server is enabled.|
|68||UDP||DHCP – Only used when the ipv4 DHCP server is enabled.|
|547||IPv6 UDP||DHCP – Only used when the ipv6 DHCP server is enabled.|
|3000||TCP||For the WebUI|
Buy Me a Coffee or Throw me some Sats
If you have found my site useful please consider pinging me a tip as it helps cover the cost of running things or just lets me get the odd beverage. Plus 10% goes to the devs of the apps I do guides for every year.