Thanks very much for your further input.
I followed the guide, that I linked (to set up MacVlan, and now have Adguard running with the following container variables:
services:
adguardhome:
container_name: adguardhome
image: adguard/adguardhome:latest
hostname: adguardhome
restart: unless-stopped
ports:
- 53:53/udp
- 53:53/tcp
- 80:80/tcp
volumes:
- /etc/localtime:/etc/localtime:ro
- /srv/dev-disk-by-uuid-85c4513d-cfd9-4134-ad11-5d6552e81a81/appdata/adguardhome/work:/opt/adguardhome/work
- /srv/dev-disk-by-uuid-85c4513d-cfd9-4134-ad11-5d6552e81a81/appdata/adguardhome/conf:/opt/adguardhome/conf
environment:
- PUID=1001
- PGID=100
networks:
mynet:
ipv4_address: 192.168.1.241
networks:
mynet:
external: true
Display More
Once I remembered to change my router's DNS to the new IP address, everything was running as expected but my Wireguard tunnel is still not working.
My only reason for wanting external access to my server, at the moment, is to use the HomeAssistant app while I am away from home.
However, I was hoping to also add some sort of back up for my photos at some point, when I am out.
As a test, I set up my Wireguard tunnel to only work with my Firefox app.
When the tunnel is down, the app works fine but when it is activated I cannot access anything.
It does seem that Adguard has somehow prevented my use of the Wireguard plugin.
Edit - as a test, I changed my router's DNS back to auto and stopped the Adguard Container.
My Wireguard tunnel still does not work, so there is some change that I have made that is stopping it from running all together.
I have looked at the logs, on my Wireguard app, and it keeps saying
"@set_metadata: update dataspace from GM"
about 10 times per second, so something really odd is going on.