Hi,
I work from home. ISP speed is 200 Mbps.
I have a pfSense firewall simple configuration with my recently upgraded Pihole RP3 (upgraded from RP zero).
I setup my network to have everything on the LAN side pass through the pihole. My pfSense is the DHCP server and firewall and i have all DNS options disabled other than the DHCP DNS Setting to point to Pihole.
All was well and it was running at optimally up until my Gotomeeting demo and 1/4 through the network halted. I am not sure why.
I currently have the Pihole offline and my pfSense using google DNS. I would like to get the pihole back online and depend on it for all purposes. Any ideas and advise is appreciated.
That should all be A-OK, and is very similar to my base network (same with regards to pfsense settings, both resolver and forwarder disabled, etc etc).
You'll need to figure out why your stream ("Gotomeeting demo" is a remote video / voip kinda thing right?) choked. It may be related to a DNS resolution failure, but you'd have to check the logs for when the failure occurred to be sure: should take all of 30 seconds to establish one way or the other.
I'd personally be more suspect of pretty much every other piece of hardware involved.
Try to reproduce the issue as the first step, and repeatedly troubleshoot from that point until you've discovered the cause?
Thanks gaso.
I will investigate and walk it back to the point of failure. I do not use the VOIP on the gotomeeting. I will look a the logs and see what happened.
-gk
Gaso,
I am not sure which logs to look at, pfSenseor Pihole?
Anyhow, I reconnected my PiHole to my pfSense and started it back up and ran through the exact same scenario when the crash occurred and I can't repeat it. So, when this happens to me, I chalk it up as "Solar Flares and Sun Spots"
You'd want to start with the pihole logs to see if a domain is being blocked (will show up as a red entry, associated with the client in question), and that this block is causing an application to "throw a tantrum".
Since you can't repeat it at this time, just get used to finding blocked entries in your pihole logs, navigating around the interface, finding specific client request, etc: you'll be building muscle memory for when you need to spring into action in the future if this happens again.