[05:44] <mirespace> good morning
[06:26] <utkarsh2102> mirespace: o/
[06:35] <cpaelzer> hi mirespace and utkarsh2102 and everyone else
[06:37] <sbeattie> ahasenack, cpaelzer: i have acked glusterfs, sorry for the delay.
[06:39] <cpaelzer> thank you so much sbeattie !
[06:40] <cpaelzer> I know we put a lot of pressure on all of you
[06:40] <cpaelzer> let me have a look if there are things to resolve before making changes ...
[07:48] <yurtesen> good morning
[07:53] <yurtesen> utkarsh2102: did you have time to review my fix suggestion? what do you think?
[09:31] <deadrom> greetings. how are ports above 49150 treated by ufw? 
[09:40] <ravage> as a port
[09:43] <deadrom> just as any other? background: I got a device talking to ubu server, control port is, let's say 4114 so I opened that on ufw. Works ok. the whole device does, while the manufacturer tells me it then spawns random ports above 49150 for actual data transmission. Still the device works as intended but I don't know why.
[09:51] <ravage> ufw is just a frontend to (only?) iptables
[09:51] <ravage> what you describe is RELATED,ESTABLISHED in iptables and tcp connections
[10:35] <ahasenack> cpaelzer: I did a quick rebase of https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+ref/jammy-samba-gluster-mir and uploaded to https://launchpad.net/~ahasenack/+archive/ubuntu/samba-gluster-mir so it builds while I'm away
[11:26] <cpaelzer> thanks ahasenack
[11:47] <athos> good morning!
[13:06] <utkarsh2102> athos: o/
[13:07] <utkarsh2102> yurtesen: hey, I've initiated the conversation with the Debian maintainer. Haven't heard from him yet. I'll let you know as soon as I hear from him. 
[14:46] <ahasenack> howdy
[14:54] <utkarsh2102> ahasenack: o/
[14:55] <ahasenack> hi utkarsh2102 
[14:56] <sdeziel> deadrom: what you describe sounds like something involving conntrack helpers which then create entries that will match as RELATED IIRC
[21:30] <yurtesen> utkarsh2102: thanks for the update