


The idea behind GeoIP resolution is that you can see where an IP address is located and who the provider of that address is.

Update: There’s a newer article for GeoIP setup in Wireshark 2.x here. Oh, and then there is GeoIP resolution, which is really helpful in some cases as well, but it takes a little time to set it up. I really like MAC layer resolution, and often I enable network layer name resolution, but I really do not like protocol name resolution. One of the many features Wireshark provides is the name resolution for various protocol layers, and I have to admit that – at least for me – some of them are really helpful while others (well, one of them, to be more specific) annoy the hell out of me.
