@maddy_in65 said in Connectivity issues after reinstall: 5260 unbound 82 0 154M 147M RUN 0 0:04 31.40% /usr/local/sbin/unbound-control -c /var/unbound/unbound.conf stats_noreset 6240 unbound 80 0 126M 120M CPU1 1 0:03 26.27% /usr/local/sbin/unbound-control -c /var/unbound/unbound.conf stats_noreset Two instances of unbound - the same process, that's a bad sign. unbound was asked to show stats without resetting them. Takes a milli second on my system, as it just spits out some variables. Yours blocks doing that, stays in memory, eating up resources. That's not normal at all. I advise you to ditch packages right away. And be sure your settings are default - especially the DNS ones. Then, ok to change settings, but look closely and a long time to system behaviour between changes.

Indeed there is no auto-update for firmware in pfSense. The only thing that does is the pfSense-upgrade and pkg packages in order to show you an updated repo list. That might happen if you open dashboard and have the firmware check enable. It will still just offer the upgrade though, it doesn't do anything until you click it. And, yes you can install as ZFS currently if you want. Steve

For me it stopped after it terminated all processes after upgrade, as in it should have rebooted after but didn't and was stuck in limbo for like an hour. I simply restarted it manually it was fine afterwards.

Same problem here, I fixed it by enabling the "state table size" option which was previously disabled before the upgrade.

Yes, it's fine to upgrade.

go to system > update and select correct branch in your case "Next stable version (2.5.0 RC)"

were you ever able to get this going ? I am having the exact same issue

Tune in here https://forum.netgate.com/topic/160845/pfsense-2-4-5-package-vulnerabilities?_=1613396520399

Yes, nothing fundamental has changed there since that was written

Mmm, you need a serial console on it to use a laptop. Otherwise you need a keyboard/monitor.

@gertjan Definitely. @gertjan said in Cannot update anymore: is packages-beta.netgate.com host deleted ?: So, special case : DNS issue, yes, but not on your - or my - side ;) Definitely. We can't fix that. We could manually add an entry host = ip if we'd know the corresponding ip. It's strange to make a so big change (or mistake?) for a company which the purpose is the security !?

@thedaveca said in 2.5.0.a.20210126.2350 unbound keeps stopping after upgrade: nothing implies any need to shut down the service Check out the history of this box checked on this forum. Hundreds of posts (issues) will argue that it's close to 'mandatory'. No service will get shut down. But DHCP clients that do not have a static MAC lease won't get their device name registered (if they even have one) into the DNS. And unbound will thank you for that. That is, this was the "2.4.5-p1" solution. Recently, I found out that, with 2.5.0 , which is using a newer unbound versionit will get hupped (send a signal called HUP) : and that it behaves diffreently. It shouldn't restart any more on DHCP events. So up to you to discover the reason. The answers will be / should be in the logs.

@jimp Thank you for explaining

@gertjan i had dns in dhcp,anyways enabling the dns resolver(in dns resolver page) in the pfsense interface got pfsense working,thanks. how do i set it to ping to cloudflare though than my isp's dns,do i put the cloudflare ip in the general setup dns box ? will putting it in the general setup dns box on general setup page also make my dhcp clients resolve to that(which i dont want). Thank you for the help. "Also, not related : these "old wifi router in apmode/switch" have often 100 Mbits/sec interfaces, limiting your (local) network speed." all my ethernet devices are on the gigabit switch.Buying a gigabit wifi router soon. also can you please look at my other post link text i want to force my local lan traffic through a proxy server running on a vm on the same lan/subnet but nat does not seem to work.

Probably a bad disc or a problem with the CD drive. The ISO itself is fine.

@gertjan Hey THanks for the tip! It worked!! Never thought of generating and APP password... My not-so-smart 'smart' devices like NVR and IP cams were able to use the regular Gmail password. BTW you have to turn on Two Factor Authentication to allow the app password generator function to work.. Thanks again!

If you were using pfSense on a bare-metal device, you wouldn't see any issues. @bahman said in error occur under startup: qemu So this concerns "VM" or "Virtualisation" => see here Home > pfSense Software > Virtualization as this is not an installation problem, pfSEnse or the software that boots / installs pfSense doesn't get even the chance to start. The messages shown are from the VM host. I tend to say : a qemu problem.