3,254
edits
Changes
Jump to navigation
Jump to search
Line 2:
Line 2: − + − + − + Line 28:
Line 28: − + Line 35:
Line 35: − + Line 99:
Line 99: − + Line 118:
Line 118: − + Line 130:
Line 130: − + Line 498:
Line 498: − + Line 517:
Line 517: − + − + Line 638:
Line 638: + + + + + + − + −
→Db compatibility with other softwares
This product includes GeoLite2 data created by MaxMind, available from
This product includes GeoLite2 data created by MaxMind, available from
https://www.maxmind.com.
https://www.maxmind.com.
=== Maintainer ===
===Maintainer===
[[User:ReetP|john crisp]]
[[User:ReetP|john crisp]]
[mailto:stephdl@de-labrusse.fr stephdl] Stéphane de Labrusse AKA [[User:stephdl|Stephdl]]<br />
[mailto:stephdl@de-labrusse.fr stephdl] Stéphane de Labrusse AKA [[User:stephdl|Stephdl]]<br />
=== Version ===
===Version===
{{#smeversion: smeserver-geoip }}
{{#smeversion: smeserver-geoip }}
{{#smeversion: smeserver-geoip1 }}
{{#smeversion: smeserver-geoip1 }}
{{#smeversion: smeserver-geoip2 }}
{{#smeversion: smeserver-geoip2 }}
{{#smeversion: smeserver-geoip-legacy }}
{{#smeversion: smeserver-geoip-lite }}
{{Warning box|From MAXMIND site :
{{Warning box|From MAXMIND site :
"Due to upcoming data privacy regulations, we are making significant changes to how you access free GeoLite2 databases starting December 30, 2019. Learn more on our blog." https://blog.maxmind.com/2019/12/18/significant-changes-to-accessing-and-using-geolite2-databases/
"Due to upcoming data privacy regulations, we are making significant changes to how you access free GeoLite2 databases starting December 30, 2019. Learn more on our blog." https://blog.maxmind.com/2019/12/18/significant-changes-to-accessing-and-using-geolite2-databases/
{{Note box|Maxmind have removed support for their legacy v1 DBs and an update to v2 DBs is required. Please see the bugtracker link to bug #9033 below for more information }}
{{Note box|Maxmind have removed support for their legacy v1 DBs and an update to v2 DBs is required. Please see the bugtracker link to bug #9033 below for more information }}
=== Installation of legacy geoip v1 db ===
===Installation of legacy geoip v1 db===
those are still available for few time only for back compatibility purpose and to avoid a yum update mess, or if you do not trust third party repo, but be aware thos db are not updated anymore since April 2018 and were already only 80% accurate then.
those are still available for few time only for back compatibility purpose and to avoid a yum update mess, or if you do not trust third party repo, but be aware thos db are not updated anymore since April 2018 and were already only 80% accurate then.
signal-event geoip-update
signal-event geoip-update
==== update of geoip v1 db ====
====update of geoip v1 db====
if you have smeserver-geoip-1.1.2-7 already installed, this will keep you on the legacy version, only change new plugin comaptible with v1 and removal of cron update.
if you have smeserver-geoip-1.1.2-7 already installed, this will keep you on the legacy version, only change new plugin comaptible with v1 and removal of cron update.
yum update --enablerepo=smecontribs
yum update --enablerepo=smecontribs
db configuration setprop geoip LicenseKey "YOUR LIC KEY" AccountID "YOUR ACCT ID"
db configuration setprop geoip LicenseKey "YOUR LIC KEY" AccountID "YOUR ACCT ID"
==== I installed the beta versions of smeserver-geoip v2 ====
====I installed the beta versions of smeserver-geoip v2====
if you installed smeserver-geoip-1.2-1, smeserver-geoip-1.2-2, smeserver-geoip-1.2-3, then you have already a v2, but you still need to do as you were with legacy version and want to upgrade to v2. Otherwise you will not have the db updated anymore
if you installed smeserver-geoip-1.2-1, smeserver-geoip-1.2-2, smeserver-geoip-1.2-3, then you have already a v2, but you still need to do as you were with legacy version and want to upgrade to v2. Otherwise you will not have the db updated anymore
db configuration setprop geoip LicenseKey "YOUR LIC KEY" AccountID "YOUR ACCT ID"
db configuration setprop geoip LicenseKey "YOUR LIC KEY" AccountID "YOUR ACCT ID"
==== Update the db ====
====Update the db====
(only working for geoip2 from 2019/01/03)
(only working for geoip2 from 2019/01/03)
signal-event geoip-update
signal-event geoip-update
This contrib adds a template to /etc/crontab to automatically update the database once a month. It's set to do so at midnight on the 5th of each month. If you have a paid subscription through the maintainer of this database (http://dev.maxmind.com/geoip/geoipupdate/) you can update more often. If you do want to update more often, you will have to create a custom template to handle the change. In addition, you will be supplied login credentials that have to be inserted into the file /etc/GeoIP.conf for the update to complete. The file is not templated so it will survive reboots. Use your favorite text editor to insert the information into this file.
This contrib adds a template to /etc/crontab to automatically update the database once a month. It's set to do so at midnight on the 5th of each month. If you have a paid subscription through the maintainer of this database (http://dev.maxmind.com/geoip/geoipupdate/) you can update more often. If you do want to update more often, you will have to create a custom template to handle the change. In addition, you will be supplied login credentials that have to be inserted into the file /etc/GeoIP.conf for the update to complete. The file is not templated so it will survive reboots. Use your favorite text editor to insert the information into this file.
==== More info on openfusion repo config ====
====More info on openfusion repo config====
The openfusion repo now includes a number of packages as includes and Excludes, this is to prevent inadvertent system updates occurring when updating the old v1 DB package resulting in unstable or inaccessible systems, this is all they are for. These can be seen here:
The openfusion repo now includes a number of packages as includes and Excludes, this is to prevent inadvertent system updates occurring when updating the old v1 DB package resulting in unstable or inaccessible systems, this is all they are for. These can be seen here:
Users are advised to determine the effectiveness of the database for themselves.
Users are advised to determine the effectiveness of the database for themselves.
=== Db compatibility with other softwares ===
===Db compatibility with other softwares===
Some software either use or depends on a geoip library, here is a table to help understand:
Some software either use or depends on a geoip library, here is a table to help understand:
{| class="wikitable sortable"
{| class="wikitable sortable"
|yes
|yes
|Yes with updates
|Yes with updates
|Requires updated perl-IO-Socket-INET6 and check_badcountries plugin: https://bugs.contribs.org/show_bug.cgi?id=10523
|Requires updated perl-IO-Socket-INET6 and check_badcountries plugin: https://bugs.contribs.org/show_bug.cgi?id=10523
|-
|-
|qpsmtpd plugin / smeserver-geoip
|qpsmtpd plugin / smeserver-geoip
|smecontribs
|smecontribs
|yes
|yes
|
|
|provided by libmaxminddb-devel (see https://bugzilla.redhat.com/show_bug.cgi?id=1663670)
|provided by libmaxminddb-devel (see https://bugzilla.redhat.com/show_bug.cgi?id=1663670)
|-
|bind-libs /bind-utils
|smeos
|required
|unknown
|
|}
|}
you might want to use legacy db updated with recent Maxmind geoilite2, see: https://www.miyuru.lk/geoiplegacy
you might want to use legacy db updated with recent Maxmind geoilite2, see: https://www.miyuru.lk/geoiplegacy
=== Bugs ===
===Bugs===
Please raise bugs under the SME-Contribs section in [http://bugs.contribs.org/enter_bug.cgi bugzilla]
Please raise bugs under the SME-Contribs section in [http://bugs.contribs.org/enter_bug.cgi bugzilla]
and select the smeserver-geoip component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-geoip|title=this link}}.
and select the smeserver-geoip component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-geoip|title=this link}}.