I don’t have very little knowledge about networking but use IPFire quite a time without problems. However, last week I ran some updates to get the the most recent version of IPFire.
Turns out all clients on blue lost access to red / the internet.
Here’s the setup in more details:
green - standard LAN DHCP 192.168.0.0/24 255.255.255.0
blue - LAN to WLAN AP DHCP 172.17.2.0/24 255.255.255.0
PiHole DNS Server in Green at 192.168.0.253 for green and blue
Firewall Rule to access the PiHole DNS from blue:
TCP / UDP port 53: open from blue to green
Access to Blue: 172.17.2.0/24 / MAC filter off
I ran this setup without problems since a couple of years actually, but I have no clue how to find the error. maybe anyone with a lot of patience helps me to dig trough the fog step by step?
Hello Jon!
Thanks for picking up my topic!
I can reach the WebGUI of my AP and there is a ping tool. Tried it and,
yes, I can ping 8.8.8.8 or other IPs outside on red.
But I can’t ping 192.168.0.253, which would be my DNS (PiHole Machine)
In the Logs I can find several entries for the the blue interface FORWARDFW blue0 UDP from [172.17.2.253] to [192.168.0.253] DROP_FORWARD blue0 ICMP from [172.17.2.253] to [192.168.0.253] (which might be the ping?)
But a lot of DROP_CTINVALID for the IP of my phone: DROP_CTINVALID IN=blue0 OUT=green0 SRC=172.17.2.12 DST=192.168.0.253 LEN=576 TOS=0x00 PREC=0xC0 TTL=63
I guess that means that my phone (and other clients) can’t access the the DNS service?
MY updastream DNS serveron the PiHole is - of course - the IPFire maching which then get’s it’s information from outside DNS machines. This works flawlessly … at least on green.
Thanks Adolf!
If I understand correctly the issue there is a missing / broken hardware driver / module. In my case it’s a simple LAN card that is connected to the AP only. I can access my AP and therefor I don’t think my problem is similar.
Thanks for having a look anyway!
Chris
sometimes it needs a little walk to get the head right… Thank God I owe a dog!
IPFire was not the problem! On the same day I upgraded PiHole also, and changed a small setting
The red circle was activated!
That basically prevented PiHole to respond to clients on the blue network, because they need to make at least two hops to reach PiHole.
Now everything works again.
My band, sorry for wasting your time. Thanks for your help!
Chris
For what it is worth, I set my pihole differently with two network interfaces. The on-board Ethernet talks to green and a USB-to-Ethernet adapter talks to blue.