[02:25] <fattywompus> if I restart the SSH daemon with "sudo systemctl restart sshd" while connected through SSH does it seem funny that I'm not disconnected?
[02:27] <mybalzitch> the daemon forks off sessions
[02:38] <fattywompus> so are you saying I'm still on a session running on the old sshd_config file I just edited and any new sessions will use the new config?
[02:46] <fattywompus> I guess not like it matters from a practical standpoint, just curious.  And thanks for the answer.  When it didn't go down I began to wonder if I was doing something wrong or working off of bad info
[02:48] <mybalzitch> yes, any changes to the daemons configuration will be reflected in new connections, nothing happens to your already established connection, as I understand it
[14:40] <jaguardown> Hi, what's the difference between 01-netcfg.yaml and 99-config.yaml? 01-netcfg.yaml has a dhcp config for my ethernet but 99-config.yaml has a static config. This server used to be 18.04, I would have added the static config and I also upgraded to 20.04. Can I delete 01-netcfg.yaml?
[14:44] <jaguardown> I'm just gonna say yes unless someone says otherwise
[14:49] <compdoc> delete the one that isnt loading, or save it
[14:49] <compdoc> or delete the one you dont want loading
[14:56] <jaguardown> compdoc ok that's what I figured, I just renamed it with .bak and put it in a tmp folder
[14:56] <compdoc> check ownership and perms
[14:57] <jaguardown> they're 755 for the tmp directory and 644
[14:57] <jaguardown> for the files
[14:57] <jaguardown> owned by root
[14:58] <compdoc> sounds right
[17:50] <jaguardown> Can someone help me? I have KVM running on Ubuntu Server 20.04. I want the VM's to have a bridge connection. Here's my /etc/netplan/99_config.yaml: https://pastebin.com/gyhN9WGc it works great when I create the bridge in this file and run "sudo netplan apply" but as soon as I reboot the server it breaks the network connection, everything looks the same as far as IP addresses but I can't reach any IP
[17:50] <jaguardown> addresses. One possibly unrelated note is that the guests aren't configured to automatically start on host reboot.
[18:20] <compdoc> jaguardown, I use bridges. let me take a look. do you have more than one nic in the server?
[18:21] <tomreyn> dhcp on the bridge, would that be needed / correct?
[18:25] <compdoc> dhcp service, or for the bridge to confi itself?
[18:26] <compdoc> oh, let me look
[18:28] <compdoc> I would not use dhcp to define the bridge, but I use seperate nics and the bridge does not need an ip address.
[18:29] <compdoc> your mileage may vary
[18:30] <compdoc> if you have one nic, it would have an ip add assigned so you can share the nic
[18:32] <compdoc> because its a server, might be best to define the ip, ect manually in the yaml
[19:30] <fattywompus> Is it necessary to install tcp_wrappers or tcpd?  I don't see it installed but yet I have etc/hosts.allow and etc/hosts.deny which are said to be it's configuration files.  Does editing the etc/hosts files have some different result without tcpd?
[19:41] <RoyK> some daemons read hosts.{allow,deny} themselves without needing tcpwrappers
[19:42] <RoyK> I haven't used tcpwrappers for a couple of decades and I don't really miss it
[19:50] <fattywompus> So I can pretty much put whatever rules I would put in the hosts files as if I had tcpwrappers without bothering with tcpwrappers and some other already existing daemons will essentially do the same thing?  Just working with SSH at the moment but guessing this applies to other protocols as well?
[19:59] <tomreyn> ignore tcp wrappers, use a firewall if you need / want.
[20:13] <fattywompus> Sounds good.  Thanks for the help guys o7