Database GeoIP [ GeoIP.Dat ] not found. Reputation function terminated.

[Sergei_Shablovsky]

Hi folks!

The message "Database GeoIP [ GeoIP.Dat ] not found. Reputation function terminated." occur when scheduled CRON event running.
As a result Reputation function not working.

How to fix this issue?

Thank You all!

pfSenese
2.3.5-RELEASE-p2 (i386)
FreeBSD 10.3-RELEASE-p29

pfBlockerNG**-devel
2.2.1**

[johnpoz]

For starters use actual current version of pfsense.

MaxMind also will require account for downloading db very very soon, if not already! So your going to have to be on current pfblocker for those changes to work once the package is updated.

If your running on 32bit hardware - time to upgrade ;)

here is info about the changes from maxmind
https://forum.netgate.com/topic/149128/maxmind-will-require-an-account-and-license-key-to-use-geolite2-dbs

When they are doing it
"Starting December 30, 2019,"

[Sergei_Shablovsky]

@johnpoz said in Database GeoIP [ GeoIP.Dat ] not found. Reputation function terminated.:

For starters use actual current version of pfsense.

Thank You for answering!

Do You mean installing STABLE version instead of DEV version?

MaxMind also will require account for downloading db very very soon, if not already! So your going to have to be on current pfblocker for those changes to work once the package is updated.

I read this several mins ago in this forum.
Also a news about excluding IP from MaxMind database - really horrible news. Just add another one headpain for admins and security departments.

If your running on 32bit hardware - time to upgrade ;)

I know this well. This is for our test lab appliance.
We have a plan about this in nearest feature. :)

From the other side:

• vulnerabilities of 2.3.5-RELEASE-p2 (i386) & FreeBSD 10.3-RELEASE-p29 are not very critical to us in current time.
• many good packets are still available only on 2.3.5 version, and we have a timeframe when admins would have time to learn pfSense and other packets, and packets maintainers update packets to new versions of pfSense & FreeBSD requirements. (Or die, and another great packets come on a stage - both scenarios are great for us as a admins :).

here is info about the changes from maxmind
https://forum.netgate.com/topic/149128/maxmind-will-require-an-account-and-license-key-to-use-geolite2-dbs

When they are doing it
"Starting December 30, 2019,"

Thank You, I know... Horrible. And frustrating.

[johnpoz]

Doing anything with 2.3.x of pfsense is a waste of time.. Be it in a lab or not..

Current version of pfsense is 2.4.4p3..

[Sergei_Shablovsky]

@johnpoz said in Database GeoIP [ GeoIP.Dat ] not found. Reputation function terminated.:

For starters use actual current version of pfsense.

MaxMind also will require account for downloading db very very soon, if not already! So your going to have to be on current pfblocker for those changes to work once the package is updated.

Cold You be so please to give me a Execute Shell Command to manually update the DB?

Thank You another one time!

[johnpoz]

Even if I knew - I wouldn't to be honest.. Anything that helps someone stay on of EOL product is counter productive.. You should of moved off 2.3.x two years ago when it was announced it was going to be EOL in a year, etc.

[Sergei_Shablovsky]

@johnpoz said in Database GeoIP [ GeoIP.Dat ] not found. Reputation function terminated.:

Even if I knew - I wouldn't to be honest.. Anything that helps someone stay on of EOL product is counter productive.. You should of moved off 2.3.x two years ago when it was announced it was going to be EOL in a year, etc.

Ok, agree with You. :)

Try to shift pfSense to another server as fast as possible.