pfSense Plus Software Version 23.09 BETA Now Available for Testing
-
If you send me the NDI from that VM in chat I can check what it should be seeing.
-
@mikebenna 23.09.b.20231015.0519 is available now.
-
So far everything has been very smooth. I installed the 3rd 23.09 beta this morning.
-
Major packages:
Snort, pfBlockerNG, HA Proxy, and ntop. No issues whatsoever. Nice work.
-
Pulled the update tigger this morning.
Initially the GUI said "Unable to check for updates" wait a bit, nothing
so I switched back to 23.05.1 branch and it said the same "unable to check"Logged out, and back in, check again with 23.05.1 and reports current with no update
re-selected 23.09 beta - again reports "Unable to check for update"
logged out and back in with 23.09 Beta branch selected and immediately saw the 23.09 beta availableSeems like this could be a page refresh issue and nothing more, in this case
Confirmed and Updated just fine. 23.09.b.20231016.0231
All packages running as expected.
I even had two patches (of my own creation) for pfBlockerNG (for which the Auto Apply was checked just before running the update) and they both survived
the Auto Created boot environment for "default" is reporting about 2GB more under space column as compared to what "default" was before. (previous read 3.4G and the current default reads 5.24G (no issue just an observation)
-
@jrey said in pfSense Plus Software Version 23.09 BETA Now Available for Testing:
the Auto Created boot environment for "default" is reporting about 2GB more under space column as compared to what "default" was before. (previous read 3.4G and the current default reads 5.24G (no issue just an observation)
This is typical with any boot environment since it's technically just pointers to the same installed packages - just the config diffs are what's different. If you delete the old boot config, you will reclaim the 2GB+ of space.
-
No issue - just and observation ;-)
I have all my previous boot environments going back to 22.05 and the mention was only because this was by far the single largest increase in "default" from one version to the next -also the memory footprint has changed significantly from what was "normal" on 23.05.1 -- again no issue, just an observation
-
That memory should eventually be freed but you should also be able reboot again to free it. The upgrading process itself uses significant memory.
-
Hmm... my slave VM was happy running the beta over the weekend. This morning I upgraded my master VM and it crashed 3 times immediately after the upgrade. It was happy for 30min or so, then I did another reboot to see what happened and boom... crashing again during startup... once, twice, three, four times. I may simply revert. Oh wait, fifth reboot succeeded! I'll leave it here for now. :)
Looks like a page fault right around the time of bringing up a Wireguard tunnel.
Slave is running a similar Wireguard config but has never crashed.
How can I be of further assistance?
-
Better to open a thread in the 23.09 sub to troubleshoot problems: https://forum.netgate.com/category/92/plus-23-09-development-snapshots
Steve
-
@stephenw10 said in pfSense Plus Software Version 23.09 BETA Now Available for Testing:
eventually be freed
so just to close the loop on this observation, about 2 hours later I noticed that the Active and Inactive values had reverted (actually just about switched positions (crossed) from where they are shown on graph above and therefore more in line with their pre-update lines.
The value for the cache never cleared and after about 3 hours (so an hour after the other values corrected) I just let it run but "eventually" I just rebooted to flush whatever had been cached during the update.
clearly 3+ hours is not enough time to be considered eventually.
All values now trending very near pre-update values.
Still not an issue, just an observation. Have a great evening. -
@jrey said in pfSense Plus Software Version 23.09 BETA Now Available for Testing:
@stephenw10 said in pfSense Plus Software Version 23.09 BETA Now Available for Testing:
eventually be freed
so just to close the loop on this observation, about 2 hours later I noticed that the Active and Inactive values had reverted (actually just about switched positions (crossed) from where they are shown on graph above and therefore more in line with their pre-update lines.
The value for the cache never cleared and after about 3 hours (so an hour after the other values corrected) I just let it run but "eventually" I just rebooted to flush whatever had been cached during the update.
clearly 3+ hours is not enough time to be considered eventually.
All values now trending very near pre-update values.
Still not an issue, just an observation. Have a great evening.After each OS update, even a minor one, I usually let it reboot post-install, make sure all packages are up-to-date, clear most of the logs, delete the old boot environment if things looks smooth, and reboot once more manually just to start clean after post-processing. That way the system comes up in a normal state with clean resources. This has worked well for me.
-
I tested 23.09 beta on my Intel NUT where is runnin 23.05. It has several problems and I had to reload 23.05 on boot enviroment. It loads slower then 23.05, mostly I had 502 Bad Gateway when I tried access GUI. Freeradius doesnt work properly and I also do not have internet connection even if all packages were running in System/Services . Dont know why this happen, but on 23.05 is everything working fine again.
-
Open a thread in the 23.09 sub with any details you have: https://forum.netgate.com/category/92/plus-23-09-development-snapshots
-
Hello, I am currently validating a Dell server for the purpose of installing pfSense+. With version 23.05.1 for home/lab use, there was a regression issue related to Broadcom BNXT drivers. After updating to version 23.08, this driver issue has been resolved. However, I encountered a problem when trying to import a configuration from version 23.05 using the 'Diagnostics Backup & Restore' page and the 'Restore Configuration' button; clicking the button had no effect.
-
@philippe-richard
Hello, I'm responding to myself. It seems that I had a browser issue earlier, as I just tried again and successfully imported the configuration file. I apologize for any inconvenience this may have caused -
@stephenw10 said in pfSense Plus Software Version 23.09 BETA Now Available for Testing:
If you send me the NDI from that VM in chat I can check what it should be seeing.
Hello Stephen, can you give advise what to do if I have several pfsenses on proxmox, all for personal use but also not in a final configuration. Is it better to keep them on CE or can I get a token every time one is "needed" again...? Will I get "listed" by netgate?
-
There is a rate limit on the tokens to stop someone scripting something to just pull 1000 tokens in one go! But if you are just registering one new host a day for example I doubt you would ever come close to it.
-
System unpinned this topic on
-
@stephenw10 said in pfSense Plus Software Version 23.09 BETA Now Available for Testing:
Open a thread in the 23.09 sub with any details you have: https://forum.netgate.com/category/92/plus-23-09-development-snapshots
I think, that I know what happen now. It was because I use Freeradius for connection. After upgrade, also package was upgraded, but configuration dissapiered! I wasnt able to connect, so I thought that it is broken. I will try again, because I just upgrade package and lost config and wasnt able to login. So now it should be fixed and I assume that also upgrade will be OK.
I think the issue regarding loosing configuration of Freeradius after last package upgrade can cause big issues to others. I use it also for VPN, so I lost access on affected device. I know it is out of this topic. Sorry :)
-
@GeorgeCZ58 said in pfSense Plus Software Version 23.09 BETA Now Available for Testing:
Freeradius after last package upgrade can cause big issues to others
An issue that is known for a couple of weeks now.
People started to discover what happens when this Services > FreeRADIUS > Settings isn't set.
and this one is even nastier : there was a bug in FreeRadius itself.
And when you upgrade pfSense, it will re install packages that are found when rebooting after pfSense after the upgrade (common advise is/was : remove packages before pfSense upgrading - but I admit : I'm not doing that neither).At the end you were protected by the last safely net : before upgrading pfSense, take config backups, right after the pre pfSense reboot (the manual reboot before the upgrade).
See Upgrade of FreeRadius3 from 0.15.10 to 0.15.10_1 sets all configuration values to default. in the pfSense Package forum (third thread).
