[06:54] <makara> exit
[12:43] <coreycb> cpaelzer: fyi kashyap in #openstack-nova opened this for the firmware descriptor files issue we discussed - https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1836859
[12:46] <cpaelzer> thanks coreycb I'll ping dannf who usually takes care of edk2
[12:46] <coreycb> cpaelzer: ok thank you
[15:24] <teward> for 18.04 servers, is it possible to roll custom nameservers with DHCP and ignore the DHCP assigned nameservers?
[15:24] <teward> i forget :P
[15:25] <teward> (this is for LXD containers which get DHCP'd network data)
[15:43] <lordcirth> teward, yes
[15:44] <lordcirth> teward, using netplan, you need dhcp4: true but dhcp4-overrides: use-dns: false
[15:45] <lordcirth> Assuming the docs are correct, haven't tried it
[17:00] <seveneleven> how can i configure a NIC to use vlan id 2 using ubuntu preseed?
[17:01] <lordcirth> seveneleven, the NIC is on a tagged port, and you need it to create a vlan2 interface and configure networking on that?
[17:01] <seveneleven> lordcirth, it's on an untagged vlan 2 port
[17:01] <seveneleven> lordcirth, so i should just configure pvid 2 on that port instead?
[17:02] <lordcirth> seveneleven, if it's untagged, why would you need to do anything different?
[17:02] <seveneleven> wait, let me rethink why it didn't work last time
[17:02] <seveneleven> ok i described it wrongly
[17:03] <seveneleven> it's a vm on a hypervisor, now the hypervisor is connected to a tagged vlan 2+3 port, last time i created a br.2 bond and got the vm working with an internet connection
[17:04] <lordcirth> seveneleven, so the hypervisor should expose an untagged port to the VM, and put it on vlan 2.
[17:04] <seveneleven> yeah
[17:05] <lordcirth> We do that with LXC containers at $WORK
[17:05] <seveneleven> i use libvirt kvm qemu
[17:06] <lordcirth> seveneleven, ok, so what problem are you having?
[17:06] <seveneleven> i wonder how I can configure br.2 in ubuntu's preseed
[17:07] <lordcirth> seveneleven, if the hypervisor is providing an untagged eth0, why would you need to?
[17:08] <seveneleven> hmm, not sure
[17:08] <seveneleven> last time I simply created a br0 bond, and got no route to WAN, once I created the br.2 explicitely it worked
[17:08] <seveneleven> thats why i thought i need it
[17:09] <lordcirth> seveneleven, then your hypervisor was passing in a tagged port.
[17:09] <seveneleven> hmm
[17:13] <seveneleven> lordcirth, i just checked and my hypervisor uses a bridge between the vm http://dpaste.com/0NB8V3S
[17:13] <lordcirth> seveneleven, ok, so what is br0 tied to? 'brctl show br0'
[17:14] <seveneleven> enp0s31f6, vnet1 and vnet2
[17:15] <lordcirth> seveneleven, and enp0s31f6 is the tagged one with vlans 2+3, right?
[17:16] <seveneleven> yeah
[17:16] <lordcirth> seveneleven, so, br0 is tagged, and your VM's interface is therefore tagged.
[17:16] <seveneleven> enp0s31f6 is like eth0
[17:16] <seveneleven> ohh gotcha
[17:16] <lordcirth> What you want is to create a enp0s31f6.2 interface on the host, which is untagged vlan2
[17:17] <lordcirth> Then make a br2 that is tied to that, and put your VM on that.
[17:17] <seveneleven> oh that's clever
[17:18] <lordcirth> Our LXC servers essentially do this - I use Salt to generate the netplan configs for a list of vlan IDs, and we get a iface.422 tied to a br422, and make containers on br422, etc.
[17:18] <seveneleven> wow then you end up with many many interfaces
[17:19] <lordcirth> yeah, but, automation :P
[17:19] <seveneleven> im going to try that, but just out of curiousity, would it have been possible to configure ubuntu to br.2 via the preseed? i assume yes, but it's probably more complicated
[17:20] <lordcirth> It is probably possible, but I don't know how.
[17:20] <lordcirth> Well, you could drop a netplan file in, but that wouldn't get you networking in the installer.
[17:25] <seveneleven> mhmm
[17:26] <seveneleven> i keep it simple and stupid and try your solution :-)
[17:36] <seveneleven> yeah seems custom bonds are not really supported for ubuntu installer https://askubuntu.com/questions/528211/can-d-i-ubuntu-installer-configure-bond-vlan-and-second-network-interface-dur
[17:53] <seveneleven> lordcirth, should i configure an ip on the iface.422?
[17:53] <seveneleven> or just "create" it and configure the IP on the br422?
[17:53] <seveneleven> im using /etc/network/interfaces for configuration
[17:54] <lordcirth> seveneleven, you don't need an IP on the host side to have the VM work
[17:54] <seveneleven> mmhm
[17:55] <seveneleven> so I just add `auto enp0s31f6.2` and `auto br2` inside /etc/network/interfaces?
[17:56] <seveneleven> (and use brctl to add enp0s31f6.2 to br2)
[18:00] <lordcirth> seveneleven, this is what I have: https://gist.github.com/lordcirth/a4c3b71a0f6ec29be704a440ceb5961e
[18:01] <lordcirth> brctl is transient, you want it all in files.
[18:01] <seveneleven> aaah right, brctl forgets it after reboot
[18:01] <lordcirth> the vlan device needs to be explicitly tied to the interface, and the bridge to the vlan
[18:04] <anton4i3ke> Im seveneleven, seems like my network died after restarting its service hehe 😊
[18:05] <lordcirth> anton4i3ke, it is easy to make a mistake when doing this
[18:06] <sarnold> anton4i3ke: you might have missed < lordcirth> the vlan device needs to be explicitly tied to the interface, and the bridge to the vla
[18:09] <anton4i3ke> Yeah
[18:09] <anton4i3ke> Going to troubleshoot now
[18:12] <sarnold> anton4i3ke: due note that it's entirely normal for all existing connections to an IP address to drop when you add a bridge to a NIC (or add a NIC to a bridge?) -- on linux the IP is associated with the *bridge*, not the nic..
[18:13] <coreycb> jamespage: sahid: i think i have the remaining py2 drops done. once we get the RM bugs handled we should know for sure.
[19:27] <seven-eleven> lordcirth, hmm i dont get a route between the vm and the hypervisor
[19:28] <seven-eleven> how does your interfaces config look like on the vm?
[19:28] <lordcirth> seven-eleven, just eth0 as a static IP
[19:28] <seven-eleven> hmm i tried that
[19:28] <seven-eleven> i worry this is a libvirt issue
[19:28] <lordcirth> seven-eleven, can you pastebin your /etc/network/interfaces on the host?
[19:28] <seven-eleven> ok
[19:31] <seven-eleven> lordcirth, sorry i need a while, i have X running in the basement now, so i cant connect to the X remotely anymore, and i dont know what display manager i used so i cant stop it :D
[19:31] <lordcirth> seven-eleven, lol. you can kill X?
[19:31] <seven-eleven> i tried killall X
[19:31] <seven-eleven> i run `startx` in the basement
[19:32] <lordcirth> seven-eleven, killall Xorg
[19:32] <seven-eleven> let me try
[19:32] <seven-eleven> not found hmm
[19:32] <seven-eleven> i can just reboot, but im curious
[19:33] <seven-eleven> i reboot
[19:38] <seven-eleven> i cant pastebin because i dont have a connection, so I write it 1:1 http://dpaste.com/0R0RKCT
[19:40] <lordcirth> seven-eleven, is that the host or the guest?
[19:40] <seven-eleven> ah thats the guest
[19:40] <seven-eleven> a moment
[19:41] <seven-eleven> https://termbin.com/1ixi
[19:41] <seven-eleven> ohhh
[19:41] <seven-eleven> found the mistake!
[19:42] <seven-eleven> it's actually libvirt issue
[19:42] <seven-eleven> libvirt automatically adds vnet1 to br5, so now we have enp0s316.5 and vnet1 inside br5
[19:43] <lordcirth> And you wanted 2?
[19:43] <seven-eleven> nope
[19:44] <lordcirth> I thought you wanted vlan 2, but there's no enp0s31f6.2. Was it 5 you wanted?
[19:44] <seven-eleven> ah, two interfaces dont matter regarding tagged vlan, would have to be two vlans inside br5 to be considered tagged?
[19:44] <seven-eleven> i wanted vlan 2
[19:44] <seven-eleven> but the problem is if I set it to vlan 2 then br0.2 stops working
[19:45] <lordcirth> seven-eleven, if the switch port is tagged, it's tagged, even if there's only 1 vlan
[19:45] <seven-eleven> i had to delete enp0s31f6.2 to get my LAN back working
[19:45] <seven-eleven> gotcha
[19:45] <seven-eleven> so I need to get the vm to use vlan 2
[19:46] <lordcirth> But the host also needs an IP on vlan 2?
[19:46] <seven-eleven> that means I have to remove br0.2, rewrite my iptables to source through br2
[19:46] <seven-eleven> yes
[19:46] <seven-eleven> the host itself needs an ip
[19:46] <seven-eleven> i would add it to br2 right?
[19:47] <lordcirth> I would create a enp0s31f6.2, which is an untagged interface. Then tie it to 'br2'. Then set an IP for the host on br2, and attach the VM's eno3 to br2 as well
[19:47] <seven-eleven> so i would do something like http://dpaste.com/00YW181 ?
[19:48] <seven-eleven> ok i retry this :-)
[19:50] <seven-eleven> lordcirth, should I move br0.3 to enp0s31f6.3 respectively or leave it as br0.3?
[19:50] <seven-eleven> br0.3 is not used for guests, br0.3 goes directly to the WAN router
[19:50] <seven-eleven> br0.3 is tight via br0 to enp0s31f6
[19:51] <seven-eleven> not sure if br0.3 can coexist with using enp0s31f6.2
[19:51] <seven-eleven> i will just try
[19:53] <lordcirth> seven-eleven, the paste looks correct, assuming you use '2' instead of '5' and that the enp0s31f6.2 interface is also correct
[19:53] <seven-eleven> lordcirth, ok
[19:54] <seven-eleven> lordcirth, so i leave br0.3 tied to br0
[19:54] <seven-eleven> and use now br2
[19:54] <lordcirth> I am not sure how your network is set up for br0.3
[19:54] <seven-eleven> br0.3 is in the subnet of my WAN router
[19:55] <seven-eleven> br0 is tied to eth0
[19:55] <seven-eleven> br2 is now tied to eth0.2
[20:49] <seven-eleven> lordcirth, works fine. now it's properly configured, so much easier to just configure eth0 on the guests, and makes auto installing easier
[20:49] <seven-eleven> thx! :-)
[20:49] <lordcirth> seven-eleven, great, you're welcome