I have tested the Internet Connectivity that is provided with VMware vCloud Air OnDemand Service. And the results are pretty impressive! I went through assigning a public IP address, interconnecting it with the internal gateway, did some NAT and firewall configuration, and eventually tested the connection speeds with speedtest.net. See for yourself in the screenshots accompanied by few words below.
Assigning a Public IP Address
The first step is to go into the Gateways Tab and click on your default Gateway. I have intentionally hidden the Gateway’s IP in order to protect the public IP addresses that are provided by VMware. I will mark it as GW_IP in all future screenshots.
When you click on the gateway, you will be taken to another menu with NAT Rules, Firewall Rules, Networks and Public IPs – this is the menu that we want to enter. After we are there, click on “Add IP Address”:
You will be notified that you will be charged for this public IP Address. And of course we are sure we want to add one:
After you have confirmed the IP address registration, you will see your new public IP address – I have marked it down as PUBLIC_IP. This is same as the GW_IP you have been provided even before you requested a public IP Address.
Configuring the Firewall
There are no rules in Firewall by default – that means a “Block All” rule is in Effect.
Let’s create one to allow us to ping our Machine (a bit lazily though – from ANY IP Address 🙂 – the interface after you click Add Firewall Rule is pretty simple. Just name it, enter the settings – you can also log the traffic, which is pretty neat.
After you have configured the rule, you can create some more or if you are happy with the rule set you have just created, you can click Finish.
And behold, our rule is indeed working!
Now, what we have done is to enable our gateway to be able to ping – but we’d like to map the IP we just got to our Windows 2012 R2 Machine we have created in the previous article. This is done by two NAT rules – DNAT and SNAT – see the screenshots below on how it is configured.
The first rule binds the 192.168.0.2 LAN address to Public IP and when a request for Port 3389 from outside gets sent to this IP, it redirects it to our server on the same port. Pretty Nifty.
The first thing I have wanted to do is to connect to the Windows Update service and see any new updates – I was pleasantly surprised that the OS Image VMWare uses is pretty up-to-date! Just a “few” updates to install.
Now, aside from internet browsing, there is one more thing I wanted to test out – and that is a speedtest. I’ve tried testing a connectivity to London – and got some really nice speeds.
What surprised me more, however – is testing out connectivity to my geographical location – and that is Brno, Czech Republic. And I was positively surprised yet again!
This test has confirmed my opinion on the VMware vCloud Air OnDemand Service. It is easy to use, quick to provision. The bandwidth is excellent from two places that were in my interest -VMware’s Data Center has plenty of horsepower to push the bits through the network.