Nigtmare with latest version of PfSense

Networking & Firewalls
1

I’ve had PfSense for some time. Plus at work CE at home. Love it. Upgrading by the GUI and tweaking and modifying as required. Always play at home first. Then because I was an idiot I tried the new DHCP server and it seemed fine. Then after a few days it refused to provide IPs. After playing for a while I decided to roll back and then I discovered the new rules on downloads. So I installed the latest and greatest and found that I had lots of connection errors, no package updates, wouldn’t allow access to NGinx PM serving containers, after playing for a while I found an old 2.5.2 image and rebuilt it. All fine. I could connect and everything worked. Package Manager wouldn’t install anything so I upgraded to 2.7.0. It doesn’t see 2.7.2. and now it can’t retrieve the package information. DNS works fine I can access the Interweb fine, it says I’m on the latest PfSense version at 2.7.0. I tried upgrading via the console but no joy.
So I install 2.5.2 and everything works. I then upgrade via GUI to 2.7.0 to install NGBlocker. Everything bar Package Manager works which defeats the upgrade.
I install 2.7.0 or 2.7.2 via the new installer and I can get outward connections but not incoming. But I install 2.7.2 via an IMG and it works fine.
I’m now on 2.7.2 and everything is working fine. Rebuilding from notes rather than restoring from backup just in case something was corrupt.
I’m now concerned that any new upgrade is going to screw it up.

Anyone else hit this or do you have any ideas?

2

As someone who just updated several plus systems to the latest 24.11 without any issues and just built a new 2.7 CE for my lab all without any issues I am not sure why you did. Are you sure you are not having some DNS issues or blocking too many things with pfblocker?

3

Tom, as viewer of your Youtube channel I must tell you, that your pfSense video for the Update 24.11 update is being missed. :pensive:

4

I might do one soon, just catching up on a few other videos first.

5

Well it was a brand new install and I was using PfSense as my DNS resolver and pfblocker wouldn’t install due to the package issue. That doesn’t mean there wasn’t and upstream DNS problem but that sounds unlikely to hit specific builds. Like I said strange one.

6

You aren’t the only one having issues. Tom may not be running into any issues, but I have been running into issues with HAproxy and kea DHCP also. I’ve filed bug reports but they haven’t even looked at them. I’m hesitant on upgrading businesses at the moment.

7

That is still beta, so I am not using that right now.

1 Like