Something I worked on today's end result tested:
kcoleman@kcoleman-proj:/etc/netplan$ sudo networkctl status -a 1: lo Link File: /lib/systemd/network/99-default.link Network File: n/a Type: loopback State: carrier (unmanaged) Address: 127.0.0.1 ::1 2: enp0s31f6 Link File: /lib/systemd/network/99-default.link Network File: /run/systemd/network/10-netplan-enp0s31f6.network Type: ether State: carrier (configured) Path: pci-0000:00:1f.6 Driver: e1000e Vendor: Intel Corporation Model: Ethernet Connection (5) I219-LM HW Address: 50:9a:4c:12:60:03 (Dell Inc.) Connected To: KColemanSwitch on port gi2 3: virbr0 Link File: /lib/systemd/network/99-default.link Network File: n/a Type: ether State: no-carrier (unmanaged) Driver: bridge HW Address: 52:54:00:67:34:15 Address: 192.168.122.1 4: virbr0-nic Link File: /lib/systemd/network/99-default.link Network File: n/a Type: ether State: off (unmanaged) Driver: tun HW Address: 52:54:00:67:34:15 5: br0 Link File: /lib/systemd/network/99-default.link Network File: /run/systemd/network/10-netplan-br0.network Type: ether State: routable (configured) Driver: bridge HW Address: a2:5f:6d:de:d0:47 Address: 18.104.22.168 fe80::a05f:6dff:fede:d047 Gateway: 22.214.171.124 (Sonicwall) DNS: 126.96.36.199 188.8.131.52
This took too long but I feel very good that I made it work. I started with Ubuntu 18.04.3 as a total newbie. Got QEMU-KVM installed. And setup my first bridge to the network interface on the server, thus allowing the VM's to connect outside. Feels good to learn.
Next step in learning from the ground up the whole linux sysadmin side of things (as a way of helping me learn more about how to admin a windows environment more deeply) is to remove this from our network, place it into it's own VLAN so it won't harm anything on our network, isolate it basically, and somehow get that to be a DMZ'd VLAN out to the internet, so I can create a virtual network using VM's and everything else. Using this guide as a rough guideline, but trying to modernize it and do it all in Ubuntu instead: