<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vlan on nagg.eu</title><link>https://nagg.eu/tags/vlan/</link><description>Recent content in Vlan on nagg.eu</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 25 Jul 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://nagg.eu/tags/vlan/index.xml" rel="self" type="application/rss+xml"/><item><title>Debian QEMU/KVM bridged networking and VLAN</title><link>https://nagg.eu/debian-qemu-kvm-bridged-networking-and-vlan/</link><pubDate>Sun, 25 Jul 2021 00:00:00 +0000</pubDate><guid>https://nagg.eu/debian-qemu-kvm-bridged-networking-and-vlan/</guid><description>&lt;p&gt;By default on every Linux distro after installing &lt;code&gt;QEMU&lt;/code&gt; and &lt;code&gt;libvirt&lt;/code&gt; two
kinds of networking are available:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;NAT: VM sits behind a NAT.&lt;/li&gt;
&lt;li&gt;MACVTAP: without going into much details it acts more or less like a
bridged network, except not really. One of the most annoying limitations is
that host to guest communication and vice versa are not really working well.
Other important things might be broken as well, like for example VRRP.
This mode is good for quick and dirty testing but not really for a stable
environment.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;BRIDGED networking is also supported by &lt;code&gt;libvirt&lt;/code&gt; but requires some manual
work.&lt;br&gt;
A possible networking schema could be the following:&lt;/p&gt;</description></item></channel></rss>