VLAN for virtual machines - Versionsgeschichte

Ingo: Änderung 28 von 86.62.117.180 (Diskussion) rückgängig gemacht.

2018-08-09T19:26:06Z

Änderung 28 von 86.62.117.180 (Diskussion) rückgängig gemacht.

86.62.117.180: TECHBASYS

2017-11-07T17:08:12Z

TECHBASYS

Ingo: bug is fixed

2017-09-28T15:41:56Z

bug is fixed

Ingo: state Workaround for DefaultPVID more precisely

2017-09-28T08:23:49Z

state Workaround for DefaultPVID more precisely

Ingo: some minor corrections

2017-09-27T22:20:48Z

some minor corrections

Ingo: linkfix

2017-09-27T21:31:18Z

linkfix

Ingo: describe workaround setting DefaultPVID

2017-09-27T21:28:31Z

describe workaround setting DefaultPVID

Ingo: describe bridge with hook scripts

2017-09-27T14:13:32Z

describe bridge with hook scripts

Änderungen zeigen

Ingo: linkfix

2017-09-24T11:01:24Z

linkfix

Ingo: revise descriptions, add discussion

2017-09-23T23:57:22Z

revise descriptions, add discussion

@@ Zeile 159: / Zeile 159: @@
 The guest gets now an IP-Address on boot and is connected to VLAN 10.
-Hey guys!!!
+=== Discussion ===
-designs and builds specialty lines of lead oxide production equipment, material handling systems, battery related process machinery, parts, and accessories for the battery, pigment, glass, and chemical industries.  http://techbasys.com offers technical application and engineering services to help the customer acheive maximum benefit from their equipment and manufacturing processes.
+This works because of [[#References|three conditions]].
 === References ===

@@ Zeile 159: / Zeile 159: @@
 The guest gets now an IP-Address on boot and is connected to VLAN 10.
-=== Discussion ===
+Hey guys!!!
-This works because of [[#References|three conditions]].
+designs and builds specialty lines of lead oxide production equipment, material handling systems, battery related process machinery, parts, and accessories for the battery, pigment, glass, and chemical industries.  http://techbasys.com offers technical application and engineering services to help the customer acheive maximum benefit from their equipment and manufacturing processes.
 === References ===

@@ Zeile 383: / Zeile 383: @@
 == Workaround for setting DefaultPVID=none ==
 Setting [https://www.freedesktop.org/software/systemd/man/systemd.netdev.html#DefaultPVID= DefaultPVID] in a<code>systemd-networkd</code> configuration file to "none" does not work. Until this bug is fixed I've made a workaround. The kernel accepts setting <code>default_pvid</code> to 0 (means "none") only if <code>vlan_filtering=0</code>, so we have to do:
   '''harley$''' sudo bash -c 'echo 0 >/sys/class/net/br0/bridge/vlan_filtering'

@@ Zeile 406: / Zeile 406: @@
   '''harley$''' sudo chmod 744 /etc/systemd/network/DefaultPVID.sh
   '''harley$'''
-Next I create a service to execute this script:
+Test with <code>'''harley$''' sudo /etc/systemd/network/DefaultPVID.sh</code>. Next I create a service to execute this script:
   '''harley$''' cat /etc/systemd/system/DefaultPVID.service
   [Unit]
@@ Zeile 420: / Zeile 420: @@
   WantedBy=multi-user.target
   '''harley$'''
-And then I create a [https://www.freedesktop.org/software/systemd/man/systemd.unit.html#id-1.11.3 drop-in file for overriding vendor settings] so this service will be executed together with <code>systemd-networkd</code>:
+Test with <code>'''harley$''' sudo systemctl start DefaultPVID.service && systemctl status DefaultPVID.service</code>. After this I create a [https://www.freedesktop.org/software/systemd/man/systemd.unit.html#id-1.11.3 drop-in file for overriding vendor settings] so this service will be executed together with <code>systemd-networkd</code>:
   '''harley$''' cat /etc/systemd/system/systemd-networkd.service.d/DefaultPVID.conf
   [Unit]
@@ Zeile 428: / Zeile 428: @@
   Before=DefaultPVID.service
   '''harley$'''
 [[Category:Virtualization]]

@@ Zeile 208: / Zeile 208: @@
 == linux bridge with libvirt hook scripts ==
 We setup a bridge with VLAN enabled:
-  '''harley$''' cat 08-br0.netdev
+  '''harley$''' cat /etc/systemd/network/08-br0.netdev
   [NetDev]
   Name=br0
@@ Zeile 216: / Zeile 216: @@
   VLANFiltering=true
   STP=false
-  '''harley$''' cat 12-br0_add-enp1s0.network
+  '''harley$''' cat /etc/systemd/network/12-br0_add-enp1s0.network
   [Match]
   Name=enp1s0
@@ Zeile 227: / Zeile 227: @@
   [BridgeVLAN]
   VLAN=30
-  '''harley$''' cat 16-br0_up.network
+  '''harley$''' cat /etc/systemd/network/16-br0_up.network
   [Match]
   Name=br0
@@ Zeile 259: / Zeile 259: @@
 # [[#set VLAN-ID to the dynamic virtual network interface vnet*]]
 <span id="debug.sh">For debugging the hook-scripts</span> I've made a small script:
-  '''harley$''' cat debug.sh
+  '''harley$''' cat /etc/libvirt/hooks/debug.sh
   #!/bin/bash -e
   # https://www.libvirt.org/hooks.html
@@ Zeile 290: / Zeile 290: @@
 === get information on startup from the runtime XML-config of the domain ===
 It seems a little bit difficult to get needed information out of the big XML-config but it's no problem with XSLT. I've made a XSL-stylesheet for this and use xmlstarlet. Start a virtual machine and then its runtime configuration is available with <code>'''harley$''' virsh dumpxml deb9-test | xmlstarlet tr qemu.xsl</code>. With this I can test my stylesheet. Here is it:
-  '''harley$''' cat qemu.xsl
+  '''harley$''' cat /etc/libvirt/hooks/qemu.xsl
   <?xml version="1.0" encoding="UTF-8"?>
   &lt;!-- This stylesheet extracts the VLAN-ID and the target device of the

@@ Zeile 6: / Zeile 6: @@
 and document it here.
-In gerneral I will look at four methods:
+In gerneral I will look at three methods:
 # [[#oldstyle linux bridge as hub|oldstyle linux bridge as hub]]
 # [[#linux bridge as hub|linux bridge as hub]]
 # [[#linux bridge with libvirt hook scripts|linux bridge with libvirt hook scripts]]
 == Preparation ==

@@ Zeile 69: / Zeile 69: @@
 modify to
   ExecStart=-/sbin/agetty --autologin ''yourloginname'' --keep-baud 115200,38400,9600 %I $TERM
-To list all settings of the bridge you can use:
+<span id="bridge-settings">To list all settings of the bridge</span> you can use:
   '''harley$''' find /sys/class/net/br0/bridge/ -type f -readable -printf '%f = ' -exec cat {} \; | sort
@@ Zeile 255: / Zeile 255: @@
   vnet0   None
   '''harley$'''
-The virtual network interface vnet0 for deb9-test has no VLAN Id. Libvirt does not know something about this so we have to tell it. Libvirt provides [https://www.libvirt.org/hooks.html hook scripts] that we can use for this. We have to:
+The virtual network interface vnet0 for deb9-test has no VLAN ID. Libvirt does not know something about this so we have to tell it. Libvirt provides [https://www.libvirt.org/hooks.html hook scripts] that we can use for this. We have to:
 # [[#define VLAN-ID the virtual machine belongs to]]
 # [[#get information on startup from the runtime XML-config of the domain]]
@@ Zeile 277: / Zeile 277: @@
 === define VLAN-ID the virtual machine belongs to ===
-For thist we have an extra [https://libvirt.org/formatdomain.html#elementsMetadata element <metadata> in Domain XML format] for custom metadata. We can simply add the information to the static configuration with <code>'''harley$''' virsh edit deb9-test</code> like this (look only at the <metadata> element):
+For this we have an extra [https://libvirt.org/formatdomain.html#elementsMetadata element <metadata> in Domain XML format] for custom metadata. We can simply add the information to the static configuration with <code>'''harley$''' virsh edit deb9-test</code> like this (look only at the <metadata> element):
   '''harley$''' virsh dumpxml deb9-test | head -n9
   <domain type='kvm' id='1'>
@@ Zeile 290: / Zeile 290: @@
 === get information on startup from the runtime XML-config of the domain ===
-It seems a little bit difficult to get needed information out of the big XML-config but it's no problem with XSLT. I've made a XSL-stylesheet for this and use xmlstarlet. For developing I took a snapshot from runtime XML-config useing [[#debug.sh|debug.sh]] and prepaired it to a well formed xml-document by hand for hook-parameter $2=start. This is the result:
+It seems a little bit difficult to get needed information out of the big XML-config but it's no problem with XSLT. I've made a XSL-stylesheet for this and use xmlstarlet. Start a virtual machine and then its runtime configuration is available with <code>'''harley$''' virsh dumpxml deb9-test | xmlstarlet tr qemu.xsl</code>. With this I can test my stylesheet. Here is it:
   '''harley$''' cat qemu.xsl
   <?xml version="1.0" encoding="UTF-8"?>
-  &lt;!-- This stylesheet extracts the VLAN-Id and the target device of the
+  &lt;!-- This stylesheet extracts the VLAN-ID and the target device of the
        bridge from the domain-xml given to the libvirt hook-script "qemu".
        Example output: <meta><vlan>10</vlan><dev>vnet0</dev></meta>
@@ Zeile 322: / Zeile 322: @@
     </xsl:template>
   </xsl:stylesheet>
   '''harley$'''
-  '''harley$''' xmlstarlet tr qemu.xsl /var/log/libvirt/hooks.xml
+  '''harley$''' virsh dumpxml deb9-test | xmlstarlet tr /etc/libvirt/hooks/qemu.xsl
   <meta><vlan>10</vlan><dev>vnet0</dev></meta>'''harley$'''
 === set VLAN-ID to the dynamic virtual network interface vnet* ===
-Putting it all together here is the hook-script:
+Putting it all together here is the executable hook-script:
   '''harley$''' cat /etc/libvirt/hooks/qemu
-  #!/bin/bash -e
+  #!/bin/bash
   #/etc/libvirt/hooks/qemu
   # Docs: https://www.libvirt.org/hooks.html
@@ Zeile 338: / Zeile 337: @@
   # On startup of the domain (guest) This script does:
-  # get Metadata VLAN-Id of the guest and target device of the bridge from
+  # Get Metadata VLAN-ID of the guest and target device of the bridge from
       # the domain-xml available on standard input. It is the runtime
       # version from 'virsh dumpxml domainname'. For extracting the
@@ Zeile 377: / Zeile 376: @@
       ;;
   esac
   '''harley$'''
 === References ===
 * https://www.libvirt.org/hooks.html
 * https://serverfault.com/questions/696011/libvirt-hook-qemu-suse12
 [[Category:Virtualization]]

@@ Zeile 161: / Zeile 161: @@
 === Discussion ===
-This works because of three conditions.
+This works because of [[#References|three conditions]].
 # ageing time is 0: ageing time specifies the number of seconds a MAC Address will be kept in the forwarding database after having a packet received from this MAC Address. Setting it to 0 means there is never a MAC Address stored in the FDB.
 # unicast flood on interfaces is on: this controls whether the bridge should flood traffic for which an FDB entry is missing and the destination is unknown through this port. Defaults to on.

@@ Zeile 2: / Zeile 2: @@
 I wanted to update VLAN connections for virtual
 machines to newer technologies and put a question on
-[https://unix.stackexchange.com/questions/392758/setup-vlan-on-linux-bridge-for-virtual-machines-with-systemd?noredirect=1#comment700641_392758 unix.stackexchange]. But I do not get any answer. It seems there is very
+[https://unix.stackexchange.com/questions/392758/setup-vlan-on-linux-bridge-for-virtual-machines-with-systemd unix.stackexchange]. But I do not get any answer. It seems there is very
 little knowledge for this out there. So I decided to work on it by myself
 and document it here.
@@ Zeile 13: / Zeile 13: @@
 == Preparation ==
-I have Debian GNU/Linux 9.1 (stretch) on the host and on virtual machines for testing as described here: [[Setup KVM with console]]. I'm sitting on harley as host, my all day workstation.
+I have Debian GNU/Linux 9.1 (stretch) on the host and on virtual machines for testing. Setup is described here: [[Setup KVM with console]]. I'm sitting on harley as host, my all day workstation.
 Now I start the virtual machine, login and show its interface setting:
   '''harley$''' virsh start --console deb9-test
@@ Zeile 32: / Zeile 32: @@
   Name=vlan10
   [Network]
-  Address=192.168.10.57/24
+  DHCP=ipv4
- Gateway=192.168.10.1
+ IPv6AcceptRA=no
-To test if we have connection direct after startup I append this to .bashrc:
+ LinkLocalAddressing=no
-  '''deb9-test$''' echo ping -c3 192.168.10.1 >> .bashrc
+To test if the virtual machine has connection I use:
 Because I have to start the test virtual machine many times I setup autologin. It's no problem. There is nothing on the guest.
   '''deb9-test$''' grep ^ExecStart= /lib/systemd/system/serial-getty@.service
@@ Zeile 41: / Zeile 69: @@
 modify to
   ExecStart=-/sbin/agetty --autologin ''yourloginname'' --keep-baud 115200,38400,9600 %I $TERM
 == oldstyle linux bridge as hub ==
@@ Zeile 76: / Zeile 106: @@
 Yes, there is no VLAN filtering, means VLAN on the bridge is disabled but the guest sees the VLAN-tagged packets.
 === References ===
@@ Zeile 112: / Zeile 140: @@
   [Match]
   Name=br0
   '''harley$''' sudo systemctl restart systemd-networkd
   '''harley$'''
-But AgeingTimeSec=0 is not acepted:
+AgeingTimeSec=0 is not acepted but should:
   '''harley$''' cat /sys/class/net/br0/bridge/ageing_time
    (means 300 sec)
   '''harley$''' cat /sys/class/net/br0/bridge/stp_state
@@ Zeile 123: / Zeile 158: @@
   '''harley$'''
 === References ===