After upgrading from 2.6.0 to 2.7.2, the firewall rules do not work

sahhha

BIOS Vendor: Phoenix Technologies LTD
Version: 6.00
Release Date: Fri Jul 28 2017
Version 2.7.2-RELEASE (amd64)
CPU Type Intel(R) Xeon(R) CPU E3-1270 V2 @ 3.50GHz
AES-NI CPU Crypto: No
QAT Crypto: No

Pfsense suggested installing an update from version 2.6.0 to 2.7.0. After installation, the package manager stopped working correctly. The list of available packages has become empty. Updates 2.7.1 and 2.7.2 were missing and were not offered for installation. I have tried various methods and your recommendations and nothing has been successful. Updates 2.7.1. and 2.7.2 appeared, but could not be installed. The installation process was stopped. I performed a forced reinstallation of the packages according to the instructions Netgate Docs:

Force a reinstall of the pfSense software base package and kernel:
/usr/local/sbin/pkg-static install -yf pkg pfSense pfSense-kernel-pfSense

As a result, the system was updated to version 2.7.2. But the rules stopped working. Any Aliases attempt fails. The filters don't work.
Filter Reload
Bell Notification:

There were error(s) loading the rules: pfctl: DIOCSETREASS - The line in question reads [0]: @ 2023-12-12 17:01:36

I have completed the request
Shell Output - pfctl -s rules
it looks like it worked correctly - A list of rules is displayed.

Is it possible to restore "pfctl" in the same way as the package manager was restored?

SteveITS

@sahhha re: the first part, could be https://docs.netgate.com/pfsense/en/latest/releases/2-7-1.html#troubleshooting

stephenw10

Try running: pfctl -v -f /tmp/rules.debug
See where it fails.

stephenw10

Actually with that error it's probably a mismatch between the kernel and something in userspace.

Check: pkg-static info -x pfSense

sahhha

This post is deleted!

sahhha

@SteveITS I read this in the first place, but I didn't notice anything similar to my problem.

sahhha

@SteveITS I don't have much knowledge - I don't see a failure here.
I posted the result of the upload on Google Drive

https://drive.google.com/file/d/1RHIl42A_y1j18ERI6A90cyV0NRwb3rzM/view?usp=drive_link

sahhha

@stephenw10 Yes, I've read about it. Here is the output of the data. What can I do about it?

pkg-static info -x pfSense

pfSense-2.7.2
pfSense-Status_Monitoring-php82-1.8_3
pfSense-base-2.7.2
pfSense-boot-2.7.0
pfSense-composer-deps-0.1
pfSense-default-config-2.7.0
pfSense-kernel-pfSense-2.7.2
pfSense-pkg-Cron-0.3.8_3
pfSense-pkg-Lightsquid-3.0.7_3
pfSense-pkg-squid-0.4.46
pfSense-pkg-squidGuard-1.16.19
pfSense-repo-2.7.0_2
pfSense-repoc-20230912
pfSense-upgrade-1.2.1
php82-pfSense-module-0.95

stephenw10

Yes you have a bunch of 2.7.0 stuff still on there. Try running: pkg-static upgrade

Se what that offers you. You can probably just accept those and complete the upgrade but be sure to have a config backup first.

Steve

sahhha

This post is deleted!

sahhha

@stephenw10
Thanks Steve! I have updated and installed the packages. The error is gone.