pfBlockerNG-devel v3.1.0_19/10

bigjohns97

@cmcdonald Correct, dashboard shows 23.01 RC

Current Base System23.01.r.20230202.1645
Latest Base System23.01.r.20230202.1645
StatusUp to date.

cmcdonald

@bigjohns97 That is very odd.

The problem is you are running older Unbound which is using Python 3.9 and not 3.11

unbound-1.17.1_2
py311-libzfs-1.1.2022081600
py311-maxminddb-2.2.0_2
py311-setuptools-63.1.0
py311-sqlite3-3.11.1_8
py39-libzfs-1.1.2022081600
py39-maxminddb-2.2.0_1
py39-setuptools-63.1.0
python311-3.11.1_1
python39-3.9.16

These are the versions that we ship with 23.01-RC

I would try reinstalling unbound:

pkg install -fy unbound

bigjohns97

@cmcdonald That's odd, I also seem to be missing that 311 libzfs which I am using zfs and boot environments.

How would I go about getting these correct packages?

Edit: that worked, I now show the following.

py311-maxminddb-2.2.0_2
py311-setuptools-63.1.0
py311-sqlite3-3.11.1_8
py39-libzfs-1.1.2022081600
py39-setuptools-63.1.0
py39-yaml-5.4.1
python311-3.11.1_1
python39-3.9.15
unbound-1.17.1_2

cmcdonald

@bigjohns97 what if you just do pkg upgrade what does it offer to upgrade?

bigjohns97

@cmcdonald

Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
Checking for upgrades (4 candidates): 100%
Processing candidates (4 candidates): 100%
The following 5 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
whois: 5.5.7 [pfSense]

Installed packages to be UPGRADED:
pfSense: 23.01.b.20230106.0600 -> 23.01.r.20230202.1645 [pfSense]
pfSense-Status_Monitoring: 1.7.11_4 -> 1.8 [pfSense]
pfSense-repo: 23.01.b.20230106.0600 -> 23.01.r.20230202.1645 [pfSense]
python39: 3.9.15 -> 3.9.16 [pfSense]

Number of packages to be installed: 1
Number of packages to be upgraded: 4

71 KiB to be downloaded.

Proceed with this action? [y/N]:

cmcdonald

@bigjohns97

What repo is set on the update GUI page?

bigjohns97

@cmcdonald

cmcdonald

@bigjohns97

Very strange....

I'm not sure how you've got in the state that you have, but I would first the pkg upgrade above, let that install, and then go back and try pkg upgrade again and see what it offers. It almost seems like you're still pointing at an old repository (you're version of pfSense-repo is 23.01.b)

strange.

Get the pfSense-repo package updated, and let's try again.

Bob.Dig

@cmcdonald Sry to interrupt, I have no hit with pkg info py*
Is this normal?


[23.01-RC][admin@pfSense.home.arpa]/root: pkg info py*
pkg: No match.

bigjohns97

@bob-dig Put the py* in quotes

Bob.Dig

@bigjohns97 said in pfBlockerNG-devel v3.1.0_19/10:

Thx, I am good.

[23.01-RC][admin@pfSense.home.arpa]/root: pkg info "py*"
py311-maxminddb-2.2.0_2
py311-setuptools-63.1.0
py311-sqlite3-3.11.1_8
py39-libzfs-1.1.2022081600
py39-setuptools-63.1.0
python311-3.11.1_1
python39-3.9.16

cmcdonald

sorry yes, otherwise it will do shell expansion on the current working directory, which is wrong lol we want the asterisk literal to be passed to pkg(8).

bigjohns97

@cmcdonald Ok, it took the upgrades and now the system info widget no longer suggests there is a upgrade and when I run pkg upgrade

Also after deleting the py_error.log and doing an update everything is back to working order on that pfblockerng side as well.

There must have been some issues with the upgrade between the 23.01 beta and the 23.01 RC. (Normally I only try RC's but was really ready to get on this 23.01 due to the upgrade to FreeBSD and the use of Speedshift vs Speedstep).

Everything is working perfectly again, thank you for all of your help.

Excellent work on the WG implementation BTW!

Draco

@BBcan177 Just wanted to confirm that I inserted the (most recent) link to the JSON file and it is parsing just fine. Much easier than manual downloads, thanks!