Logo Atlas
  • Home
  • About Me
  • Skills
  • Education
  • Recent Posts
  • Certifications
  • Posts
  • Dark Theme
    Light Theme Dark Theme System Theme
Logo Inverted Logo
  • Tags
  • ACLs
  • Administration
  • ANDORID
  • APACHE
  • ARP
  • ASIR
  • ASO
  • AW
  • BIND9
  • Bridge
  • CENTOS
  • CI/CD
  • CISCO
  • Cloning
  • CMS
  • Comands
  • Containers
  • Contenedores
  • Controladores NVIDIA
  • DEBIAN
  • Debian 12
  • Debian13
  • DHCP
  • DNAT
  • DNS
  • DNSMASQ
  • Docker
  • Enrutamiento
  • FIREWALL
  • FORENSE
  • FORTINET
  • FORWARDING
  • FTP
  • GNS3
  • HTTPS
  • Hypervisor
  • IPTABLES
  • IPv4
  • IPv6
  • ISO
  • IWEB
  • Jenkins
  • Jenkis
  • Kubernetes
  • KVM
  • LAMP
  • LEMP
  • Libvirt
  • LINUX
  • MariaDB
  • Metrics
  • Mysql
  • NAT
  • Network
  • Networking
  • NFTABLES
  • NVIDIA Drivers
  • Observability
  • OPENVPN
  • Oracle
  • Pools
  • PostgreSQL
  • Prometheus
  • Redes
  • REDHAT
  • Resize
  • Resources
  • ROCKY
  • Routing
  • Services
  • Servicios
  • Sistemas
  • SMR
  • Snapshots
  • SNAT
  • SSH
  • Storage
  • STRONGSWAN
  • Switches
  • Templates
  • Ubuntu
  • Virtualization
  • VM
  • Volumes
  • VPN
  • Windows
  • WIREGUARD
  • Wireshark
  • WordPress
Hero Image
Network types in KVM (NAT, isolated and bridged)

In KVM, network virtualization is mainly managed through libvirt, which lets us create and administer various kinds of virtual networks to which our virtual machines connect. Understanding the available network types is key to properly configuring guest connectivity and the host interaction. There are two broad categories of networks in KVM: Private virtual networks: Internal networks isolated from the outside, managed via virtual bridges created by libvirt. Bridged networks: Networks that connect virtual machines directly to the host’s physical network. Private virtual networks These networks are created on the host and provide a controlled environment for virtual machines. They fall into three main types:

  • KVM
  • Virtualization
  • Libvirt
  • Networking
  • Linux
Saturday, October 18, 2025 | 3 minutes Read
Hero Image
How to create and configure private virtual networks

In this step-by-step guide you’ll create three types of virtual networks managed by libvirt and learn simple ways to verify them: NAT (Network Address Translation) Isolated Very isolated (L2 only) We’ll use virsh and XML definitions (you can do the same with virt-manager, but we’ll focus on the CLI). After each creation, there’s a quick check to confirm everything looks good. Before you start: quick requirements Packages: libvirt-daemon and libvirt-daemon-system (or your distro equivalents). Optional: virt-manager. Run commands as root or with sudo. Service: systemctl status libvirtd should be active. See current networks: virsh net-list --all Persistent config paths: /etc/libvirt/qemu/networks/ Tip: avoid subnet conflicts; choose ranges that don’t collide with your physical LAN or other libvirt networks.

  • KVM
  • Virtualization
  • Libvirt
  • Networking
  • Linux
Saturday, October 18, 2025 | 4 minutes Read
Hero Image
How to create a bridge interface on the KVM host

A bridge on the host allows your virtual machines to connect directly to the physical network as if they were another machine on the LAN. It’s the basis for “bridged networks” covered in the network types section. Important: if you perform these changes over remote SSH you may lose connectivity. Whenever possible use local/console access or have a recovery plan (KVM/IPMI, a second interface, maintenance window, etc.). 0. Preparation: identify your physical interface and back up configs Identify the physical interface connected to your LAN/Internet (for example: enp1s0, enp3s0, eth0): ip -br link ip -br addr Back up your network configuration files before changing anything — use the command appropriate to your setup: sudo cp -a /etc/netplan /etc/netplan.bak.$(date +%F) 2>/dev/null sudo cp -a /etc/network/interfaces /etc/network/interfaces.bak.$(date +%F) 2>/dev/null Important note: the IP must live on the bridge (br0), not on the physical interface. The physical interface will be left without an IP and become a slave of the bridge. Option A: Netplan (modern Ubuntu/Debian) Applies to systems using Netplan (Ubuntu Server ≥ 18.04, Debian when migrated). The most common renderer is networkd, but NetworkManager can also be used. Here we configure br0 and enslave the physical interface to the bridge.

  • KVM
  • Virtualization
  • Libvirt
  • Networking
  • Linux
  • Bridge
Saturday, October 18, 2025 | 5 minutes Read
Hero Image
IPv6 Tunnels

Introduction In this detailed post, we explore the process of configuring IPv6 to IPv4 tunnels and vice versa in Linux and Cisco environments. As the migration to IPv6 gains importance, the ability to establish communication between IPv4 and IPv6 networks becomes essential. We will cover the basics of tunnel configuration, including the most common types of tunnels, such as 6to4 and Teredo. Additionally, we will provide step-by-step instructions for configuration on both Linux systems and Cisco devices.

  • Networking
  • IPv6
  • IPv4
  • Cisco
  • Linux
Friday, September 8, 2023 | 10 minutes Read
Hero Image
Underworld

Introduction You live in UNDERWORLD. In your world, there are different types of species with one goal: to “crossbreed” with each other. These creatures are: VAMPIRES WEREWOLVES (LICÁNTROPOS): Werewolves with the ability to return to their human form. WOLFMEN (HOMBRES LOBO): Werewolves who, after their first transformation, cannot return to their human form. HUMANS: Some annoying little creatures. YOU: A tech-savvy warrior with superpowers like turning around a game that hasn’t even been released yet or having the ability to become invisible when going out to party and trying to flirt with a girl by saying things like: “Do you want me to compile your kernel, babe?” The layout of UNDERWORLD is as follows:

  • Networking
  • Wireshark
  • GNS3
  • Cisco
  • Routing
  • ACLs
Friday, September 8, 2023 | 7 minutes Read
Hero Image
Underworld evolution

The world of UNDERWORLD has evolved greatly in recent months, so you must perform network management tasks to face the new situation. On one hand, the Internet has been discovered in the Underworld, allowing each of the sub-worlds (remember: vampires, werewolves, lycanthropes, and humans) to connect to a router that, in turn, connects them to one of the two large routers that form Underworld’s Internet, called Marcus (for humans and vampires) and Alexander (for werewolves and lycanthropes). Marcus and Alexander are connected to each other.

  • Networking
  • SNAT
  • DNAT
  • Cisco
  • Linux
Friday, September 8, 2023 | 16 minutes Read
Navigation
  • About Me
  • Skills
  • Education
  • Recent Posts
  • Certifications
Contact me:
  • contacto@javiercd.es
  • javierasping
  • Francisco Javier Cruces Doval

Liability Notice: This theme is under MIT license. So, you can use it for non-commercial, commercial, or private uses. You can modify or distribute the theme without requiring any permission from the theme author. However, the theme author does not provide any warranty or takes any liability for any issue with the theme.


Toha Theme Logo Toha
© 2023 Copyright.
Powered by Hugo Logo