Pi-hole won't work with VLANs?

General beta
1

I have 2 vlans off of my eth0 port on my pi.

Under Core 5.3.1, everything works good.

When I upgraded to 5.4, the devices that are on the VLANs could not access the pihole for DNS lookups. My pihole is on 192.168.1.21. VLAN 50 is 192.168.50.21--device on that VLAN can't get a DNS lookup from 192.168.50.21 Anything on 192.168.1.x can get DNS lookups on 192.168.1.21.

2

How are you bridging DNS traffic across the VLANs?

3

Don't think I did anything specific. Just created the VLANS and had Pihole listen on everything.

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.21  netmask 255.255.255.0  broadcast 192.168.1.255
        ether b8:27:eb:4b:9c:f3  txqueuelen 1000  (Ethernet)
        RX packets 60567  bytes 11536004 (11.0 MiB)
        RX errors 0  dropped 1  overruns 0  frame 0
        TX packets 35581  bytes 10153782 (9.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0.25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.25.21  netmask 255.255.255.0  broadcast 192.168.25.255
        ether b8:27:eb:4b:9c:f3  txqueuelen 1000  (Ethernet)
        RX packets 4087  bytes 293006 (286.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 231  bytes 31410 (30.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0.50: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.50.21  netmask 255.255.255.0  broadcast 192.168.50.255
        ether b8:27:eb:4b:9c:f3  txqueuelen 1000  (Ethernet)
        RX packets 10577  bytes 662884 (647.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2093  bytes 294229 (287.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
4

There seems to be a small bug with the interface listening behavior resetting itself (see here). Please try switching from listen on all interfaces to listen on one specific interface and back to listen on all interfaces. Is the issue now fixed?

2 Likes
5

@piman58 Did you get a chance to do what @Coro suggested?

6

Looks like that worked. Thanks!