re: assigning VM to a VLAN on a trunk bridge that exists on LACP bond - how to

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


I was able to achieve what I wanted to do by the /etc/network/interfaces
file posted below on the host. KVM/QEMU does not accept the bridge
notation with dots in it, such as bridge0.20. Instead, one needs to
create a separate vlan definition and a bridge on top of that vlan. This
would create an access port for the VMs that use that bridge. What I was
trying to do was to create a trunk port on a bridge, and by the static
IP chosen for VMs, let each VM claim their VLANs. In this working
version, the access ports claim the VLAN that the VM would belong to
instead. I hope that this would help people avoid the suffering I
endured during the last week to achieve this, lol!

auto lo
iface lo inet loopback

# bond interface
auto bond0
iface bond0 inet manual
        bond-slaves enp5s0 enp6s0
        bond-mode 802.3ad
	bond-xmit-hash-policy layer2+3
        bond-miimon 100
        bond-lacp-rate 1

# vlan 20
auto vlan20
iface vlan20 inet manual
	vlan-id 20
	vlan-raw-device bridge0

auto bridge20
iface bridge20 inet manual
	bridge-ports vlan20

# bridge interface
auto bridge0
iface bridge0 inet manual
	bridge-ports bond0
	bridge_stp on
	bridge_fd 2
	bridge_maxwait 0
	bridge-vlan-aware yes
	bridge-vids 1-500

auto bridge0.1
iface bridge0.1 inet static
Users mailing list -- users@xxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxx

[Index of Archives]     [Virt Tools]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux