Now Available: pfSense® CE 2.8.0-RELEASE

nimrod

I just performed dirty update and it all worked without any issues. Good work guys and keep it up.

sTicKs23

@stephenw10 Did you guys atleast managed to include the other kernel drivers in the default kernels like iscsi or rs232? Or we need to compile it ourselves again?

stephenw10

For any specific driver? It's pretty much the same included drivers as 2.7.2.

kikuyu

@stephenw10
I performed today a fresh install on new SSD from 2.7.2 to 2.8.0 with restore configuration from media during install. All went smooth. Perfect !!!

matthijs

Hi,
I have a question about the new PPOE
what are recommended settings
I run pfsense on proxmox hypervisor with virtio on this hardware https://protectli.com/vault-6-port/

Hardware Checksum Offloading yes or no ?
Hardware TCP Segmentation Offloading yes or no ?
Hardware Large Receive Offloading yes or no ?

Thanks in advance

Kr,

stephenw10

I would leave them disabled. I doubt you would see any gain using vtnet with if_pppoe on any of them.

sokeada

Hello Experts,

I have a message like below, is it normal and safe to upgrade?

stephenw10

Yes, that's expected. The appended kernel version is a result of build changes. It won't be shown going forward but 2.7.2 still sees it.

sokeada

@stephenw10 thanks for the info, so it's safe to upgrade, right?

netblues

@sokeada Yes, of course it is. It is always like that before the upgrade.

sokeada

@netblues @stephenw10 I've try to upgrade my pfSense via GU, the update process seems going smooth but at the final step while system rebooting for the upgrade, it stucked like attached, please help to analyze the problem. This micro pc is using Intel NIC.

1258dc64-a509-4bf1-9206-f0acefa37b92-photo_2025-06-03_14-05-14.jpg

netblues

@sokeada aah.. its the wifi card
See this for a solution.

https://forum.netgate.com/topic/197485/kernel-panic-when-upgrading-to-2-8-0-beta/4

sokeada

@netblues @stephenw10 thanks for the use full info but I kinda not so clear yet about disable wifi in boot loader, I can disable the wifi card in pfSense 2.7.2 before I upgrade to 2.8.0 or I can only disable wifi card after upgrade to 2.8.0 in the kernel panic screen? some said disable wifi card in bios might not help, the best option should be disable in config file or take out the hardware wifi card from the machine... please help to choose the best method and long term fix for the next issue. Actually, I don't need wifi, I use only LAN.

Thanks,

Sokeada

fireodo

@sokeada said in Now Available: pfSense CE 2.8.0-RELEASE:

take out the hardware wifi card from the machine...

Hi,

in my humble opinion that whould be the best - if possible!

Regards,
fireodo

sokeada

@fireodo thanks for the tips, I'll spare sometime to shutdown and take out the wifi card then. Just only take out the card, that's it? no extra task to turn off in bios or add in local config file, right?

Best Regards,

Sokeada

fireodo

@sokeada said in Now Available: pfSense CE 2.8.0-RELEASE:

Just only take out the card, that's it?

Yes, thats it - if you remove physically the WLAN-Card neither BIOS nor pfsense (freebsd) Kernel can detect her anymore :-)

netblues

@sokeada Obviously, since after upgrading there will be no access to the system, as it fails, you have to do everything on 2.7 before upgrading.

Οf course if you can take out the card its easier.

sokeada

@fireodo thanks, I really appreciate your suggestions.

sokeada

@netblues thanks, I really appreciate your suggestions.

stephenw10

@netblues said in Now Available: pfSense CE 2.8.0-RELEASE:

It is always like that before the upgrade.

In fact it would usually appear just as 2.8.0 for the available version but some changes to the builder resulted in 2.7.2 seeing the appended kernel version there. At what will probably be 2.8.1 it will just show 2.8.1. But, yes, safe to upgrade.

I agree removing the hardware is the best option to prevent that panic. It's doing nothing but consuming resources whilst present.

But, yes, you could add the loader disable hint to /boot/loader.conf.local whilst in 2.7.2 and then upgrade. It would still apply in 2.8.

Or if you are already in 2.8 you can interrupt the bootloader to reach the OK> prompt and set the hint there manually to allow it to boot. Then add it to the loader file once it's booted so it reboots OK next time.