When I had meeting with SDN guys about the SDN implementation in cloud, it recalled me VXLAN that by somehow I forgot quite a long time. In fact, tunneling/overlay network solution has an indispensable role in SDN solution, especially when we would like to implement SFC in Network Function Virtualization.

In this blog, I would not show you the VXLAN implementation in SDN solution, I only have time to show you a small test bed for VXLAN in a play of a tunneling between containers running on multiple hosts.

The role of VXLAN is extending layer 2 that is basically put the containers (in this blog) or virtual machines across multiple hosts on the same layer 2 network or subnet. Of course it depends on the overlay network types that will entail caveats or issues (overhead, MTU, latency, etc.).

Here I will use LXC containers (you can use docker containers later if you want), KVM since it has OVS (virtualbox has another type of networking virtualization, a little bit complicating than KVM) and of course Linux kernel support VXLAN with both of multicast and unicast. I am going to boot two virtual machines that running on the same subnet, on each of them, I boot one LXC. Since LXC container only can connect to the host where it is running and other containers running on the same host, then if we want to connect them running on multiple hosts, we need tunneling to connect their networks together.

I did a small experiment for VXLAN with unicast, for the multicast, I will do it later if I have free time:D.

Here is the link of github where i put my instruction on, check it out:

Otherwise, if you have time, check the below blogs for VXLAN and network: