Groups not working due to wrong ingress device

[idoodler]

The issue I am facing:
I can't get groups to work properly, in the Query Log i can see that the client for the majority of the requests is 172.30.0.1 which is the the IP of the dockers bridge network gateway.

The Groups would be used to whitelist my significant others devices as he doesn't like to encounter blocked pages.

Details about my system:
Running inside docker on an Ubuntu Server Host

FTL version:	v5.23
Process identifier (PID):	16316
Time FTL started:	Sat Aug 26 18:16:13 2023 UTC
User / Group:	pihole / pihole
Used memory:	9.99 MB
DNS cache size:	10000
DNS cache insertions:	18300
DNS cache evictions:	0

What I have changed since installing Pi-hole:
Created a group and added his devices via IP and MAC to it

[chrislph]

Can you produce a debug log please using either pihole -d or Tools > Generate debug log and post the token URL here.

[Bucking_Horn]

To employ Pi-hole's client-specific filtering, your clients need to send their DNS requests directly to Pi-hole, lest Pi-hole would not be able to attribute DNS requests to individual client IPs.

Depending on your configured Docker network mode (e.g. in its default bridge network mode), Docker would be isolating a container into a separate subnet, NATing traffic from your normal home network.

You should consider to run your Pi-hole container in network mode that wouldn't do that, e.g. macvlan or host.

For further details, refer to Docker's documentation on its different network mode drivers.

[idoodler]

That makes sense. Thanks for the advice.

That requires some rework of my containers and of Pihole I'll do it when it disturbes the whole network the least and will keep you updated.

Edit
I am using host network now and it works. Thanks!