03:27:04 <_xor> domlaut: https://github.com/fujiapple852/trippy
03:27:05 <VimDiesel> Title: GitHub - fujiapple852/trippy: A network diagnostic tool
03:27:42 <_xor> domlaut: https://github.com/GyulyVGC/sniffnet
03:27:43 <VimDiesel> Title: GitHub - GyulyVGC/sniffnet: Application to comfortably monitor your Internet traffic 🕵️‍♂️
03:27:56 <_xor> I've used both of those, and I think both of this do what you're looking to accomplish.
03:29:05 <_xor> CrtxReavr: Don't remember of the top of my head, but I'm curious now. Going to look when I go back into the basement.
06:21:19 <dch> _xor these are both excellent, thanks for the tip
06:42:23 <ExclamationPoint> q
06:42:26 <ExclamationPoint> lol
14:12:08 <wikan> hi, i am working on my installation script
14:12:25 <wikan> may i ask if it is possible to pass the password string to geli command?
14:13:08 <wikan> i ask for encryption password using dialog window and i don't want to type it while installation process
14:13:52 <wikan> this is my command: geli init -b -s4096 -l256 /dev/label/${iGeliLabel}
14:17:26 <RhodiumToad> -J filename   will take the passphrase from a file (can't contain newlines - only the first line of the file is taken)
14:18:57 <wikan> @RhodiumToad can I remove this file after geli attatch?
14:18:58 <EdnaLuv> TSA Delta Flight 194 Ad - Be Careful What You Eat before Your Flight! A TSA public service ad urges air passengers to be mindful of what they eat before their flight to avoid another Delta 194 diarrhea spray incident. https://justpaste.it/Delta_194_TSA/
14:19:00 <VimDiesel> Title: TSA Delta Flight 194 Ad - Be Careful What You Eat before Your Flight! - JustPaste.it
14:23:47 <CmdLnKid> wtf
14:25:32 <RhodiumToad> wikan: sure
14:26:52 <wikan> great, thank you so much :)
14:28:53 <PyR3X> anyone able to get a Garmin watch usb storage to work on FreeBSD?
14:29:19 <PyR3X> ugen0.8: <vendor 0x091e product 0x0003> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (500mA)
14:34:13 <RhodiumToad> PyR3X: is it presenting as a block storage device, or as MTP or something?
14:41:31 <PyR3X> RhodiumToad: I think it's like an Android USB
14:41:51 <PyR3X> Linux/Windows just pops up like a normal USB storage
14:44:03 <RhodiumToad> what does  usbconfig -d ... dump_all_desc   show?
14:44:19 <RhodiumToad> e.g.  -d ugen0.8
15:08:28 <beowuff> Should autotrim on zfs be set for nvmes?
15:10:23 <Freaky> https://freshbsd.org/freebsd/ports/commit/82f691 yay
15:10:24 <VimDiesel> Title: FreeBSD / ports / 82f691 / security/portacl-rc: Add new port - FreshBSD
15:39:11 <CmdLnKid> if were compiling all the time with obj directories ... why is there a warning that /usr/src is a read-only filesystem ?
15:40:46 <CmdLnKid> forever now i mount nullfs if ya will /usr/src ro from a zfs filesystem. why would it need to be writable by any means or less thereof by freebsd methods of using obj ?
15:41:37 <CmdLnKid> these warnings are moot bs
15:42:42 <CmdLnKid> for further context "writeable" /export/usr/src. unwriteable is /usr/src
15:44:12 <CmdLnKid> i don't comprehend why these are there and why when using a obj directory we should be concerned when compilation does not require writing to /usr/src at all. thats just dirty in itself
15:44:25 <RhodiumToad> CmdLnKid: the warning is a bug in make
15:44:32 <CmdLnKid> k
15:44:56 <CmdLnKid> ill look further into make
15:45:17 <CmdLnKid> irratations ... ya know
15:45:20 <RhodiumToad> it wants to check whether the obj dir is writable, but it's checking it before actually changing it
15:46:07 <CmdLnKid> seems make went a little to far on its checks instead of doing its most simplest job
15:46:10 <CmdLnKid> just do it
15:49:24 <CmdLnKid> to an unexperienced user i see this as a wtf moment
15:49:51 <CmdLnKid> not much to worry over but yet nothing that should be there
16:23:22 <Soni> does freebsd support RFC 6525?
16:24:52 <CmdLnKid> soni, sctp has been here a very long time
16:25:28 <CmdLnKid> reconfiguration should be a option
16:26:28 <Soni> how do you use SCTP_ADD_STREAMS? we don't see it in the manual?
16:26:30 <CmdLnKid> support may vary for important options
16:27:22 <CmdLnKid> what are you seeing vs what you expect ?
16:27:41 <Soni> can't find SCTP_ADD_STREAMS in manual
16:38:06 <CmdLnKid> as close as i see to that is tracking global addresses but adding streams does not seem to be something that is implemented. " not definate word" per my search
16:38:24 <CmdLnKid> so in otherwords.. np
16:38:29 <CmdLnKid> no
16:38:47 <CmdLnKid> as in just not handled
16:39:19 <CmdLnKid> afaict
17:05:10 <Soni> ah that's unfortunate :(
17:07:31 <meena> Soni: might want to direct your questions at freebsd-net@
17:07:53 <CmdLnKid> don'nt get me wrong thats just a cursory glance but nothing is sticking out to me right now. whats your usage tho ?
17:08:25 <CmdLnKid> its just i don't see it where i think it would be
17:08:48 <meena> IIRC, a proxy of some sort
17:09:36 <CmdLnKid> freebsd-net@ tho may raise the proper eyebrows
17:12:56 <RhodiumToad> afaict, SCTP_ADD_STREAMS was added in 2012 or so
17:32:12 <kevans> Soni: fwiw, my understanding is that freebsd is the SCTP reference platform
17:33:07 <kevans> SCTP_ADD_STREAMS seems to be implemented, not sure why its' not documented
17:34:02 * kevans scrolls down and sees RhodiumToad confirmed already
17:34:14 <RhodiumToad> heh
17:34:18 <Soni> oh okay
17:34:30 <Soni> is it okay to open a few hundred thousand AF_UNIX streams?
17:34:58 * RhodiumToad notes that D40961 is not committed yet
17:35:42 <RhodiumToad> Soni: why would you want to, and do you have the RAM for it?
17:36:10 <Soni> RhodiumToad: for pain reasons. how much RAM does a socket take?
17:36:38 <RhodiumToad> you need the limits on file descriptors to be high enough
17:36:53 <Soni> yeah
17:36:57 <RhodiumToad> the RAM will depend on how much buffer space ends up being needed
17:37:18 * kevans slaps a threat of a timelimit on D40961
17:37:41 <Soni> usually, how much RAM should be expected per socket?
17:40:09 <RhodiumToad> "it depends", but consider that when you write data to the socket and the reader isn't immediately ready to receive it, it will be buffered
17:40:35 <Soni> *nod*
17:41:06 <RhodiumToad> the size of that buffer is capped by kern.ipc.maxsockbuf and set by SO_SNDBUF/SO_RCVBUF etc.
17:41:37 <RhodiumToad> default for maxsockbuf seems to be 2MB
17:41:51 <Soni> yeah honestly we wouldn't come anywhere close to 100k in practice
17:42:01 <RhodiumToad> but there's also global caps on the amount of network memory
17:42:37 <RhodiumToad> kern.ipc.maxmbufmem
17:43:18 <RhodiumToad> which looks like it defaults to about half of physmem
17:43:27 <Soni> so basically it'd take a TB of RAM
17:43:58 <Soni> fair enough
17:52:08 <RhodiumToad> that would be the worst case
17:53:06 <RhodiumToad> if there's not a ton of buffered data, then there'll just be memory for various data structures, maybe in the hundreds of bytes per socket
19:12:32 <PyR3X> I see the default Wireshark is not built with sshdump enabled by default. Is my only option to build from ports to enable it?
19:54:11 <meena> PyR3X: the alternative is to badger the maintainer until they give in
21:32:19 <vkarlsen> Which license is this? It's similar to BSD3CLAUSE, but not quite it -- https://github.com/agateau/nanonote/blob/master/LICENSE
21:32:20 <VimDiesel> Title: nanonote/LICENSE at master · agateau/nanonote · GitHub
21:36:22 <RhodiumToad> looks like SPDX has it as BSD-3-Clause-Clear
21:36:31 <RhodiumToad> https://spdx.org/licenses/BSD-3-Clause-Clear.html
21:36:32 <VimDiesel> Title: BSD 3-Clause Clear License | Software Package Data Exchange (SPDX)
21:38:12 <vkarlsen> RhodiumToad: That does indeed look like the one, thanks
21:38:21 <V_PauAmma_V> Beat me to it.
22:00:01 <Ronis_BR> Hi! I am planning to use FreeBSD to install a gitlab. I know that we have a gitlab package. The problem is with updates. Gitlab requires a very linear update path. Let's say I install 16.2. Then, 17 is launched. However, to update to 17, I need to update first to 16.3. If I missed the update when 16.3 was in the repository, how can I obtain the old 16.3 version so that I can follow the update
22:00:03 <Ronis_BR> path?
22:00:30 <Ronis_BR> AFAIK, FreeBSD repositories does not host old binary versions right?
22:02:03 <RhodiumToad> that is correct as far as I know
22:04:57 <kevans> right, we mercilessly purge previous versions from the repo with each build
22:05:24 <kevans> it's why you can get into a glorious situation where you lose firefox, for instance, if you're not paying attention
22:27:32 <thedaemon> do not unplug a Wacom device, X will freak out.