Skip to main content

mac spoofing in Ovirt

What is mac spoofing?

Each networked device or network interface is assigned a unique Media Access Control address (MAC). MAC address spoofing (or MAC spoofing) is a technique of "faking" this mac address, However MAC address is the hard coded address, But by using some tools we can change it on operating system layer. But never changed forever.

Why we need mac spoofing in Virtualization?

Now a question about the virtualization, why we need to enable mac spoofing in Virtualization? In Normal virtualization we don't need to enable the mac spoofing. But when we create nested virtual environment (or guests inside of guest). In that case we need to enable mac spoofing to pass the packet to nested virtual guest.

Now each vendor has different technologies to enable mac spoofing in nested virtualization. Here i am going to demonstrate the steps how we can enable mac spoofing in Ovirt?!


First of all i need to install the vdsm hook on the Node machine:

# yum install vdsm-hook-macspoof

After thet i need to create a property of new vdsm hook in ovirt engine:

# engine-config -s "UserDefinedVMProperties=macspoof=(true|false)"

Now we need to reload the service:

# service ovirt-engine restart 
# service vdsmd restart ( on host )

Now we can select this new value for our new virtual guest:

To select the new property we following steps:

Step 1: Bring Down the Virtual Machine

Step 2: Edit the Virtual Machine

Step 3: Click Advanced

Step 4: Go to custom properties


Step 5: Add a key

Step 6: Select macspoof

Step 7: Type "true" as the value

Step 8: Start the Virtual Machine




    

Comments

Popular posts from this blog

Docker Container Management from Cockpit

Cockpit can manage containers via docker. This functionality is present in the Cockpit docker package. Cockpit communicates with docker via its API via the /var/run/docker.sock unix socket. The docker API is root equivalent, and on a properly configured system, only root can access the docker API. If the currently logged in user is not root then Cockpit will try to escalate the user’s privileges via Polkit or sudo before connecting to the socket. Alternatively, we can create a docker Unix group. Anyone in that docker group can then access the docker API, and gain root privileges on the system. [root@rhel8 ~] #  yum install cockpit-docker    -y  Once the package installed then "containers" section would be added in the dashboard and we can manage the containers and images from the console. We can search or pull an image from docker hub just by searching with the keyword like nginx centos.   Once the Image downloaded we can start a contai

Remote Systems Management With Cockpit

The cockpit is a Red Hat Enterprise Linux web-based interface designed for managing and monitoring your local system, as well as Linux servers located in your network environment. In RHEL 8 Cockpit is the default installation candidate we can just start the service and then can start the management of machines. For RHEL7 or Fedora based machines we can follow steps to install and configure the cockpit.  Following are the few features of cockpit.  Managing services Managing user accounts Managing and monitoring system services Configuring network interfaces and firewall Reviewing system logs Managing virtual machines Creating diagnostic reports Setting kernel dump configuration Configuring SELinux Updating software Managing system subscriptions Installation of cockpit package.  [root@rhel8 ~] #  dnf   install cockpit cockpit-dashboard  -y  We need to enable the socket.  [root@rhel8 ~] #  systemctl enable --now cockpit.socket If firewall is runnin

Containers Without Docker on RHEL/Fedora

Docker is perfectly doing well with the containerization. Since docker uses the Server/Client architecture to run the containers. So, even if I am a client or developer who just wants to create a docker image from Dockerfile I need to start the docker daemon which of course generates some extra overhead on the machine.  Also, a daemon that needs to run on your system, and it needs to run with root privileges which might have certain security implications. Here now the solution is available where we do not need to start the daemon to create the containers. We can create the images and push them any of the repositories and images are fully compatible to run on any of the environment.  Podman is an open-source Linux tool for working with containers. That includes containers in registries such as docker.io and quay.io. let's start with the podman to manage the containers.  Install the package  [root@rhel8 ~] # dnf install podman -y  OR [root@rhel8 ~] # yum