[02:32] <teward> zzlatev_: you're welcome (sorry I had errands all day)
[02:32] <teward> zzlatev_: there should be an updated version now :P
[09:04] <super_koza> Hi! Each time when I restart my server, or when network parameters change, the server isn't able to get a new IP address. I have to manually run dhclient in order to get an IP address.
[09:04] <super_koza> Any idea what might be the issue here and how to solve it?
[10:05] <blackflow> super_koza: what's your network configuration like? pastebin?
[10:23] <super_koza> I haven't done anything network wise, after installing the OS.
[10:23] <super_koza> What should I paste?
[10:25] <blackflow> super_koza: your network configuration. if you're running a server, you must know what that is.
[10:29] <super_koza> well I am not experienced, but I am willing to learn :)
[10:29] <super_koza> or at least I am trying to learn
[10:31] <blackflow> super_koza: default on ubuntu is netplan.io which is just a configuration abstractor for a backend. on server editions, the backend is networkd. can you can pastebin systemd-networkd config? It should be under /etc/systemd/network/<files here>
[10:31] <blackflow> also please pastebin files under /etc/netplan/
[11:13] <zzlatev_> teward: yes it is, once again - tnank yo for everything
[13:35] <super_koza> @blackflow: Sorry, I was AFK
[13:37] <super_koza> The folder /etc/systemd/network is empty, there is nothing there :)
[13:37] <super_koza> In /etc/netplan/ there is only 1 file: 01-netcfg.yaml
[13:39] <super_koza> Here it is: https://pastebin.com/tf9cQJk0
[13:41] <super_koza> This is the network interface that I use: https://pastebin.com/4RcvHs40
[13:41] <super_koza> Notice that it is called eno1
[13:45] <blackflow> super_koza: that's your problem. netplan is configuring enp0s25 instead. I'd say just change that to eno1 in that netplan file  but the $32k question here is why did it change.
[13:46] <super_koza> ok, thanks a lot
[13:47] <super_koza> I will give it a try :)
[13:47] <blackflow> run `netplan apply` after you change its config. might disconnect you if you're doing this over ssh.
[13:48] <super_koza> The only explanation I have for the change is that it might have picked up a small USB dongle when I attached a monitor to it...
[13:49] <blackflow> that's possible I suppose. there have been bug reports of NICs changing names after random hardware is added, removed. but usually it'd be something like different slot in the enp0sX form
[13:49] <blackflow> nevertheless, you can force and bind the NIC name via its MAC address.