Logo Atlas
  • Home
  • About Me
  • Skills
  • Education
  • Recent Posts
  • Certifications
  • Posts
  • English
    Español English
  • 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
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
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