Project

General

Profile

Actions
Copy link

Bug #14228

closed

pfBlockerNG might not support new Maxmind license keys

Added by Jon Brown about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
pfBlockerNG
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.6.0
Affected Plus Version:
Affected Architecture:

Description

https://dev.maxmind.com/geoip/release-notes/2023?lang=en#changes-to-maxmind-license-keys

  • New license keys will be longer, with a six character prefix.
  • The character set is changing from [a-zA-Z0-9] to [a-zA-Z0-9_].
  • The length of the license key will now be 40 characters.
  • License keys will have a _mmk suffix.
The Maxmind input fields uses the PFB_FILTER_ALUM The PFB_FILTER_ALUM is a boolean for alphanumeric or not, but the new licenses will have an underscore allowed in them
Actions
Copy link
 #1

Updated by Kris Phillips about 1 year ago

  • Status changed from New to Confirmed

I can confirm this behavior in 3.2.0_3 on 23.01 of pfSense Plus.

Actions
Copy link
 #2

Updated by aleksei prokofiev about 1 year ago

I can confirm this issue.
I used a workaround on Reddit and it worked.
https://www.reddit.com/r/pfBlockerNG/comments/11tswx0/maxmind_license_key_invalid/

Actions
Copy link
 #3

Updated by Artur Hawkwing about 1 year ago

This was fixed in the 3.2.0_4 which is live.

Actions
Copy link
 #4

Updated by Chris W about 1 year ago

Closing this out since 3.2.0_4 is now available in System > Package Manager.

Actions
Copy link
 #5

Updated by Chris W about 1 year ago

  • Status changed from Confirmed to Resolved
Actions
Copy link

Also available in: Atom PDF