Now Available: pfSense CE 2.9.0 Release
-
@LHoust I was corrected, sorry, you have to ssh into pfsense, and do a
nano /boot/loader.conf.local
and put your command there, do a ctrl O for saving it, after you place the command into /boot/loader.conf.local
-
said in Now Available: pfSense CE 2.9.0 Release:
@SteveITS said in Now Available: pfSense CE 2.9.0 Release:
@LHoust Did you set https://docs.netgate.com/pfsense/en/latest/releases/2-9-0.html#hardware-errata ?
I tried creating a System Tunable as hint.acpi_spmc.0.disabled=1, although through what I observed today, that was unable to create /boot/loader.conf.local, (unless I manually create that file and add that entry myself)!!!
What am I missing here???
Sorry my question was NOT worded very well, actually I what I wanted to ask was:
What am I missing here: In terms of how have hint.acpi_spmc.0.disabled=1 included within a Saved CE 2.9.0 Config, such that I would NOT have to manually create that /boot/loader.conf.local Entry after Restoring a CE 2.9.0 Config???
Given my addition of a System Tunable Entry, did NOT work...
-
@LHoust I'm not sure there is a way to save/restore that file...? Maybe use the cron package and have it create that file at boot, which is after boot but at least it's created. How fast does it die?
-
@SteveITS said in Now Available: pfSense CE 2.9.0 Release:
@LHoust I'm not sure there is a way to save/restore that file...? Maybe use the cron package and have it create that file at boot, which is after boot but at least it's created. How fast does it die?
There is a way to do it properly by simply using the "filer" package. Just let filer create
/boot/loader.conf.localwith your entries and filer will make sure the file with entered permission mask and content as described is created. For a new install, that would need a second reboot after the install, as after the first boot after installing the file isn't there, your config would then make all packages reinstall including filer and that would bring back the loader.conf.local managed therein. That's the downside, but managing it that way is far simpler/easier then throwing some cron job at it and you've documented your file content that way in your config.xml.Cheers
-
@JeGr Logged in to pfsense with root access,.. did a
dmesg | grep CPU CPU: Intel(R) Celeron(R) CPU J3160 @ 1.60GHz (1600.15-MHz K8-class CPU) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUsconfirmed celeron J cpu, Followed Instructions to create
/boot/loader.conf.localconfirmed file presence with
[2.8.1-RELEASE][admin@pfSense.mylocal]/root: cat /boot/loader.conf.local hint.acpi_spmc.0.disabled=1Started Upgrade process,.. which took approx. 15 mins... all completed fine,.. and finished with login prompt
Question to devs. do I need to keep maintain this 'fix/fudge', whilst maintaining this hardware?
Thankyou to community for a trouble free update.. -
@tb404 Good to hear your upgrade went well on APU2.
I always had issues in the past where I had to upgrade the firmware first. Except now I'm wary because there's no new firmware since 2023 (4.19.0.1).
-
@Dacmot said in Now Available: pfSense CE 2.9.0 Release:
there's no new firmware since 2023 (4.19.0.1)
Slight correction, there is no free upgrade anymore. You can get paid support/firmware from 3mdeb (https://docs.dasharo.com/variants/pc_engines/overview/).
-
Hi, thanks for this new release. I upgraded and almost everything went fine. One issue I encountered is that my Virtual IP adresses I use for pfBlocker DNSBL are gone after the upgrade to 2.9.0 (also in de pfblocker DNSBL config section) It was easy to reconfigure the VIP adresses again and select them in de pfBlocker DNSBL config section (after running DNSBL update everything was up & running again)
-
@matthijs said in Now Available: pfSense CE 2.9.0 Release:
Virtual IP adresses I use for pfBlocker DNSBL are gone after the upgrade
This is "expected"...IIRC, the new behavior is the package doesn't create it automatically. So if upgraded it is kept but if uninstalled and reinstalled it needs to be created.
A year or so ago this changed for Plus so CE is catching up.
-
Since i updated to CE 2.9.0 a few days ago my router did reset out of nowhere random 3 times already. Just now a few minutes ago it did it again. Before i never had this update. I never changed anything in the config only updated it.
I looked in my logs but could not find anything that could result in this random reboot. Its 2 time in about 30 hours timespan.
Privacy Policy · Cookie Policy