After upgrading from 2.6.0 to 2.7.2, the firewall rules do not work
-
@sahhha re: the first part, could be https://docs.netgate.com/pfsense/en/latest/releases/2-7-1.html#troubleshooting
-
Try running:
pfctl -v -f /tmp/rules.debug
See where it fails. -
Actually with that error it's probably a mismatch between the kernel and something in userspace.
Check:
pkg-static info -x pfSense -
This post is deleted! -
@SteveITS I read this in the first place, but I didn't notice anything similar to my problem.
-
@SteveITS I don't have much knowledge - I don't see a failure here.
I posted the result of the upload on Google Drivehttps://drive.google.com/file/d/1RHIl42A_y1j18ERI6A90cyV0NRwb3rzM/view?usp=drive_link
-
@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 -
Yes you have a bunch of 2.7.0 stuff still on there. Try running:
pkg-static upgradeSe what that offers you. You can probably just accept those and complete the upgrade but be sure to have a config backup first.
Steve
-
This post is deleted! -
@stephenw10
Thanks Steve! I have updated and installed the packages. The error is gone.
