[00:21] <brandonkal> systemd-networkd-wait-online.service is basically slowing startup by 2min. It's waiting for interfaces which never go up. Is there a way to tell it to ignore all but one interface or otherwise fix it?
[00:27] <rfm> brandonkal, mark the interfaces as "optional: true" in netplan...
[00:28] <brandonkal> I've done that but it seems the system generates random interfaces. There should only be two but I've got a whole lot...
[00:29] <brandonkal> rfm Could snap packages be generating cruft here?
[00:31] <rfm> brandonkal, never seen snap generate net interfaces, container stuff like docker, yes..
[00:31] <rfm> brandonkal, are there systemd network units for these strange interfaces?   if so need to find out who's generating them...
[00:32] <brandonkal> I have docker, but typically when I've done that it only added a docker0
[00:32] <brandonkal> I have br-a8c7c,docker0,eno0,enp7s0f1,ens5f0,ens5f1,lo,veth4bc9,virbr0
[00:33] <brandonkal> And also an IP on br-a8c7ce24a6eb
[00:33] <brandonkal> I did have an eth4 and eth5 earlier as references in my netplan file.
[00:34] <brandonkal> How does one check for that. Thanks rfm
[00:38] <rfm> brandonkal, I'd start with "sudo lshw -C network" to see what those other interfaces are, and put entries in netplan matching on MAC address (not the interface name, which can change around on PCIe) to mark them optional
[00:47] <brandonkal> Thanks. That lists the ones that went missing such as eth3,eth4. Now I recall I have a 4-port pcie eth card that was previously passed through to a VM. Is there a way to disable those ports when not being passed through? rfm
[00:53] <rfm> brandonkal, I guess you could blacklist the driver. not anything I've ever done. also could disable  networking on those interfaces in /etc/sysctl.conf, but I can't tell you the syntax offhand 
[00:56] <brandonkal> Ok thanks, I'll look into those options. It's interesting because based on this: https://unix.stackexchange.com/questions/134483/why-is-my-ethernet-interface-called-enp0s10-instead-of-eth0 I shouldn't be seeing ehtX on some of those ports.
[00:59] <rfm> brandonkal, this is all controlled in the udev rules, perhaps you (or somebody else) tweaked them sometime?
[01:00] <rfm> brandonkal, that's why I use MAC matching, that doesn't change around...
[01:02] <brandonkal> Installed NetworkManager for Cockpit and uninstalled but I suspect it left some cruft behind...
[01:02] <brandonkal> I will be switching to mac
[08:41] <JanC> MAC addresses can change too...
[13:21] <tuxick> usually not
[17:33] <daevski> Trying to setup wifi on ubuntu 20.04 server using netplan and getting some output I'm not understanding... https://pastebin.com/g0fWUBYy
[19:48] <tomreyn> daevski: while this configuration seems to be in line with https://netplan.io/examples/#connecting-to-a-wpa-personal-wireless-network i also seem to remember that systemd-networkd does not actually work well with setting up a wireless connection, and you should be using network-manager for it. this info may be outdated or just wrong, i suggest studying bug reports.
[19:49] <daevski> Can I use NetworkManager on the server edition without a gui?
[19:49] <tomreyn> sure
[19:50] <tomreyn> there is nmcli and nmtui
[19:50] <daevski> Okay, I will try those. Thanks for the tip!
[19:50] <tomreyn> note also that netplan.org points to #netplan for support
[19:51] <tomreyn> https://netplan.io/examples/#using-network-manager-as-a-renderer
[19:52] <tomreyn> "You can specify which network backend should be used to configure particular devices by using the renderer key."
[19:54] <tomreyn> so this seems to suggest that you can use networkd for ethernet and networkmanager for wireless
[19:55] <tomreyn> networkmanager is a bit resource hungry and slow sadly, which is why you may want to only use it where you have to.
[20:09] <daevski> tomreyn great info, thanks again :)
[20:09] <tomreyn> you're welcome