@Gertjan Really wish I could, we have some legacy IPMI gear that can only send alerts in the clear to smtp, they support authentication but not SSL or TLS so it limits us configuring them to send directly to our external mail server, we need a service to capture them internally and them securely forward them externally.

I restored a couple more times and the VLANs worked after reassigning the NICs. I don't know what went wrong during the first restores, but it finally works on the last one.

@Rico yes, thank you.

Thanks.

You could download an upgrade image for 2.3 if you can find one, and upgrade to that offline, but that only gets you to 2.3. There isn't a way to live upgrade from 2.3 to 2.4.x offline.

Reinstalling would be much faster and easier.

A clean reinstall with 'Recover config.xml' option is probably the fastest way: https://docs.netgate.com/pfsense/en/latest/backup/automatically-restore-during-install.html
Before the reinstall take a Backup first just in case...

-Rico

Hello,

Sorry for this late response as a student and I'm not always at work.
Thank you very much for your help because that's exactly what I was looking for.

@rbuckland said in Upgraded from 2.4.3.? to 2.4.4p2 (now p3) sporadic loss of network WAN:

add in some extra monitoring somewhere ..

That for sure. I'd go and set up a small VM or server/raspi/whatever to not only ping an external source but also add 2-3 other checks as in Ping, DNS, File get / File Put (via sftp for example)
Also check if your cable modem has a status site you can call.

That's some strange error, that would let out ping and dns but nothing else.

@ady2 said in PHP Startup: Unable to load Dynamic Library. Help please:

But this situation when for unknown reason the pfSense stopped working completely, it's a bit worrying me.

You just hopped into the thread with "me too" ;) As no one knows what exactly your problem was, one can't read minds what the reason/solution is. The error above is typical for a system that wasn't on at least version 2.4.3 and had trouble with the update. As the OP wrote he had uninstalled squid it's possible that triggered an update (from an older version, 2.4.2 or older perhaps) that had the problem with not locking various packages so they don't accidentally trigger a package update of only few packages instead of a complete update of pfSense base.

@walchst said in Unable to Upgrade 2.4.3-p1 to 2.4.4:

Cheers had the same issue using Cloudflare 1.1.1.1.

Huh? You want to say that CFs 1.1.1.1 and 1.0.0.1 intercepted your SSL, broke it up and handed you a bad certificate error while contacting the netgate PKG repositories? I can hardly believe that statement as I'm running several production and live setups with CF nameservers as fallback/default for pfSense itself and never ever have I been seeing this. OpenDNS makes sense, as their offer is to filter your DNS with your setup. But CF doesn't filter their public DNS as to my knowledge!

Which will upgrade you to p3 ;)

Hi again.

Today, the firewall has decided to crash. After recovering, the IPSEC tunnel has stopped working again, but this time doesn't seem to recover in any way.
I've tried to reset de VM but still is unable to connect.
I'll try to revert to a snapshot prior of the upgrade.

@rmaeder said in Absolute Worst Experience Trying to Upgrade to 2.4.4_3:

but that should have been fixed in 2.4.4_1?

Yes, it was, but fix didn't clean your existing config file.

Open a console, option 8 and use

Add an empty

And save the config (: wq).
From now on, it will be part of your config file, it will last in there.

Note that reading in the existing config while booting doesn't break things, but importing does (when a double rrddata exists).

Also : https://github.com/pfsense/pfsense/blob/master/src/usr/local/www/diag_backup.php#L204 looks nice, but I guess (again - I'm just thinking out loud here) that a second <rrddata></rrddata> isn't removed. So, in a config backup, selected without rrddata you had always an empty rrddata section, that silently failed when restoring the actually RRD data files on disk when booting pfSense.
Actually exporting rrd data :

57f1302b-8da6-490b-b8d5-55cad482b471-image.png

and you wind up having two rrddata section again, and that went wrong.

https://redmine.pfsense.org/issues/9541

@albgen said in Upgraded to 2.4.4_3 - system now unstable:

Arrived today and i had a dead box.

'Dead box' is not a helpful term for debugging. Was it powered off with no LEDs? Was it totally unresponsive via console? Was it showing any errors? Did you reboot it? etc etc

What happened? well i don't know, it seem this version(2.4.4_3) is braking something.

And what have you seen that makes you believe this? I've been here for many years, and if I had a dollar for every user who complained about pfSense - only for the real fault to be bad hardware - then I could retire already.

Never happened since using monowall and pfsense. First time!

Like I said earlier, everything works until it breaks.

As JeGr said, if you have a problem then post a new thread.

That's a question for a FreeBSD forum. They must have made some change in FreeBSD that helps it work on that hardware. Probably newer drivers in one area or another. You'd have to ask them to know for certain.

I upgraded the Bios on my APU2 bios to v4.9.0.5 and later to v4.0.25. On both these Bios versions the 2.4.4 installation progressed passed the xterm terminal selection point to where Auto(UFS) is selectable. Beyond this point a “Device Busy” error is reported and progress is halted. While on the v4.0.25 Bios I persevered with repetitive attempts at Auto(UFS) selection and eventually it burst through the Device Busy error and progressed to a full install. At this stage I have not tried to repeat this experience. PfSense has been operational for a day now with no adverse indications. My plan now is to battle test the current 2.4.4 installation for some days and when satisfied it is solid I will go to my second mSata drive with my penultimate 2.3.4 system still intact and then replace it with a fresh 2.4.4 install, trying to replicate the “Device Busy” error and explore just what is happening there.

Yeah "any" wifi router can be just used as AP/Switch by turning off its dhcp server and connecting to your network via one of its lan ports.. Some allow for bridging the wan port into the switch/ap bridge in AP mode... Others do not..

Be yeah any soho wifi router can be just AP and switch ports. Good idea to give it an IP for its lan that your going to be connecting it to so easier to manage your wifi settings..

Keep in mind that many native firmware for these devices don't even allow for setting a gateway on the lan interface - so you have to manage them from the network they are connected to. Unless you can put 3rd party firmware on them which allows gateway - like say dd-wrt.