I have the same problem. The following message "The solution from robsgax is promissing." I can't follow for a container, if the VETH is just added to the central VLAN-bridge without any NAT.I have the same problem, but after installing Pi-Hole on the container - according to the manual from Mikrotik (https://help.mikrotik.com/docs/display/ ... atenetwork)
Previously I used Pi-Hole on a Raspberry and then everything was fine. Now as a Client I can only see the IP address of the Pi-Hole gate.
Have any of you found a solution to this problem?
FW rules for input and forward for port 53 (udp) are created to cover the VLANs
I tried DSTNAT to offer pi-hole (in the example 172.17.0.2 : 53) as dedicated IP in my main VLAN (e.g. 192.168.100.88 : 53) to be used as DNS-Server in DHCP Server Netwroks. But it didn't work
What is to do to see all client IPs in pi-hole and not the gateway only?
Statistics: Posted by toffifee — Sun Feb 11, 2024 6:28 am