pfSense Plus Software Version 24.11 is here!

keyser

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

Going to try out KEA DHCP now.....
The switch to KEA DHCP has so far introduced no issues other than it starts handing new leases out (with no prior lease on record) - meaning clients will change their IP address at next renewal.
I dunno if it will cause IP conflicts down the line with new clients getting IPs from still working ISC leases belonging to continuously active clients.

But it upgraded with all settings kept - including static leases.

I enabled Dynamic DNS and Early Dynamic DNS registration. Seems to works quite flawless this far :-)

keyser

@keyser I seem to no longer be able to edit my replies in this forum.... a little annoying with "quote" error in my last response

keyser

Upgraded the first of many 2100's and it went flawlessly albeit it does take some time :-)

Like my 6100 it upgraded with pfBlockerNG, Freeradius, NUT, TFTP, LLDP packages running - all without issues.

I also moved to KEA DHCP4 backend after the upgrade, end experienced no problems on this box either. Seems like an overall good upgrade package. Let's see how it behaves the coming weeks.

markster

Upgraded 5100 without issues.

Packages running include avahi, ntpd and nut. Switched to KEA DHCP no issues. Run external Unbound DNS on docker synology.
No issues experienced.
Great update. Thank you team.

coxhaus

@mwatch I put on 24.11-RC version a couple of days ago and everything was working great. So, this morning it said 24.11 was available and I thought it should work great since the RC is running so well. I upgraded and my Dell PC no longer worked. I could not ping my LAN interface. I assumed my license expired but it did not warn me. So, I pulled the NIC and installed it in an older Dell PC using 2.7.2

joedan

Upgraded my custom box yesterday without drama and immediatly switched to using Kea.

(Intel i5-8365U CPU @ 1.60GHz / 16GB memory / 2.5Gb igc)

No issues at all, noticed slight connection improvements showing up on the monitoring graphs.

I looked back to my monthly data and a previous reboot just over a week ago made no difference so something changed for the better in this upgrade for me.

JonathanLee

@delphin_007 has this issue resolved ?

SwissSteph

Update carried out on my 8200, just a little scared because it took pkusieurs perides of “20 seconds” more for me to get the login page again.

All's well for now.

THANK YOU to all the team and happy new year!!!!

SwissSteph

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

Update carried out on my 8200, just a little scared because it took pkusieurs perides of “20 seconds” more for me to get the login page again.

All's well for now.

THANK YOU to all the team and happy new year!!!!

Update carried out on my 8200, just a little scared because it took several periods of “20 seconds” longer for me to get the login page again.

All's well for now.

THANK YOU to the whole team and happy new year! !!!

Modified my text for a better translation (sorry)

And a question, can we switch to “KEA” having “pfBbockerNG” trasparently or do we have to wait for a “tuto”!? Thanks again!

keyser

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

And a question, can we switch to “KEA” having “pfBbockerNG” trasparently or do we have to wait for a “tuto”!? Thanks again!

I have switched to KEA after 24.11 on alll my boxes without any issues. All of them runs pfBlockerNG so no tutorial needed - I just switched and have not done any additional config apart from enabling dynamic DNS registration.

Cylosoft

Am I just missing it or do the DHCP logs not show IP/MAC on IP registrations when you switch to Kea on 24.11?

SwissSteph

@keyser

Thank you for your message and confirmation that “everything should go smoothly”.

Gertjan

Upgraded to 24.11 from 24.03.
Selected in the GUI, System > Update > System Update : "24.11".
Then, from the console, as the views is so much better, option 13.

Better take a drink while you sit this one out, I thought.
When I came back search for one, everything was already downloaded and installing was well underway.
Love the small detail : while all this was going one, the Internet connection was just fine.

After the install, the system rebooted into the new "Boot environment" : no issues at all.
De reboot took slightly longer as usual as I didn't bother removing packages before upgrading.
A couple of seconds more, and there was the console menu.

Re connected to the GUI, and everything was as before.

Even connected portal users were still there ...
Less then 60 seconds down time.

I tested the OpenVPN server access (for my own personal remote admining ) : worked fine.
FreeRadius ; all ok.
pfBlockerng : still blocking.

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