[00:04] <exalted_shmo> the network adapter being used looks like this in ifconfig: https://paste.ubuntu.com/p/dNTQZFZSzx/
[00:47] <RoyK> is 20.04 still using ufw or has it moved to firewalld? I read debian is moving that way
[00:49] <oerheks> ufw for now, an LTS does not make such huge change
[00:50] <RoyK> debian rarely make large changes either
[00:50] <RoyK> but IIRC ufw doesn't use nft, which is the new thing now
[00:50] <oerheks> true, i would expect such change in minor releases
[00:51] <oerheks> we do have Wireguard
[00:51] <RoyK> I haven't tested 20.04 yet - setting up a vm to look around now :)
[00:52] <oerheks> :-)
[00:52] <oerheks> have fun!
[00:52]  * RoyK usually sticks to debian
[00:52] <quadrathoch2> the move should happen at the latest with the 22.04 lts release ;)
[00:52] <RoyK> I'll test on 20.04 anyway - seems it's in the repos
[02:58] <mybalzitch> so how come ubuntu seems to really want to apply fq_codel limiters to my network interfaces
[03:19] <RoyK> mybalzitch: can you pastebin 'tc -s qdisc show', please?
[03:19] <mybalzitch> it's all noqueue now, but if I delete the root queue after a minute or two it'll go back to a bunch of fq_codel interfaces
[03:19] <mybalzitch> just a sec
[03:20] <mybalzitch> https://paste.ubuntu.com/p/BT9Hk2jMkY/
[03:21] <mybalzitch> is this because of macvlan ?
[03:22] <RoyK> dunno - sorry :)
[06:21] <icey> hey jamespage - thoughts on https://bugs.launchpad.net/ubuntu/+source/python-pylxd/+bug/1887805 ?
[06:21] <ubottu> Launchpad bug 1887805 in python-pylxd (Ubuntu) "[RM] python-pylxd" [Undecided,Incomplete]
[06:22] <jamespage> icey: reasonable push-back - we're not maintaining it and it has wider use than just nova-lxd (which has gone)
[06:22] <jamespage> its just synced from Debian
[06:23] <icey> jamespage: well, I don't know how much wider use it has, at least from a package peprspective
[06:23] <icey> but fair enough
[06:24] <jamespage> icey: its also in universe so no promise of support etc..
[06:24] <icey> jamespage: ah, fair enough - I thought it was in main :)
[06:24] <jamespage> rmadison python-pylxd says otherwise
[06:25] <icey> jamespage: yeah - I went and looked when you said
=== Napsterbater_ is now known as Napsterbater
=== kedar is now known as kedar_apte
=== kedar is now known as kedar_apte
[13:05] <littlebit> hi people, i have installed ubuntu-server along with nextcloud with the help of snap. Now my server will be running only in my local network where I have my custom domain running and I'd like to generate my own certificates and place them accordingly.
[13:05] <littlebit> now, I have googled around a bit and found this site: https://frankindev.com/2019/12/05/setting-up-snap-nextcloud-on-ubuntu/
[13:07] <littlebit> and is it that simple that i place generated files in /var/snap/nextcloud/current ?
[13:07] <littlebit> and then run nextcloud.enable-https custom ./cert.pem ./privkey.pem ./chain.pem
[13:09] <oerheks> yes, browse to that folder, execute command
[13:09] <littlebit> ok
[13:09] <oerheks> but you want certbot, as your certs will expire some day
[13:16] <littlebit> oerheks: since it is my own domain name that only exists at my home, certbot should have a problem with it or?
[13:21] <oerheks> no, but your url shows a possible complication, when those ports are already in use
[13:21] <oerheks> then you would need to do this manually
[13:21] <oerheks> set a cron job with an email as reminder, something.
[13:29] <littlebit> thought of using ansible
[14:14] <Ussat> to do what ?
[17:59] <smoser> paride: around ?
=== xMOPX is now known as XMoPX
=== swills_ is now known as swills