Hi, In the example, cloudbr1 uses eth0.200 which means the packets will have vlan tag 200.
If you have only 1 physical interface, you can use the same bridge (cloudbr0) for mgmt/public/guest, etc.Not ideally, but it should work. When you create the zone, set the "kvm traffic label" of physical networks to cloudbr0 -Wei On Thu, 1 Feb 2024 at 19:19, Javi Moncayo <[email protected]> wrote: > Should I use eno1 for cloudbr1 for public access then… and eno2 for > private network? > > From the documentation I see they're referring to "eth0" in both cases. > Am I misinterpreting something? > > > auto lo > iface lo inet loopback > > # The primary network interface > auto eth0 > iface eth0 inet manual > > auto eth0.200 > iface eth0 inet manual > > # management network > auto cloudbr0 > iface cloudbr0 inet static > bridge_ports eth0 > bridge_fd 0 > bridge_stp off > bridge_maxwait 1 > address 192.168.42.11 > netmask 255.255.255.240 > gateway 192.168.42.1 > dns-nameservers 8.8.8.8 8.8.4.4 > dns-domain lab.example.org > > # guest network > auto cloudbr1 > iface cloudbr1 inet manual > bridge_ports eth0.200 > bridge_fd 0 > bridge_stp off > bridge_maxwait 1 > > Sent from Outlook for Android<https://aka.ms/AAb9ysg> > ________________________________ > From: Wei ZHOU <[email protected]> > Sent: Thursday, February 1, 2024 5:40:35 PM > To: [email protected] <[email protected]> > Subject: Re: Why do the bridges kill the network witht this config? > > Two bridges (cloudbr0/cloudbr1) with same interface (eno1) ? > > 在 2024年2月1日星期四，Javi Moncayo <[email protected]> 写道： > > > Hi guys, > > > > I am using Ubuntu 20 I have two interfaces. One physical (eno1) with > > internet access, and eno2 is a vRack for the private network. > > > > On the configuration below, if I use eno2 as interface for both bridges, > I > > can create VMs and they can ping each other but I do not have internet > > access. However, if I set the interface to eno1, the network crashes... > > > > What am I missing? How should my configuration look like? > > > > Thanks in advance! > > > > network: > > version: 2 > > ethernets: > > eno2: > > dhcp4: no > > addresses: > > - 192.168.0.1/16 > > eno1: > > accept-ra: false > > addresses: > > - xxxx:xxxx:xxx:xxxx::/56 > > dhcp4: true > > match: > > macaddress: ac:1f:6b:df:50:78 > > nameservers: > > addresses: > > - xxxx:xxxx:x:xxx::1 > > bridges: > > cloudbr0: > > addresses: [192.168.1.1/16] > > gateway4: 192.168.255.255 > > nameservers: > > addresses: [8.8.8.8] > > interfaces: [eno1] > > dhcp4: false > > dhcp6: false > > parameters: > > stp: false > > forward-delay: 0 > > cloudbr1: > > interfaces: [eno1] > > dhcp4: false > > dhcp6: false > > parameters: > > stp: false > > forward-delay: 0 > > > > eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > > inet xx.xxx.xx.xxx netmask 255.255.255.0 broadcast > xx.xxx.xx.xxx > > inet6 xxxx::xxxx:xxxx:xxxx:xxxx prefixlen 64 scopeid 0x20<link> > > inet6 xxxx:xxxx:xxx:xxxx:: prefixlen 56 scopeid 0x0<global> > > ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet) > > RX packets 441753 bytes 142093871 (142.0 MB) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 425365 bytes 66792387 (66.7 MB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > eno2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > > inet 192.168.0.1 netmask 255.255.0.0 broadcast 192.168.255.255 > > ether ac:1f:6b:df:50:79 txqueuelen 1000 (Ethernet) > > RX packets 29006 bytes 2390888 (2.3 MB) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 24554 bytes 1715980 (1.7 MB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > >
