Beta 26.07 26.07.b.20260702.2342

netblues

Upgraded from 26.03.1 "dirty" i.e. without removing anything

frr, pfblockerng, openvpm, wireguard included.

Two, plus one minor glitches

If upgrading via web interface and ram disk is in place, it takes much more time to save ramdisk and reboot, after completing the upgrade, so web interface goes back to login (but its still in 26.03 since reboot hasn't happened yet.
If the user starts looking at things especially packages, bad things might happen.
One has to wait

Second glitch is that after upgrade wireguard doesn't seem to work.
Service won't start, and connectivity doesn't happen.
Doing a second reboot fixes everything and never happens again.
This was also the case on 26.03 rc and betas.
Minor, but still can create havoc trying to debug.

And last, if a non standard mtu is used in openvpn server., a message will appear on every reboot asking to put the same value on the openvpn interface (even when it is there).

Didn't notice anything else yet, but its kinda early.

sgw

I also was curious and did a dirty upgrade to 26.07.b.20260702.2342 on a SG1100 hardware.

For me wireguard was up immediately after first boot.

Did the upgrade via ssh. No glitches so far but it's only a few minutes since the box came up again.

stephenw10

Interesting. The 1100 is usually the worst case for upgrades because of the RAM limit.

@netblues What hardware did you test on?

netblues

@stephenw10 redhat 9 under kvm q35 hardware, bios. 8g ram

Hardware is an HP EliteDesk 800 G5 SFF i7.

Router on a stick , around a 10g mellanox x3.

sgw

@stephenw10 said in Beta 26.07 26.07.b.20260702.2342:

Interesting. The 1100 is usually the worst case for upgrades because of the RAM limit.

So far everything OK.

marcosm

Would you share screenshots of the message and the related config?

netblues

@marcosm To which message are you refering? Notice about openvpn mtu on every reboot?

marcosm

@netblues Yes,

netblues

@marcosm

and

A notice message appears after every reboot.

(I need to reboot to see it)

marcosm

Thank you. I've posted a fix here:
https://redmine.pfsense.org/issues/16938

netblues

@marcosm said in Beta 26.07 26.07.b.20260702.2342:

https://redmine.pfsense.org/issues/16938

Yes, confirmed fixed in 27.07 beta.

netblues

said in Beta 26.07 26.07.b.20260702.2342:

@marcosm said in Beta 26.07 26.07.b.20260702.2342:

https://redmine.pfsense.org/issues/16938

Yes, confirmed fixed in 27.07 beta.

26.07 obviously. :)