[00:34] <echelon> fanatic26: show your config
[16:04] <fanatic26> network:
[16:04] <fanatic26>     ethernets: 
[16:04] <fanatic26>         enx00e04c681826:
[16:04] <fanatic26>             dhcp4: false
[16:04] <fanatic26>             addresses:
[16:05] <fanatic26>             - 192.168.1.246/24
[16:05] <fanatic26>             nameservers:
[16:05] <fanatic26>              addresses: [8.8.8.8,8.8.4.4]
[16:05] <fanatic26>     version: 2
[16:05] <fanatic26>     wifis:
[16:05] <fanatic26>         wlp1s0:
[16:05] <fanatic26>             access-points:
[16:05] <fanatic26>                 XXXXXX:
[16:05] <fanatic26>                     password: XXXXXXXX
[16:18] <echelon> fanatic26: i think nameservers: addresses: field needs to be separated by a list as well
[16:19] <echelon> ie, - 8.8.8.8 \ - 8.8.4.4
[16:20] <echelon> and does wifis use dhcpd?
[20:36] <fanatic26> I pulled that nameserver addresses syntax from a netplan.io example
[20:37] <fanatic26> The wifi can actually stay on DHCP, which is what is currently active on the machine. This was as far as I had gotten in testing