Knowledge Base

Does PingPlotter work in a virtual machine environment?


Can I run PingPlotter in a virtual machine environment such as Parallels, or VMware?


Absolutely! We've tested our products pretty thoroughly in both Parallels, and VMware - without any sort of issues. That being said - some adjustments need to be made in the network settings of both of these environments in order to get things working.

If you're running PingPlotter inside of a virtual machine, you need to make sure that you don't have the network configuration set up to use NAT. VMware and Parallels both have issues with this setting because of shortcomings in their network stack (they rewrite TTL packets in a way that PingPlotter isn't able to query any intermediate hops). This results in PingPlotter only showing the final hop, like so:

Switching the network configuration to bridged mode gets things working as you'd expect - and it's pretty easy to accomplish.

In Parallels:

You can adjust your network configuration to use bridged mode by going to "Devices" -> "Network" -> Bridged Network," and then choosing the appropriate adapter (Default, Ethernet, Wi-Fi, etc).

In VMware:

You can choose a bridged connection by going to "Virtual Machine" -> "Network Adaptor" -> "Bridged."

Some notes about Wine/Crossover

Unfortunately, PingPlotter doesn't work under Wine (or CrossOver - which is based off of Wine) - for a variety of reasons. The biggest show stopper with Wine is that it must be running as root to create the raw packets that PingPlotter requires. This creates a pretty serious security problem that could allow Wine to corrupt your host machine. The Wine creators strongly advise against running Wine as root - and as a result of this, we've stopped supporting PingPlotter in this scenario.

Article Rating (3 Votes)

Rate this article

Article Info

Article Number: 101 | Last Updated: March 10, 2017

This article has been viewed 17501 times since June 5, 2014

Filed Under: Usage


There are no attachments for this article.