Still an issue. Lost pfSense GUI connection again, after trying to access Diagnostics > Backup/restore.

Sometimes that happens if you are in the middle of an update when a new snapshot rolls out. Wait a few minutes and try again.

Same issue maybe? https://forum.netgate.com/topic/138788/no-default-route-after-reboot-using-gateway-groups -Rico

I had some trouble with the console on my Windows 10 PC but support I was able to point me to a proper copy of the drivers. Then things misbehaved in the putty session to the console (oddly garbled screen) but a power cycle got me to the menu and a factory reset. I am having a mess of trouble importing a backup from my old pfsense box and support is trying to see if they can possibly massage it to be usable in the SG-3100. I'll update when I hear back from them. Thanks for the reply.

The check to the left of System Watchdog means it's current. The text would be red if something is wrong.

We don't usually put out a patch release image for CE but there were a sufficient number of issues with 2.4.4 that we did this time (along with all the additional testing that incurs). P2 is a much smaller patch, installing p1 and upgrading should be painless. Steve

Almost certainly not the same issue. But small packet pass (initial handshake) big packets fail (TLS exchange) does sounds like it could be MTU. Why are you running 2.3.5 though? Unless you have a very good reason not to you should upgrade before doing anything else. Steve

Hit CTRL+F5 and try again. -Rico

work now clone the mac address of the router there work thx for the help

Solved here too - update worked properly now.

@frankbicknell I have it all sorted out. I didn't quite realize that it is the hostname and domain of the pfSense appliance. It is up and running and so far with pfBlocker my spam, scams, and extortion emails are down by 90%. What a great piece of work. Thank you.

@chpalmer said in Package update/reinstall issues after update to 2.2.4_2: Assuming you mean 2.4.4-p2 Anything 2.2 would be quite old and unsupported. yes! oops

same problem for me on all my pfsense servers, all of them resolve srv records fine... seems to be a problem take a look at the twiter netgate account https://twitter.com/NetgateUSA/status/1088455647807455232

Our twitter feed is a good spot: https://twitter.com/NetgateUSA/status/1088455647807455232 We will update there when it's resolved.

@datpif said in Crashes after upgrading to latest version: Ok so it turns out that it might be the Wemo smart plug. I have had solid 24 hours without a crash how odd. Unclean power can do all sorts of weird things, so it's not terribly surprising. If you have a power strip or UPS that done line conditioning you could put that after the smart plug, but odds are if you have it on a smart plug you don't want a UPS. Though you wouldn't normally want to shut off a firewall by a smart plug, that harsh of a shutdown is likely to cause filesystem corruption.

Soon.

@gertjan Sometimes it is worth mentioning the source, to get feedback from people having the same issues. We mention it happens to all the hardware from this supplier to let you guys know that it isn't a single one with a disk error or problem. Thanks in advance for constructive feedback ;)

I personally wouldn't open gui on the wan, unless you have a way to lock it down to your source IP... You prob be better VPN to pfsense, then hit the gui.. Problem with that is if problem with vpn you can not access gui to fix it ;) If you know the source IP(s) that you will admin from, then you can allow access to gui port via a rule on your wan limiting it to these source IP(s).

This is why I put the worst case in quotes. ;-) -Rico