Now Available: pfSense® CE 2.8.0-RELEASE

[b3rt]

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

@b3rt I am not 100% sure but I believe pfSense CE 2.7.2 users did not receive a package update.

I think there is no difference between CE / pfsense + package, it's all based on this package, no?
https://github.com/pfsense/FreeBSD-ports/commits/devel/www/pfSense-pkg-squid
And that by itself is behind the more up-to-date freebsd version.

[fireodo]

Hi,

the GUI update is offering me, when choosing 2.8.0 stable branch, the version 2.8.0.1500029 - is this correct?

Regards,
fireodo

[Popolou]

Great news and thank you. Two years is a looong time in this industry mind you but the mob will indeed be pleased (if not reassured!).

[ramup]

@b3rt
Yes there were differences between CE / plus users in respect of squid package.
CE users package stayed at 0.4.somewhat version while up-to-date-package was 0.5.3

[ramup]

@b3rt
pfsense 2.7.2 users stayed at "Config Rev 23.3"
pfSense Versions
while pfSense Plus users changed to "Config Rev 23.6" on 2024-11-25 and higher since then.
pfSense 2.8.0 now uses "Config Rev 24.0" equally to pfSense Plus

[b3rt]

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

@b3rt
pfsense 2.7.2 users stayed at "Config Rev 23.3"
pfSense Versions
while pfSense Plus users changed to "Config Rev 23.6" on 2024-11-25 and higher since then.
pfSense 2.8.0 now uses "Config Rev 24.0" equally to pfSense Plus

right, that's all ok (:
are you sure this impacts the list of available packages? given these packages are by default not part of any pfsense version?

[stephenw10]

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

the version 2.8.0.1500029 - is this correct?

Yes, that's correct. The appended kernel version is the result of build system changes. The display code is fixed in 2.8.0 but 2.7.2 will still show that until you upgrade.

[fireodo]

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

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

the version 2.8.0.1500029 - is this correct?

Yes, that's correct. The appended kernel version is the result of build system changes. The display code is fixed in 2.8.0 but 2.7.2 will still show that until you upgrade.

Thanks!

[nimrod]

Is there going to be offline installation image ? I dont see it here:

https://atxfiles.netgate.com/mirror/downloads/

[stephenw10]

Not currently. New installs of 2.8.0 are via the Net Installer only.

[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.