Upgrade from Pfsense 24.03 > 24.11, Many missing files

LoGman

@Gertjan said in Upgrade from Pfsense 24.03 > 24.11, Many missing files:

@LoGman
Missing man files ?
Totally normal.
True, every package comes with 'the manual' but these aren't included in pfSense packages as the whole idea of pfSense is that you pilot it using your mouse. pfSense users want to click, and don't 'read' manual ^^.

The decision was probably made because these man files, even when most are zipped up, take a lot of space. And space is often a rare resource for devices that meant to be a 'router'.

If you have a web browser and an internet connection : the manuals are just one click away : https://man.freebsd.org/cgi/man.cgi

Btw : thanks for the
pkg-static check -s -a
command.
Useful, as I can see now what files are different from what a stock pfSense is (for me) :
...
pfSense-24.11: checksum mismatch for /etc/inc/captiveportal.inc
pfSense-24.11: checksum mismatch for /etc/inc/services.inc
pfSense-24.11: checksum mismatch for /usr/local/captiveportal/index.php
pfSense-24.11: checksum mismatch for /usr/local/www/firewall_rules_edit.php
pfSense-24.11: checksum mismatch for /usr/local/www/services_dhcp_settings.php

I thought the same about those documentation files, that this is normal.

During the update, the console "spams" messages about "missing file"..

I’m also wondering why, even though I’m using the stock pfSense version, the following stood out to me, as they do not match the stock version:

/usr/local/sbin/pkg-static
/usr/local/sbin/pkg
pfSense-kernel-pfSense-24.11: checksum mismatch for /boot/kernel/linker.hints

LoGman

After Re-install:

Checking all packages: 86%
pkg-1.21.3_4: checksum mismatch for /usr/local/lib/libpkg.a
pkg-1.21.3_4: checksum mismatch for /usr/local/lib/libpkg.so.4
pkg-1.21.3_4: checksum mismatch for /usr/local/sbin/pkg
pkg-1.21.3_4: checksum mismatch for /usr/local/sbin/pkg-static
Checking all packages: 100%

Gertjan

@LoGman

pfSense 24.11 ?

I've version "pkg-1.21.3_4" but no mismatches.
And a bit strange for binary files .....

LoGman

@Gertjan said in Upgrade from Pfsense 24.03 > 24.11, Many missing files:

@LoGman

pfSense 24.11 ?

I've version "pkg-1.21.3_4" but no mismatches.
And a bit strange for binary files .....

Yes, pfsense plus 24.11. Netgate 6100.

Can you give sha256 from binary files i will check if match.

--

87c1d4ce6bba990545c736ffa68b79e7a2eaeec2cf64ee276f4359cc9c694e07  /usr/local/sbin/pkg
2e9e3aca8aa41b69d8f8d7c41dbfda8d1e4182d9a97ad02bd81dce4bc63b5c46  /usr/local/sbin/pkg-static
d2c7507a69296148012a69b62799afdac50482a495b0aaf7546738b17a04db3a  /usr/local/lib/libpkg.a
c61a105b104d76cba030bdad7f68d691ea55b63fc6cec49378ee6077154abaed  /usr/local/lib/libpkg.so.4

After Re-install of pkg.

pkg-1.21.3_4
Name           : pkg
Version        : 1.21.3_4
Installed on   : Mon Dec 30 18:39:27 2024 EET
Origin         : ports-mgmt/pkg
Architecture   : FreeBSD:15:amd64
Prefix         : /usr/local
Categories     : ports-mgmt
Licenses       : BSD2CLAUSE
Maintainer     : pkg@FreeBSD.org
WWW            : https://github.com/freebsd/pkg
Comment        : Package manager
Options        :
        DOCS           : off
Shared Libs provided:
        libpkg.so.4
Annotations    :
        FreeBSD_version: 1500019
        build_timestamp: 2024-11-27T18:28:31+0000
        built_by       : poudriere-git-3.4.99.20240122_1
        port_checkout_unclean: no
        port_git_hash  : d3d8c5a1f90a
        ports_top_checkout_unclean: no
        ports_top_git_hash: fc8cad959635
        repo_type      : binary
        repository     : pfSense
Flat size      : 45.9MiB
Description    :
Package management tool

5af0aaa6950942d16ec25abd5d027e92933fec7b4880d2ad60e3ddf66957da9c  /usr/local/sbin/pkg
8a5f737f89631fb372c8b2fa22a37bdca2d37fa75567d33543c4c55fbc6ae1fc  /usr/local/sbin/pkg-static
7da0797579932522efe914ba3bbc0053fa24ddc5dc7d2d063d90717ac69030cc  /usr/local/lib/libpkg.a
dbc88b9b31f232300670009d2b0d20a41965ce9a6d11c6a547a6263cbde870e5  /usr/local/lib/libpkg.so.4

pkg-static check -s -a
pfSense-kernel-pfSense-24.11: checksum mismatch for /boot/kernel/linker.hints

I did also generate new linker.hints_new

kldxref -f /boot/kernel/linker.hints_new /boot/kernel
Both files sha256 was same.

d763c084fcf45e9c7e6c9019d6b30d03ea97db336f5ff333038a8a33bc24e58a  /boot/kernel/linker.hints

Dunno why it says "mismatch"

stephenw10

Mmm, that is curious. Seeing that here too. Digging...

Not seeing any errors/warnings logged though and I would expect to if the linker file was actually incorrect.

stephenw10

OK that file is rebuilt at each boot so could vary from the original pkg hash.

GPz1100

@stephenw10 Any thoughts on why the difference in pkg hashes?

My 24.11 installed from scratch reflects the first set of checksums (ending in 4e07 for pkg) for pkg.

I did try the upgrade method first. Didn't see any fatal or serious errors in the upgrade (other than the tons of missing man files. Also wanted to try an install from scratch to how involved it would be to recover.

The latter worked but relied on eapol auth (cursed by att gpon w/802.1x enforcement here) being retained. This wasn't hard to do with the sfp stick being in a switch which was NOT rebooted during the process. Recall eapol auth is retained so long as the ONT link (in this case an sfp ONT) remains unbroken. Prior to shutting down 24.03, wpa_supplicant was killed with kill -9 to ensure it didn't try to do a disconnect or logoff.

stephenw10

Hmm, the only one I see changed here is linker.hints.

GPz1100

@stephenw10 Strange. I just did another reinstall with similar sha256 results from post https://forum.netgate.com/post/1201027 .

It is curious that force reinstalling pkg yields different checksums (for what appears to be the same build based on pkg info pkg).

This is using netgate installer iso - netgate-installer-v1.0-RC-amd64-20240919-1435.iso with sha256 of

5e1e2302f5e4668f4e72951670cd1e7acb075537f7fe58a241f2bb9821c6dc8d

Is there a newer installer and/or should this even be cause for concern?

stephenw10

There isn't yet a newer public installer version but it should be available soon.

The checksum difference is not a cause for concern IMO. It is curious though.