Description of problem: jwhois.conf contain some regular expressions to match IPv6 addresses and select relatedwhois database. Version-Release number of selected component (if applicable): jwhois-3.2.3-4 (from devel) How reproducible: always Steps to Reproduce: 1. Add a entry to /etc/jwhois.conf like # 2A01:0000::/16 "^2A01:[A-F0-9][A-F0-9][A-F0-9][A-F0-9]:.+" = "whois.ripe.net"; (this is according to newer data on IANA) 2. Try $ whois 2a01:800::/23 Actual results: $ whois 2a01:800::/23|grep Querying [Querying whois.internic.net] Expected results: Same result with leading "0" in the second address part: $ whois 2a01:0800::/23|grep Querying [Querying whois.ripe.net] Additional info: Looks like the solution to catch IPv6 addresses should be only a temporary one and replaced by CIDR lookup like already implemented for IPv4. See also https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=143682#c0 I would suggest to take a look at my project ipv6calc http://www.deepspace6.net/projects/ipv6calc.html I have already implemented the registry selection by database. You will find also code for "decompressing" IPv6 addresses and could use the database file http://cvs.deepspace6.net/view/ipv6calc/databases/ipv6-assignment/dbipv6addr_assignment.h to generate proper CIDR data for jwhois.conf from current data taken from the registries. Hopefully, one has time to implement this in the near future. Otherwise, I had to look for some free time...
Hello, you can probably use "^2A01:[A-F0-9]?[A-F0-9]?[A-F0-9]?[A-F0-9]:.+" = "whois.ripe.net"; or in this case even "^2A01:.+" = ... I agree jwhois should be doing a real subnet match, but that should happen upstream, not as a Fedora-specific patch. I'll try to prepare something....
Created attachment 129129 [details] Add type = cidr6 I have sent this patch upstream.
The patch was accepted upstream, so Fedora should get it with a new upstream release. Thanks for your report.
Hmm...looks like they need much time for releasing a new version :-(
See also https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199261 for RHEL4