2.8.0-BETA snapshots are now available

chpalmer

Mostly successful upgrade for my Watchguard XTM5 "test box"

Anything unsuccessful was self inflicted.. ;) Make sure you have access to the box in case your Wireguard instance does not come up should you be using one.. (luckily mine is in the same rack as my primary box.)

;)

patient0

Did an upgrade of a VM on Proxmox from CE 2.7.2 with UEFI with a root disk of only 6GB of which 3.2GB where free before the upgrade. And it when smooth.

I actually did it twice, once with a serial port device and once without. Upgrade worked with both configurations.

netblues

@patient0 proxmox seems to use legacy virtio and works.
Redhat and derivatives seem to be different

patient0

@netblues said in 2.8.0-BETA snapshots are now available:

@patient0 proxmox seems to use legacy virtio and works.
Redhat and derivatives seem to be different

You are right, I do follow your thread about the issue you got.

Just wanted to give feedback of a situation where it does work.

Popolou

You guys at Netgate do like flying close to the sun what with the mini-fits caused by last year's April Fools

nimrod

@Popolou

All future ce releases should target April 1st as a release date. I just love Netgate trolling. The amount of salty comments afterwards is just amazing.

Popolou

I suppose it's only fair, we troll them and they gaslight us in return

fireodo

@patient0 said in 2.8.0-BETA snapshots are now available:

I actually did it twice, once with a serial port device and once without. Upgrade worked with both configurations.

Can you say something about the dashboard cpu load? Is that better now?

stephenw10

2.8 is branched at the same point as 25.03 so it should have the same improvements that does. Of course it will be harder to see because 2.7.2 still used the old refresh method.

fireodo

@stephenw10 said in 2.8.0-BETA snapshots are now available:

2.8 is branched at the same point as 25.03 so it should have the same improvements that does. Of course it will be harder to see because 2.7.2 still used the old refresh method.

Thanks. On my Lab machine (APU2C0) under 24.11 the problem still persists despite of all patches ... :-(

LHoust

After using the RC1 Network Installer with my Zimaboard 432 (Dual 10Gtek NIC), I had to reassign the WAN Interface: Following the reboot, the WAN had been re-assigned to an Onboard Realtek NIC.

On the First Restore of my 2.7.2 Config, there were NO Packages Available and the BETA had rebuild its list of Packages. For the Second attempt: All Packages were Available and those which my Config Required, were successfully Downloaded in the Background...

Although it has only been couple of days, so far I had NOT Noticed any Problems with this BETA running my 2.7.2 Config???

stephenw10

Hmm, so at first boot after a clean install the WAN had been auto-assigned to re0? Was the LAN also assigned to re1?

LHoust

Actually LAN was still assigned to igb1.

All of which I found a bit "Strange", since igb0 had just been used to complete the Network Installation before the reboot!

mikey_s

Just upgraded a spare XG 230 Rev2 from pfsense 2.7.2 to version 2.8. Will have a further look in due course. It's a generic install that has been upgraded.

One observation, QAT is now list in the drop down list for Cryptographic Hardware under advanced settings? Was this added? I have other hardware with QAT on the CPU, so could be interested in getting pfsense CE on that.

stephenw10

Depends what CPU that has but QAT support was added upstream so...

mikey_s

@stephenw10 Many thanks and good to hear it's come from upstream.

Test box atm doesn't have QAT capable CPU, XG 230 Rev 2 with an Intel G4400.

My other boxes is a XG135 Rev 3 with a Intel Atom C3558 and that has QAT on the CPU. They've currently got XG Home and another pfsense install.

I have a restore from a plus instance to use.

matthijs

I am a bit stubborn, so I made a snapshot (Proxmox VM) and did the upgrade with the following packages installed: acme,cron,haproxy,iperf,notes,openvpn-client-export-pfblockerng,service_watchdog,shellcmd,system_pathces
Also no pre reboot

After the upgrade everything seems to work perfectly fine,no issues so far (I will inform here if I encounter issues)

Thank you very much for all the work making this new CE release

FCS001FCS

I did a fresh install of CE 2.8 Beta on a bare metal mini-PC with an Intel N5105 via the NetGate Installer and all seem to work OK.

I wanted to transition to KEA DCHP and that also seems to work well as the static IP reservations are working as best as I can tell.

I have 2 Unifi USW Flex Mini switches that I test a few VLANs on and I had to find a way to get the DCHP-Option 43 working in KEA DCHP as that is the only way for these basic managed switches (no SSH) to find the Unifi Controller on another sub-net. Many thanks to @Gertjan for the help and my solution is described in NetGate forum link.

I also installed TailScale and pfBlockerNG and they also seem to work fine, at least on this small home-lab test mini-PC.

Overall, I am very pleased with the CE 2.8 Beta and I am looking forward to upgrading my main home pfSense system once CE 2.8 gets out of Beta.

Thanks to all the developers for all their hard work on pfSense.

SteveITS

@Popolou said in 2.8.0-BETA snapshots are now available:

You guys at Netgate do like flying close to the sun what with the mini-fits caused by last year's April Fools

https://www.reddit.com/r/PFSENSE/s/B4plyGO6RX

matthijs

@matthijs

I had an issue with a static arp entry, but it was a wrong configuration on my side (an old wrong static arp entry/Mac address) The IP adres with this static ARP entry was in use by another host (with another MAC address) an that was an issue. I did not experience this in 2.7.2 So in fact 2.8.0 is behaving correctly