I have updated from 10.0-RELEASE to 10.1-RELEASE and got these messages after reboot:
The host serves as Internet gateway and firewall and there's no Internet access from the LAN now. But there's Internet access on the server host itself. The upgrade procedure was flawless. What could it be and how to solve it?
I searched the Internet and found that it's a common (more or less) issue which may happen after a system upgrade. But, it happens when there's a version mismatch between the system kernel and some additional components which are not upgraded in time.
In my case all components are managed with the pkg utility, nothing was built from source. So, the system should be up to date and consistent. But something went wrong.
Here's the output from the
The complete output is huge. It seems that the most part of the system wasn't updated. How to fix this?
Code:
pfctl: DIOCADDRULE: Operation not supported by device
miniupnpd[2015]: ioctl(dev, DIOCGETRULES, ...): Operation not supported by device
miniupnpd[2015]: ioctl(dev, DIOCCHANGERULE, ...) PF_CHANGE_GET_TICKET: Operation not supported by device
I searched the Internet and found that it's a common (more or less) issue which may happen after a system upgrade. But, it happens when there's a version mismatch between the system kernel and some additional components which are not upgraded in time.
In my case all components are managed with the pkg utility, nothing was built from source. So, the system should be up to date and consistent. But something went wrong.
Here's the output from the
freebsd-update IDS
command:
Code:
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for [HIGHLIGHT]10.1-RELEASE[/HIGHLIGHT] from update6.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
...
[FILE]/sbin/pfctl[/FILE] has SHA256 hash 24ec617f68afd314d37366e47bce72ec376290752bb56d5c56b9211056afa142, but should have SHA256 hash d8774d2a5ed24dcf5ac817dd73b80c88b906ad4a25a1c90152f28584602a3dd1.
[FILE]/sbin/pflogd[/FILE] has SHA256 hash 248d6ed5e83b6d24f631a9212cc2f4873f258f1258d77ca62db76f258a03c8b9, but should have SHA256 hash 2769d1938cd2cc51310937a84f3f13cab665ce2a7f2b78960090296ee4c6c757.
...