I have found the solution here: https://github.com/pfsense/pfsense/commit/63b2c4c878655746f903565dec3f34b3d410153f Hope this will be delivered on the last version.

Sure you can do that. I've done exactly that myself. There would be a few things to consider when importing the config. The interface names will be different, em* in VB and igb* on the 2440. When you import the config in the GUI is should ask you to re-assign the interfaces at that point but you should be sure to have console access to the 2440 in case there is still an interface mismatch and it asks you there. The VB install will almost certainly not have a serial console by default. That should be overridden when you import it to the 2440 but you might want to enable dual consoles in System > Advanced > Admin Access tab. You should always enable PowerD on an SG-2440 config to get the full CPU speed in System > Advanced > Miscellaneous tab. That obviously doesn't do much in VB. However restoring a config is pretty easy using the ECL: https://www.netgate.com/docs/pfsense/backup/automatically-restore-during-install.html?highlight=ecl#external-configuration-locator-ecl If you manage to break the config sufficiently on the 2440 you can always restore a backup by simply rebooting with a USB stick containing it attached. Steve

If I was hitting that I would install 2.3.5 onto a new CF card and then restore the config from the old install. That is by far the safest thing to do there. You will still have the old card to boot into if required. When the update system reports Theres already an update running it means there's a pkg update running not an upgrade necessarily. So you probably had the dashboard open for example. You should consider swapping out th ALIX (I'm guessing) for something newer though. End of all support for that is coming soon. Steve

Thank you jahonix. I really do appreciate it.

@stephenw10 Good to know, thanks. But I've already bought the cables, and I'm trying to reset it right now.

@mats said in Problem with upgrade from 2.3.5 to 2.4.3: Thanks, It almost fixed my problem too. I had to do a reboot after these steps and run an updte from the console followed by a final reboot but now it works Tried this but it did not work for me. Ended up reinstalling from scratch to fix the botched upgrade.

@xero9 said in Upgraded from 2.4.3 -> 2.4.3_1. IPv6 problems: .... Will report back if I have any more issues! Maybe this one : The latest upgrade ( 2.4.3-RELEASE-p1 ) came out about 2 month ago. Better check out why you discovered this only yesterday.

@jimp I tried with 2.4.3. it give me two option for installation. I faced same issue of bootup complete.

@jahonix See my post with the steps we took. We did essentially what you did, but we also removed any references to the wan interface before we did the find-and-replace. Perhaps the cycling of OPT* interfaces was unnecessary, but it help us with consistent organization (since we have almost 2 dozen interfaces, organization is essential).

Edit : the problem is a console problem on bhyve. In fact pfSens boots correctly, but the console from vm-bhyve hangs. I had to dig my network in order to find that the LAN interface had the default setup which was (surprising !) 192.168.1.1. Just set my Laptop's interface to that network and voilà, I was able to configure the router with the correct IPs. More question to come in an other section of the forum. Cheers Xavier

@trumee said in ZFS feature set 2.4.4 vs 2.4.3: The pool can still be used, but some features are unavailable # zpool get all zroot | grep feature@ and then check for which ones are "disabled" discussion: https://forums.freenas.org/index.php?threads/zpool-features.18651/

I was able to perform the update to 2.4.3_1 Seems it was a DNS setting. Once I corrected this setting pfsense saw the latest update. -Gary

You're welcome. Glad I could assist.

NAT issue? As well was firewall rule(s), you'll need NAT for your VLAN 50 Incidentally, running a DHCP server on the Unifi box for VLAN 50 doesn't work very well - make sure you're running DHCP server for the VLAN on the pfSense box

@rbrtpfsense No you should not be concerned. This only indicates that you have not turned it on (Active) If you use EAS-NI crypto engine in your ipsec, then switch it on if needed. It's informative status of cryptoengine usage.

@johnpoz said in Ssh changes in 2.3.2 ?: Not sure exactly what your looking for - but here is a blog post by the person that brought chacha20 to openssh and has some reasons why he did so, etc. http://blog.djm.net.au/2013/11/chacha20-and-poly1305-in-openssh.html Thanks @johnpoz good article. I hadn't heard of these before. There was a post that listed which algos were best/safe for OpenSSH-can't remember what else. Something with general best parctices would be helpful.

Honestly, I don't know how to do anything with a blown up sbin. Some things might work, some not. The best answer is "don't do that." The file you want is /cf/conf/config.xml.

Does that happen for any log file, or only the system log file? Have you changed any log settings such as the log file size or the number of lines displayed in the firewall GUI? Go straight to the log settings page, /status_logs_settings.php, and check.