Bsrgvty

I'm struggling with this...

I have a KVM/QEMU hypervisor, running Ubuntu 18.04 server. It manages various VMs, all of them in a DMZ IP class (192.168.63.0/24). All the VMs uses bridged connection br0 as Network source.
The server uses two NIC cards (out of a few more):

• eno1 is connected to our LAN, static IP 192.168.1.221, GW
  192.168.1.99, ecc. (VLAN 1 default)


• eno2 is connected to our LAN at a specific switch port, traffic has to be tagged for VLAN 63 (DMZ's VLAN)

I have this netplan .yaml file (not working):

network:
 version: 2
 renderer: networkd
 ethernets:
 eno1:
 addresses:
 - 192.168.1.221/24
 gateway4: 192.168.1.99
 nameservers:
 addresses: [8.8.8.8,192.168.1.99]
 eno2: 
 dhcp4: no
 bridges:
 br0:
 addresses: [ 192.168.63.221/24 ]
 interfaces: [ vlan63 ]
 vlans:
 vlan63:
 accept-ra: no
 id: 63
 link: eno2

All my VMs have static IPs, all of their network traffic should ideally be bridged to NIC eno2. Before introducing VLANs, it was working this way.

With the configuration above, from the hypervisor I can ping/ssh into VMs in the DMZ, reach Internet, have normal access to LAN. From the VMs in DMZ, no Internet access, full visibility of other VMs in DMZ.

If I change bridge's definition to this:

 bridges:
 br0:
 dhcp4: no
 interfaces: [ vlan63 ]

from the hypervisor I can't no more ping/ssh/reach VMs in the DMZ, but I can ping DMZ's GW (192.168.63.1), accesses to Internet and LAN untouched. So I have no way to connect to my VMs.

I'm obviously doing something all wrong, and I'm not able to sort it out.
Any help or guidance would be great.

Cheers,
rash*

[ Edit ] I finally made it working, details:

• this previously was a 16.04 LTS, freshly upgraded to 18.04 LTS


• I manually enabled netplan, ifupdown was still lying around


• so I purged ifupdown and rebooted


• after reboot, my initial netplan .yaml above works as expected