ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] GeoIP information presentation

From: Ulf Lamping <ulf.lamping@xxxxxx>
Date: Sun, 08 Mar 2009 10:57:38 +0100
Jaap Keuter schrieb:
Hi list,

Currently the GeoIP information is an alternating list of source and destination paramters, like so:

     [Source GeoIP Country: China]
     [Destination GeoIP Country: Japan]
     [Source GeoIP City: Tokyo, 40]
     [Destination GeoIP City: Tokyo, 40]
     [Source GeoIP AS Number: AS4837 CNCGROUP China169 Backbone]
     [Destination GeoIP AS Number: AS17676 Japan Network Information Center]
     [Source GeoIP Latitude: 35.685001]
     [Destination GeoIP Latitude: 35.685001]
     [Source GeoIP Longitude: 139.751404]
     [Destination GeoIP Longitude: 139.751404]

Making it hard to get an overview of source and destination information and using a lot of display real estate. My proposal would be to:
1. Group source / destination information
2. Put details into subtree

This would look like so:

v [Source GeoIP: China, Tokyo, 40, AS4837 CNCGROUP China169 Backbone, 35.685001, 139.751404]
       [Source GeoIP Country: China]
       [Source GeoIP City: Tokyo, 40]
       [Source GeoIP AS Number: AS4837 CNCGROUP China169 Backbone]
       [Source GeoIP Latitude: 35.685001]
       [Source GeoIP Longitude: 139.751404]
v [Destination GeoIP: Japan, Tokyo, 40, AS17676 Japan Network Information Center, 35.685001, 139.751404]
       [Destination GeoIP Country: Japan]
       [Destination GeoIP City: Tokyo, 40]
       [Destination GeoIP AS Number: AS17676 Japan Network Information Center]
       [Destination GeoIP Latitude: 35.685001]
       [Destination GeoIP Longitude: 139.751404]

Comments?

Sounds reasonable!

Will you implement it? Otherwise please write a bugzilla entry ;-)

Regards, ULFL