Just a few short lines to let you know that for me the upgrade from plain 2.4.4 to p1 went really smooth.
I have the following plugins installed:
- bandwidthd (0.7.4_1)
- iftop (0.17_2)
- net-snmp (0.1.5_2)
- ntopng (0.8.13_3)
- Open-VM-Tools (10.1.0,1)
- suricata (4.0.13_11)
All plugins had been updated some time ago and thus prior to the pfSense core, which is not recommended. In my case, though, it did not cause any issues. This was a pleasant difference to the upgrade from 2.4.3 to 2.4.4 (also see this video on YouTube), where the fact that plugins had been installed was cause for a completely broken system after the upgrade.
Pi-hole is a great and easy addition to security. The automated installation is a nice thing, but did not work on my system. The core of the problem was that I wanted to install it on a Rasperry Pi that already had dnsmasq running on it. And of course that dnsmasq was configured to provide DNS services to the Pi. What then happened was that, as an early step of the installation, the dnsmasq daemon was stopped. Logically, the Pi-hole download that was supposed to to take place, did not work.
After a few tests the following approach showed to work
- Disable dnsmasq via
sudo systemctl stop dnsmasq.service
/etc/resolv.conf to point to the DNS server in my router or something like 188.8.131.52 (dnsmasq sets it to 127.0.0.1 on every start or stop)
- Start the Pi-hole installation normally
With more and more user accounts and single-sign-on still far away from becoming a commodity, the careful choice of passwords is more important than ever. This is not complicated, just follow a few simple points.