pfSense Plus Software Version 24.11 is here!

marcosm

@FollyDude-0 said in pfSense Plus Software Version 24.11 is here!:

@mwatch

Installed on SG-6100 went OK. The only issue I see at this time is that the dashboard System Services Status widget is showing Wireguard as down.

I have checked the Wireguard connection and it looks OK, it is connected. I have tried a reboot (also tried a cold start) and no change. I have tried starting Wireguard from the widget play button. So it looks like the widget has an issue, not wireguard itself.

Cheers

Steve

Create a new thread if you're still seeing the issue. For reference, the status looks for the process name stored in the config. You can test this by running pgrep php_wg - if it's running, you should see e.g. 40125.

stephenw10

@Cylosoft Yes the logging options in Kea are limited right now. This was better than the default 'flood'! More options coming.

michmoor

@stephenw10
BTW....That nice feeling i get when MIM is faster than going through the pfsense GUI
You guys did a great job here with the responsiveness. So far I'm making changes that way as its more performant i find and that's on a SG1100

tman222

I went ahead and upgraded to 24.11 yesterday and overall things went fairly smoothly. Ran into a few issues along the way, some of which have already been documented in other posts:

Higher CPU usage when viewing dashboard:

https://forum.netgate.com/topic/190824/cpu-load-on-1100

“Another instance of pfSense-upgrade is running” - saw this as well when when I first tried to upgrade. Error went away after waiting a couple minutes:

https://forum.netgate.com/topic/195329/huh-another-instance-of-pfsense-upgrade-is-running

FreeRadius BlastRADIUS warnings in the System Logs - not sure yet how to mitigate these; have started a thread:

https://forum.netgate.com/topic/195376/freeradius-blastradius-warning-in-system-logs-how-to-mitigate

Abnormally high SERVFAIL messages from DNS look ups after upgrading - these were high enough that websites would regularly fail to load. I'm still investigating the cause as everything worked fine in pfSense 24.03 and prior versions. I do see that unbound was upgraded from 1.19.3 to 1.22.0 so perhaps some changes were made that resulted in this behavior. For now the workaround that has helped to get rid of the excessive SERVFAIL errors, has been to explicitly disable IPv6 in unbound by setting do-ip6 to no in the Custom options section (I don't currently use IPv6 so this should not cause any issues). However, more investigation will be needed.

Overall though this has been a great release - thanks Netgate team for all your hard work!

tgl

@mwatch Updated a 4200 to this release about six hours ago. Saw the same “Another instance of pfSense-upgrade is running” strangeness others have reported, though that clearly must be the fault of the prior release (24.03) not this one. Otherwise, smooth upgrade and no problems noted since then. The dashboard widgets fill in noticeably more quickly than in 24.03. I don't see any indication of increased CPU load, although I use a fairly minimal set of widgets.

SteveITS

@SwissSteph ignore the countdown timer. Upgrades take from a few minutes to 10-15 minutes or so depending on disk write speed and CPU power, and whether one removes packages first (per the upgrade guide).

After a half hour if you still see the timer, connect a console cable, do not just power off.

SwissSteph

@SteveITS
Thank you for this message and your advice, I'll keep it to the letter. For me and this new version everything went very well.
I also got the message “Another instance of pfSense-upgrade is running”, I rebooted pfsense and the message was no longer present)

I also switched to “KEA”, thanks to your encouragement ... all OK for me

delphin_007

I already posted not starting Squid/SquidGuard-services. Tried many ways to repair - all failed. Same picture at my 4100 and 6100. So I killed and deinstalled both programs. RIP - shame. I "cleaned" the 4100 from all programs and functions I could find failiure messages about.

Both devices show significantly higher CPU-load when using GUI than I have ever seen before. Value fluctuates strongly and often reaches 100% - even with only small dataflows through the device. Monitoring graph of temperature over 2 day shows normal values.
No packet loss is documented.
May be the CPU-load is only high while using the GUI ? 2-days graph does not show problems ... but it is propably not able to register quick fluctuation.

I hope that 100%-CPU-load phases do not shorten the CPUs lifetime or leads to other problems I did not notice yet...

SteveITS

@delphin_007 re: CPU, there are a few threads on that. Check with the dashboard not visible, or see https://forum.netgate.com/topic/195325/sg2100-100-cpu-usage-post-upgrade-to-24-11/7.

delphin_007

@SteveITS Thanks for hints ! I looked over other threads.
So I leave it as "GUI-behavior".
As long as there are no problems at my Netgates I use GUI dayly only for seconds to get the "OK"-impression.

markster

One issue is that after WAN IP renew (which works) the KEA DHCP service stopped and I had to start it up manually.

mkowalski

Has anyone else had issues editing or adding domain overrides in dnsmasq in 24.11? I can add hosts and update custom options but domains don't update.

stephenw10

Yes, replicated that. https://redmine.pfsense.org/issues/15890

4o4rh

Upgraded fine, but on first boot, the boot environment failed to verify and reverted to 23.04. Manually triggered a reboot and still had issues. but booted one more time and then it was fine.

DutchBoy

I upgraded my 2100 to 24.11 without any problems.

Then I gave KEA dhcp server another try, but just like in the previous release, still no custom dhcp option possible. At least, I don't see the config option in the gui.

I switched back to the ISC backend.

stephenw10

Yup custom options are coming....

Jax

Questions:

My 2100 is not flashing the amber lights it usually does when an upgrade is waiting, thought the upgrade does show available in the web interface. Is this a concern?
I wonder if I missed some upgrade steps along the way. Is it normal to jump from 24.03-RELEASE (arm64) to 24.11?

Thank you.

stephenw10

The update LED is a known bug. It's fixed now: https://redmine.pfsense.org/issues/15880

Yes, 24.11 is the next version after 24.03.

wgstarks

@Jax said in pfSense Plus Software Version 24.11 is here!:

Questions:

I wonder if I missed some upgrade steps along the way. Is it normal to jump from 24.03-RELEASE (arm64) to 24.11?

Thank you.

The 24.11 just represents the year and month of the release. Releases aren’t sequential.

Jax

Thank you @stephenw10 & @wgstarks .