Pat Shuff's Blog

  • Iaas
    September 20, 2016

Corente DataCenter Setup

Yesterday we went through the theory of setting up a VPN to connect a subnet in our data center to a subnet in the Oracle Cloud. Today we are going to go through the setup of the Corente Gateway in your data center. We will be following the Corente Service Gateway Setup. Important, this lab has problems. Corente does not work with VirtualBox.

The first step that we need to do is ensure that we have a Linux server that we can install the services on in our data center. We will be installing these services on an Oracle Linux 6.7 release running in VirtualBox. To get started we install a new version from an iso image. We could just as easily have cloned an existing instance. For the installation we select the software development desktop and add some adminstration tools to help look at stuff later down the road.

According to the instructions we need to make sure that our user has sudo rights and can reconfigure network settings as well as access the internet to download code. This is done by editing the /etc/sudoers file and adding our oracle user to the access rights. We then run

modprobe -v kvm-intel
egrep '^flags.*(vmx|svm)' /proc/cpuinfo

to verify that we have the right type of virtualization needed to run the VPN software. It turns out that VirtualBox does not support nested virtualization which is needed by the Corente software. We are not able to run the Corente Gateway from a VirtualBox instance.

We need to follow a different set of instructions and download the binaries for the Corente Gateway Services - Virtual Environment. Unfortunately, this version was depreciated in version 9.4. We are at a roadblock and need to look at alternatives for connecting Corente Gateway Services from out sandbox to the Oracle Cloud.

I debated continuing on or showing different failed paths in this post. I decided that showing a failed attempt had as much value as showing a successful attempt. Our first attempt was to install the gateway software on a virtual instance using VirtualBox since it is a free product. Unfortunately, we can't do this since it does not support passing the virtual interfaces from the Intel Xeon chip into the guest operating system. The second attempt was to go with a binary specifically designed to work with VirtualBox and load it. It turns out that this version was decommitted and there really is not solution that works with VirtualBox. Tomorrow we will look for alternatives of running the gateway on a native Windows host and a MacOS host since I use both to write this blog. Installing a gateway on a physical host is not optimum because we might need to reconfigure ethernet connections. My preference is to stay in a sandbox but setting up an OracleVM server, VMWare server, or HyperV server would all be difficult at best. An alternative that we might look at is setting up our gateway server in another cloud instance and connecting one cloud vendor to another cloud vendor. It all depends on who exposes the hardware virtualization to their guest instances. More on that tomorrow.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.