I know this is a very specific topic and detailed questions, but would really appreciate any insight that you may have. I am running ZimaOS 1.7 on a server with one physical Ethernet interface (eth0). AdGuard Home is running as a Docker container using host networking.
My router is a Netgear R7800 running OpenWrt 25.12.5. LAN1 is configured as an 802.1Q trunk carrying:
-
VLAN 1: 10.0.0.0/24
-
VLAN 10: 10.0.10.0/24
I want AdGuard Home to use 10.0.10.4 on VLAN 10 so that OpenWrt can redirect all client DNS traffic to AdGuard while preserving the original client IP addresses in AdGuard’s query log.
I initially created a ZimaOS/NetworkManager VLAN interface:
eth0 → vlan10 → 10.0.10.4/24
The VLAN configuration appears correct, but communication from ZimaOS VLAN 10 to the OpenWrt VLAN 10 gateway fails. OpenWrt can communicate with ZimaOS, but ZimaOS cannot successfully ping 10.0.10.1.
I therefore removed further experimentation and am considering Docker’s documented 802.1Q macvlan method:
parent=eth0.10
Docker documentation states that specifying eth0.10 causes Docker to create the VLAN subinterface automatically.
Questions:
-
Is Docker 802.1Q macvlan using
parent=eth0.10supported/recommended on ZimaOS 1.7? -
Is there a recommended way to attach a ZimaOS-managed AdGuard Home container to this network while retaining its configuration?
-
Does the ZimaOS 1.7 App Manager modify or recreate externally-created macvlan networks or custom Compose networking?
-
Is there a ZimaOS-supported method for giving a Docker application its own IP on an 802.1Q VLAN?
-
Are there any known issues with VLANs/macvlan and the Intel I219-LM/e1000e Ethernet interface on ZimaOS?
The goal is specifically to have AdGuard receive DNS requests with the original client IP addresses, while keeping ZimaOS itself on the normal LAN.
I would prefer a supported ZimaOS/Docker approach rather than maintaining custom NetworkManager configuration on the immutable host.