Wireshark-bugs: [Wireshark-bugs] [Bug 4030] GeoIP issues.
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4030
--- Comment #13 from Chris Maynard <christopher.maynard@xxxxxxxxx> 2011-10-06 09:54:43 PDT ---
Another update: I again downloaded the latest GeoIP databases and updated to
SVN 39292, which includes Gerald's recent changes to support GeoIP IPv6
database support in r39280 and following. My observances:
1) Sorting Lat & Long produces unexpected results with respect to when the Lat
and/or Long is unknown. The entry contains a "-", and so they show up in
between the negative values and positive values. I would think a better sort
would be to have them show up first/last before/after those with actual values.
2) For many cities, all non-US cities, but necessarily all non-US cities, the
City column is appended with a numeric, e.g., "Moscow, 48".
3) The non-UTF8 characters are still not displayed properly.
4) With no databases present, there are still Latitude & Longitude columns, but
no Country or City. Should there even be Latitude & Longitude columns?
5) With only GeoIP.dat and GeoLiteCity.dat, the 4 columns: Country, City,
Latitude and Longitude are displayed as expected.
6) With only GeoIPv6.dat and GeoLiteCityv6.dat, the 4 columns: Country, Unknown
database, Latitude and Longitude are displayed.
7) With all 4 databases present, there are 6 columns: 2 Country columns, a City
column, an Unknown database column, Latitude and Longitude columns.
I have yet to find a pcap file (in the menagerie or elsewhere) that displays
any IPv6-related GeoIP information.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are watching all bug changes.
