Thinapped vSphere Client Updated to V5.0

The Thinapped vSphere Client has finally been updated to v5.0, and is readily available for download!

Sadly the new version is v5.0 only, and will only allow you to connect to vSphere v5 hosts and since the new release has replaced the old release on the VMware Fling website, you´re out of luck if you haven´t already got the 4.0 version stowed away in your own private locker.

I hope VMware decides to either make the 4.0 version available for download as well, even if 5.0 is the current release, or at least that they create a new download package for 5.0 that also includes the 4.0 and 4.1 versions.

I know this is a fling, and that it´s unsupported by nature, I really think that this is a good idea, that is if it´s kept current with the vSphere release cycles. If that´s not possible, it should be removed and administrators should be instructed on how to create their own “ThinApped” version. After all, it´s really not that hard to do.

Installing and Configuring WANem Virtual Appliance



In a previous post, Using the WANem WAN Emulator Virtual Appliance, I’ve talked about how I’ve successfully used WANem to emulate different WAN scenarios.

Since I work for a shipping company, the ability to emulate VSAT conditions are especially useful for testing and proof-of-concept scenarios.

You can use WANem a couple of different ways but my setup is pretty simple but does the job perfectly.

Downloading WANem

I have chose to use the WANem Virtual Appliance running in a virtual machine hosted by VMware Workstation. If you don’t have Workstation handy, VMware Player will also do the job. You don’t need to use the virtual appliance, as WANem also offers a bootable ISO download that you could boot your VM from

Starting and configuring WANem

First off, extract the file, and place the virtual machine files in a know location. My choice is c:\virtual machines\ but you will have to adjust that for your specific environment.

Secondly, fire up VMware Workstation and chose the “Open existing VM or Team” option

In the file dialog box browse to where you extracted the virtual machine files and select “Open”

I like to run the WANem VM in bridge mode, since this gives the VM it’s own IP address from my DHCP server. This comes in handy later when we setup what traffic we want to route through WANem.
By default the VM is configured in “Bridge Mode” which is the network mode we want, so go ahead and start the VM by pressing the “Power on this virtual machine” option.

The WANem VM starts to boot up, but it stops asking if you want to configure all network interfaces via DHCP.

As I use DHCP in my network, I don’t have to specify any network information so I hit ‘y’ to let it continue booting.
Once again the boot process stops, this time asking you to specify a root password for the VM. Provide your own password twice, and the boot process is finished. Don’t worry about the password strength, or even if you remember it later. The VM boots on a pre-configured Knoppix LiveCD, and the next time you start it it will ask for a new password.

If you don’t see the IP address that WANem has received from your DHCP server, type status and hit enter, and it will show you the IP it has been assigned.

Open your favorite browser, and point it to http://WANemIP/WANem (in my case this was

And there it is, WANem is up and running. We’ll leave it as is for the time being, and start routing traffic through it as is.

Running IP traffic trough WANem

You have a couple of choices when it comes to routing your traffic through WANem. The easiest setup si where you set WANem as your default gateway and route all traffic through it. Remember though that this only comes into play if your destination is on another subnet than the one you are currently connected to. In many scenarios this isn’t desirable, and I prefer to route specific traffic through WANem and not have to play around with my DHCP assigned settings.

What I usually do, is to drop into cmd in administrator mode, and issue the following command:

route add {destination IP} mask {WANem IP}

This routes all traffic from the computer I run the command on, through the WANem IP address, and from there on it goes to it’s original destination. This allows it to work on local subnet traffic, as well as remote traffic, and it will not affect any other IP traffic from that computer to the rest of the network.

Obviously, we need a destination as well. For this lab setup I decided to route the traffic to my local printer through WANem. It’s ip is, so the command to run inside cmd as administrator is:

route add mask

Now, all traffic from my local computer to my printer is routed through WANem. For now, nothing much happens. WANem receives the data on it’s network card, and promptly sends it on it’s merry way to the final destination; my printer. No innocent packets have been mauled or otherwise hurt in the process, at least not so far.


If you want to route everything even local subnet traffic through WANem, enter the following command:

route add mask {WANem IP}
See this comment for context.

Tweaking WANem settings

Finally, the fun part! Now we can start playing around with those innocent little network packets that flow through the network. Ever wanted to know what happens if you try to print to a printer over a 128kb WAN link? Well, now you can! I would strongly advise against trying to print your über 120 slide PowerPoint presentation at this point, but you can if you want to. Possibly.

I’m not going to try to print over the link as it is now, we’ll have to settle for a little demonstration using much simpler means.

Tool of choice the ever faithfull ping. Basically I’ll demonstrate how WANem fiddles with your network traffic. First off, a just a normal ping of my printer with no edits done by WANem what so ever:

As you can see, as this is on my local network, the response time is great at 1ms and no dropped packets.

Now we can open the WANem web interface, and start messing about. Click on “Advanced Mode” and then on the “Start” button to bring up the web interface.

The next screen brings up a lot of options, and we’re going to tweak a couple of them.

I set the “Delay Time (ms)” to 200ms and the “Loss %” to 25%, and hit “Apply Settings”. When we turn back to our cmd window, we should see instant results in our ping monitor.

As you can see, the response time is now approximately 200ms and the packet loss is about 25%, in accordance with the settings I’ve applied. Of course, as you can see, there are lots of other settings to play around with as well.

WANem also allows you to save your settings, so if you find your own perfect little real world emulation scenario you can export the settings and re-apply them later if you wish.

Cleaning house

When testing is over, be sure to remove your static route(s) again. If you don’t, and you power down your WANem appliance you simply will not be able to reach your destination(s) until it’s powered on again. Thankfully, removing the static routes are as easy as adding them in the first place. The command to run, in an administrative mode cmd is:

route delete {destination IP}


WANem is a very nice, and simple to set up, little appliance that could make it much easier planning deployments and emulating real world scenarios. After all, do you know how your applications behave if they get high latency connections? Or if you get jitter problems or even dropped packets?

Give it a test, you might just get a bit surprised at the results you get.

Using the WANem WAN Emulator Virtual Appliance

During preparation and preliminary information gathering for a new internal project, I had a need to emulate various networking conditions and scenarios. More specifically I’m looking at the possibility of running the vCenter Client over high latency satellite links, with varying bandwidth availability and even packet loss scenarios.

Obviously the best way of testing this, in a controlled environment, is to use some kind of WAN emulator that lets you control the various networking characteristics. WANem is a free WAN emulator and it even comes as a VMware virtual appliance.

Setup is pretty straight forward, and I won’t get into the detailed instructions at this point. If someone requests it, perhaps I’ll make a HOWTO post later on.

After the WANem Virtual Appliance has been started and setup in your network environment, all you have to do is to route your traffic through it. In my test environment, I decided to route all traffic between my local computer and my vCenter Server through the WANem appliance. Doing so is pretty straight forward; Open up a cmd window, with administrator privileges, on your local computer and use the route command to force traffic through WANem:

the command itself is:
route add {destination IP} mask {WANem IP}

To tune the network properties of the traffic going through WANem, open the WANem admin page in your browser and work some magic. The screenshots below are from the advanced tab:

WANem Advanced Mode Screenshot #1WANem Advanced Mode Screenshot #2

As a simple test, I decided to add 500ms latency (delay time) and a packet loss of 25%, and as you can see from the video below it works as expected

(Video has been scaled to fit, watch it in fullscreen mode for details).


If you need to test out how your applications or networking infrastructure works when issues like latency, jitter and even dropped packets affects your clients, WANem seems like an easy and free route (pun intended) for testing purposes.