Install the app
How to install the app on iOS

Follow along with the video below to see how to install our site as a web app on your home screen.

Note: This feature may not be available in some browsers.

DSM 6.2 Issue with macvlan and AdGurard setup

5
1
NAS
DS3615xs (Xpenology 6.2.3 U3)
Operating system
  1. Windows
Hi Folks,

I currently use Adguard on my network on a VM on ESXi; I was looking into setting up nginx reverse proxy on my Synolgy NAS to use instead of the current Synology Reverse Proxy, Thought I'd give AdGuard a try first after seeing a couple of good YouTube videos and am trying to get it working on my NAS to test, but just having issues.

Hoping someone can help me sanity check.

My Network is on 192.168.0.0/24
Router is 192.168.0.1 (DNS is my current AdGuard on 192.168.0.2)
IP LAN Pool is 6-250
and my NAS currently sits on 210 (been like this for years, can't be bothered to clean it up an put it somewhere else for now)

I've set up the macvlan for adguard as:

sudo docker network create -d macvlan -o parent=eth0 --subnet=192.168.0.0/24 --gateway=192.168.0.1 --ip-range=192.168.0.5/32 adguard_network

(if it all worked on 192.168.0.5, my plan would be to move it to 192.168.0.2 to replace my current AdGuard later on)

Bridge network set up as:
Subnet 192.168.5.0/24
IP Range 192.168.5.2/32
Gateway 192.168.5.1


When I try to get to the Web UI at 192.168.0.5:3000 I get nothing.

Grateful for any help in advance.
 
Hello and welcome to the forum.

Macvlan and the "issue" around it is in more than a few topics here on the forum. May I ask why did you decide to push for macvlan and not run that container in the host network? Is there any particular reason?

Keep in mind that any macvlan container will not be able to communicate with any other container on the same host if you will have any. Other LAN devices will, but on the same host, no.

Have you tried to run adguard using the host network configuration?
 
Hey Rusty,
Thanks for the quick reply; Good point, I should explain my thinking here. For all of the guides I have seen for setting up NginX Proxy Manager on Docker on a Synology, it explains to use macvlans to put the docker on it's own IP address in the network - to avoid conflicts with port 80 and port 443.
I'm using AdGuard as a test case before I go 'all in' on multiple macvlans for certain Docker Containers.
My 'grand plan' will be to have:
AdGuard on 192.168.0.2
NginX Reverse Proxy on 192.168.0.3
and my Synology on 192.168.0.4

This is why I want to go down the route of get macvlans to work rather than rely on using the host network in docker.
Hope that makes sense.

FWIW, The guides I've followed so far are:
How to Install AdGuard Home on a Synology NAS! - How to Install AdGuard Home on a Synology NAS!
AdGuard Home in Docker for Home Assistant on Synology - #010 -
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Nginx Proxy Manager Synology NAS Setup Instructions! - Nginx Proxy Manager Synology NAS Setup Instructions!

Thanks!
 
Makes sense ofc, just be aware of the implications. Also, just food for thought there are ways to run NPM without getting into 80/443 conflict and still run it all without macvlan (including adguard).


Maybe this article will help out just to see that it can be done and it does work just fine. Still, using macvlan is perfectly justified.
 
Makes sense ofc, just be aware of the implications. Also, just food for thought there are ways to run NPM without getting into 80/443 conflict and still run it all without macvlan (including adguard).


Maybe this article will help out just to see that it can be done and it does work just fine. Still, using macvlan is perfectly justified.
Thanks Rusty,

Any thoughts on my predicament of the macvlan not working though?
 
When I try to get to the Web UI at 192.168.0.5:3000 I get nothing.
Guessing you are referring to this? What is on port 3000 just to be clear? Guessing you are targeting adguard webui?

Also, I notice that you are mentioning a completely different subnet from your lan here:

Code:
Bridge network set up as:
Subnet 192.168.5.0/24
IP Range 192.168.5.2/32
Gateway 192.168.5.1

Is this a typo?

So when you say you are not getting anything, are you certain ADguard container is up and running as it should? Any logs we can have a look at? Also, how does your compose looks like?
 
Can you maybe give us your Adguard container configuration where it also shows us its in your "adguard_network" docker network with the IP address it should?

For example, here is the network settings of 'sudo docker container inspect' of one of my AdGuard containers:

1661685067973.png

And here is the output of my 'sudo docker network inspect physical_network_noproxy':
`
1661685382835.webp


1661685142944.png
 
Hi @Shadow
Here's the two screenshots:
sudo docker container inspect
1661686408572.webp

sudo docker network inspect
1661686525537.webp

[automerge]1661686808[/automerge]
Guessing you are referring to this? What is on port 3000 just to be clear? Guessing you are targeting adguard webui?

Also, I notice that you are mentioning a completely different subnet from your lan here:

Code:
Bridge network set up as:
Subnet 192.168.5.0/24
IP Range 192.168.5.2/32
Gateway 192.168.5.1

Is this a typo?

So when you say you are not getting anything, are you certain ADguard container is up and running as it should? Any logs we can have a look at? Also, how does your compose looks like?
Yep to get to the adguard WebUI ... tried 192.168.0.5 also and 192.168.0.5:3000/install.html. all nothing

Bridge network is in some of the instructions I've read so that comms can occur between the Synology NAS and the macvlan container, I don't believe that it's causing any issues or impacts here. Just wanted to include in case someone pointed out that I hadn't set one up yet.
 
I'm with @Rusty . I have no idea why you have the bridge network configured like that. My out-of-the-box Docker bridge network configuration is untouched and my containers on macvlan still work fine.

Anyway, and have you had a look at this?
So when you say you are not getting anything, are you certain ADguard container is up and running as it should? Any logs we can have a look at?
I vaguely remember AdGuard outputting to the logs if it's finishes initializing and ready to be contacted via port 3000 unless there is an error.

And have you tried pinging 192.168.0.5 ?
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Popular tags from this forum

Similar threads

I would like to thank you all for your efforts, but unfortunately still not working . But I found a...
Replies
23
Views
3,589
Those are two different layers: one is the management ui to perform actions on the api. the other is the...
Replies
12
Views
2,133
I can confirm it's not in the list. All I've got are the following: Worth noting that I'm already...
Replies
4
Views
1,849

Thread Tags

Tags Tags
None

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending content in this forum

Back
Top