Just run a backup from your physical box (Diagnostics\Backup/Restore), edit the config file to allow for the possibly different NIC device IDs and import into a fresh install on your VM environment. So yeah, it's an OK idea.

The stack trace is entirely unhelpful! But maybe you are hitting a divide-by-zero problem that is fixed by: https://github.com/pfsense/pfsense/commit/883777874d3064fc9730a0d7e870bf0bc991ae0c and https://github.com/pfsense/pfsense/commit/6f069e921c0a2aabe66ee069c20148b4fcbb0918 Try putting the latest status_queues.php on your system. Or even update to 2.3.1-DEVELOPMENT to get all the good stuff that has been fixed since 2.3-RELEASE.

Hi again! :-) I enabled a tunnel, but the connection did not come up, although the other side is online, too… Dunno why the tunnel does not connect, was functional in 2.1.x, but disabled since then. On the 2.2.6 pFsense I have in the log: charon: 08[IKE] <con2000|1>sending retransmit 5 of request message ID 0, seq 3 Debugging IPsec is no fun…. What is this widget-thing? I didn't install anything!</con2000|1>

And you should be able to use the auto-update from the dashboard - it will find the correct "factory" upgrade image for it and do its thing automagically.

Thanks a lot.  8)

Deleting the following files and then reinstalling haproxy-devel worked for me: /usr/local/pkg/haproxy.inc /usr/local/pkg/haproxy_htmllist.inc /usr/local/pkg/haproxy_rules.inc /usr/local/pkg/haproxy_socketinfo.inc /usr/local/pkg/haproxy_upgrade_config.inc /usr/local/pkg/haproxy_utils.inc /usr/local/pkg/haproxy_xmlrpcsyncclient.inc /usr/local/pkg/pkg_haproxy_tabs.inc I left the following files intact: /usr/local/pkg/haproxy.xml /usr/local/pkg/haproxy_rules.inc

A reinstall worked, I also decided its time to retire my aging fit-pc and ordered an SG-2440.

Actually the hardware was purchased in 2008. I've considered upgrading several times (e.g. to 5.0 and 5.5) but decided not to due to performance of the migration utility (VMware Converter). For 5.x it's much slower compared to 4.x. And also, we still use Windows XP, where newer versions of the host control utility (VMware vSphere client) doesn't seem to run smoothly.

You could make the change on 1000's of machines in a few seconds be it group policy if they are member of AD.. Or simple push of reg edit from cmd line.. if you have account that has permissions on the machines… Saying you have lots of machines so too much work to make a change on them seems odd... https://blogs.technet.microsoft.com/heyscriptingguy/2012/03/17/edit-the-registry-on-multiple-remote-computers-with-powershell/

Standard logs are circular and when you're talking about hundreds of gigabytes it is insignificant.

One thing off the top that dnsmasq can do that unbound can not is do localized responses..  Not aware that unbound can do that?  Pretty sure dnsmasq will send queries to all dns servers listed and use the fasted response.  I believe the way unbound does it is sequential? As cmb states there are differences in for sure.. dnsmasq is by design a forwarder, while out of the box unbound is meant to be a resolver while it can be put in forwarder mode that is not where it shines so having both available for sure makes better choices for pfsense.  Now if they had an authoritative dns that would be the homerun like bind..

@nima: A system mail would be nice if a system or package update is available. Hello. It can be done simply with php: Notifier package & platform updates via email. https://www.javcasta.com/bounties/#notifier_package_plarform Regards.

Thank you for all those that helped.  Everything solved and able to access securely while going thru some 'stuff'.    Family reports no issues with their side.

This issue has little to do with installing or upgrading PFSense. It'll probably get moved, but next time you may want to post in a proper forum.

Thanks mate, worked perfect.

Please can you help me with a default original config file and the steps to replace to remove and replace the config file. Please help me

Hi, I upgraded from the version before, which I dont know ;) (I always use the newest version..) There`s no error, only the normal message: "The WLAN configuration has been changed. The changes must be applied to take effect. Don't forget to adjust the DHCP Server range if needed after applying." [image: 2016-05-06_08h21_22.png] [image: 2016-05-06_08h21_22.png_thumb] [image: 2016-05-06_08h21_41.png] [image: 2016-05-06_08h21_41.png_thumb] [image: 2016-05-06_08h22_25.png] [image: 2016-05-06_08h22_25.png_thumb] [image: 2016-05-06_08h22_32.png] [image: 2016-05-06_08h22_32.png_thumb] [image: 2016-05-06_08h22_51.png] [image: 2016-05-06_08h22_51.png_thumb]

I mis-read the bug ticket for this issue, it wasn't actually fixed. https://redmine.pfsense.org/issues/6229 What output do you get for command: grep pfb_interval /cf/conf/config.xml