RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1201857 - missing IPv6 databases
Summary: missing IPv6 databases
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: GeoIP
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Jan Safranek
QA Contact: Jan Ščotka
URL:
Whiteboard:
Depends On:
Blocks: 1203710 1295796 1313485
TreeView+ depends on / blocked
 
Reported: 2015-03-13 16:29 UTC by Carl George
Modified: 2019-12-16 04:41 UTC (History)
12 users (show)

Fixed In Version: GeoIP-1.5.0-11.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 07:41:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1158667 0 unspecified CLOSED GeoIP version bump to 1.6.4 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHEA-2016:2503 0 normal SHIPPED_LIVE GeoIP bug fix update 2016-11-03 14:12:45 UTC

Internal Links: 1158667

Description Carl George 2015-03-13 16:29:33 UTC 
Description of problem:
The GeoIP package in RHEL7 does not contain IPv6 databases.

Version-Release number of selected component (if applicable):
1.5.0-9.el7

How reproducible:
Install GeoIP and look in the /usr/share/GeoIP/ for IPv6 databases.

Steps to Reproduce:
1. yum install GeoIP
2. ls /usr/share/GeoIP/

Actual results:
No IPv6 databases are available.

Expected results:
The GeoIP package in Fedora has these IPv6 databases.  I would like to have them available in EL7 as well.
/usr/share/GeoIP/GeoIPASNumv6.dat
/usr/share/GeoIP/GeoIPv6.dat
/usr/share/GeoIP/GeoLiteASNumv6.dat
/usr/share/GeoIP/GeoLiteCityv6.dat

Additional info:
IPv6 data added to Fedora package - http://pkgs.fedoraproject.org/cgit/GeoIP.git/commit/?id=84346ccb3d89c2237232db0eaca4b8545ba312e7
Comment 2 Jan Safranek 2015-03-27 09:04:27 UTC 
Thanks for the bug report. While Red Hat welcomes bug reports on Red Hat products here in our public bugzilla database, please keep in mind that bugzilla is not a support tool or means of accessing support.  If you would like technical support please visit our support portal at access.redhat.com or call us for information on subscription offerings to suit your needs.

I'll leave the bug open, but it's chance to get fixed without a support ticket is quite low.

Also, you can easily work around this problem if you manually download IPv6 GeoIP databases and place them into /usr/share/GeoIP.
Comment 3 Carl George 2015-03-27 19:16:04 UTC 
I just opened case #01422780.  Thanks Jan!
Comment 10 Leos Pol 2016-03-07 22:37:34 UTC 
Granting qa_ack.
Comment 14 Jan Safranek 2016-06-29 13:40:53 UTC 
I'm adding GeoIPv6.dat into GeoIP.rpm, the package grows by 1.6 MiB (which is IMO acceptable). I'm creating new subpackage GeoIP-data with all other databases (~54 MiB total). These databases won't be updated via erratas, customers are advised to update them by standard GeoIP update scripts or manually.
Comment 16 Carl George 2016-06-29 21:54:34 UTC 
Would it be possible to rebase GeoIP to at least the same version EL6 EPEL has?

EL6 EPEL:
GeoIP-1.6.5-1.el6
geoipupdate-2.2.1-2.el6

EL7 base:
GeoIP-1.5.0-9.el7

GeoIP 1.6.0 split off the update script into it's own codebase, hence the separate package.  Having the EL6 and EL7 versions match would be greatly beneficial for users with mixed environments like myself.

https://github.com/maxmind/geoip-api-c/releases/tag/v1.6.0
https://github.com/maxmind/geoipupdate/releases/tag/v2.0.0
Comment 17 Jan Safranek 2016-06-30 11:30:04 UTC 
I'm sorry, it's too late for rebase in 7.3. Please fill a separate bug (with a support ticket :-) and we may rebase the package in future updates. Still, it's quite low priority package and we may focus on more important stuff.
Comment 18 Carl George 2016-06-30 12:48:27 UTC 
That's understandable.  The important part is getting the IPv6 integration.
Comment 21 errata-xmlrpc 2016-11-04 07:41:42 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-2503.html
Note You need to log in before you can comment on or make changes to this bug.