00:21:10 <ketas> always run ntp!
06:53:33 <kerneldove> if i run a command `jexec -l myjail acommand < /tmp/foo.txt` is it pulling foo.txt from the /tmp of the jail host, or the /tmp from within the jail?
07:07:28 <divlamir> Don't you mean sth like `jexec -l myjail sh -c "cmd args < /tmp/foo"`
07:08:03 <nimaje> kerneldove: that < redirect is a feature of your shell, so it is reading from the host, as your shell doesn't even have an idea what the executable does
07:08:38 <kerneldove> nimaje, i knew it!
07:08:55 <kerneldove> so pull from within the jail, i guess i need to format the invocation like how divlamir said?
07:09:42 <nimaje> yes, then a shell started inside the jail handles the redirect
08:12:15 <kerneldove> ty guys
08:18:24 <kerneldove> there any probs with making huge swap space like 128g? other than burning up disk
08:32:13 <nimaje> I don't think there should be problems, but why would you need that?
08:34:26 <kerneldove> maybe im feeling cute and might just overcommit ram
13:20:54 <f451> hi, is pf capable of layer 2 filtering yet, or are there plans to have it? ie filtering by MAC address. The openbsd pf is, but freebsd pf AIUI was forked from openbsd pf around openbsd 4.8
13:40:46 <nimaje> the ETHERNET FILTERING section in pf.conf(5) reads like it can
13:48:10 <Ltning> w00, packages for current exist again :D Poor cluster...
14:15:01 <divlamir> f451, looks the opposite when comparing FreeBSD and OpenBSD man pages. FreeBSD supports it while Openbsd dropped it.
14:16:08 <divlamir> Although for something as easily spoofed, I don't see great use
14:30:02 <f451> divlamir: it's use case is for a bhyve server filtering for bridge, but bypassing filtering for tap (also a bridge member)
14:34:50 <f451> i remember kp@ saying something about it a while ago. openbsd man page indeed says layer-3 and layer-4. i thought i saw an example on the lists of layer-2 hence the question
14:35:06 <f451> (openbsd)
14:36:18 <f451> looks like i need to think a bit more deeply before moving this middleware box ;)
14:47:04 <f451> nimaje & divlamir yes you're right, it appears to be the opposite. tyvm :D
15:12:28 <divlamir> for the exact syntax, look at the bnf grammar at the bottom of the page -- ether-rules
15:22:22 <f451> tyvm
17:20:11 <phryk> where do i find eol dates for currently supported releases?
17:21:07 <nxjoseph> phryk: https://www.freebsd.org/security/#sup
17:21:50 <phryk> nxjoseph: thanks.
17:22:01 <nxjoseph> phryk: you're welcome :)
17:22:48 <phryk> so i'll have to update to 14.3 before 15.0 comes out if i want to avoid running an EOLd version (again)… and within this month.
17:23:12 <phryk> is there a tool that will tell me this info, either in the base-system or as port?
17:23:49 <nxjoseph> phryk: IIRC, FreeBSD itself (maybe pkg?) warns you if you are reached to eol
17:23:53 <phryk> because i keep running into EOLs only when poudriere refuses to build packages. to keep proper track of this, i'd really like to just integrate that shit into my monitoring.
17:24:17 <phryk> nxjoseph: yeah, but i want to know *before* i actually run EOLd versions on my entire infra…
17:24:39 <nxjoseph> phryk: i suggest keeping an eye on the dates then
17:24:47 <nxjoseph> i also didn't understand why you need to do it before 15 released
17:25:44 <phryk> according to security/#sup, 14.2 EOLs on september 30th. 15.0 release is scheduled for december.
17:26:14 <phryk> so i either upgrade to 14.3 or run an EOLd version for at least 2 months.
17:26:50 <nxjoseph> what are you on right now
17:26:53 <phryk> 14.2
17:27:10 <phryk> i mean why else would i care about when 14.2 is EOLd?^^
17:27:26 <nxjoseph> you can keep using it until 30th of that month, then you can upgrade to 14.3, then wait for it's eol too, then update to something newer version, maybe 14.4 or 15.0
17:28:18 <phryk> yeah, sure. my main issue is that i want that info in a machine-readable form so i can integrate it into my monitoring so i don't have to manually keep track of this.
17:28:48 <nxjoseph> i couldn't find ports' made for this purpose
17:29:31 <phryk> not really surprised. IMO freebsd-version would probably be the most fitting place to integrate this as a feature…
17:35:04 <nxjoseph> https://endoflife.date/freebsd
17:35:42 <nxjoseph> https://endoflife.date/api/v1/products/freebsd/
17:35:44 <nxjoseph> there is json api
17:35:50 <nxjoseph> maybe one can create a program
17:37:04 <phryk> mhh, IMO this shouldn't require network access – i.e. the system should be able to report this itself. i'll sit on this a bit and maybe open a report on bugs.freebsd.org if i can get some coherent thought about it together.
17:37:58 <phryk> but thanks for the link, that definitely goes into my bookmarks^^
17:41:03 <nxjoseph> glad i could help a bit
17:42:36 <phryk> oh you very definitely did. i think this would be a very legitimate feature request. and i'd likely be down to write a prometheus exporter for it if it's implemented.
17:45:40 <phryk> which reminds me that i want to look into libpkg because i want an exporter that reports outdated and insecure installed packages.
17:45:49 <nimaje> phryk: in general, point releases are EOL three month after the next point release for that major release is out as noted at the bottem of the already linked page https://www.freebsd.org/security/#model
17:46:12 <phryk> these two things are probably the biggest two holes to be filled in my monitoring.
17:46:53 <phryk> nimaje: but in practice the actual dates sometimes differ and are then communicated only on freebsd.org, right?
17:48:05 <nimaje> I think they only get rounded to the end of month
17:52:04 <phryk> nimaje: so if i understand correctly, i can check if a release/<major>.<minor+1> tag exists and if it does, it's creation date + 3 months (rounded to end of month) is reliably the EOL date of the currently run point release?
19:20:20 <divlamir> phryk: here's a oneliner
19:20:25 <divlamir> tag=release/14.3.0; date -j -v+4m -v1d -v-1d -f %s "$(git show --no-patch --format='%ct' "$(git rev-list -n 1 "$tag")")" +%Y-%m-%d
19:21:03 <divlamir> Well, a two-liner techically XD
19:28:35 <phryk> divlamir: thanks, but i'd rather do it through a proper api :P
20:16:44 <tuaris> I ran into an odd issue with Fuse and Mate desktop.  I reported the bug here: https://github.com/mate-desktop/caja/issues/1850.  However, I just realized something in the`df` output on the CLI.  It says "df: File system /media/Backups does not have a block size, assuming 512."
20:17:00 <tuaris> That makes me think the problem might be with FreeBSD or the fuse driver
20:17:17 <tuaris> or maybe even fuse itself?
21:12:26 <swee> Do i need any extra packages to mount a virtio 9p filesystem on freebsd 14.3? I'm trying to run `mount -t 9p -o trans=virtio -o version=9p2000.L /hostshare /mnt/share` but it says `mount: /hostshare: Invalid fstype: Invalid argument`
21:14:26 <byakuren> i beleive you need: sysrc kld_list+=virtio_p9fs
21:15:04 <byakuren> then a quick change of: mount -t p9fs should do the trick c:
21:15:26 <byakuren> add virtio_p9fs_load="YES" to /boot/loader.conf if you need
21:35:31 <swee> what if virtio_9pfs.ko doesn't exist in /boot/kernel
21:44:45 <byakuren> try a kldload virtio_p9fs just as it is, as it should be there
21:45:02 <byakuren> note that it's _p9_fs not _9p_fs c:
21:46:15 <byakuren> if you still don't have it - then it's src is at /usr/src/sys/modules/virtio/p9fs - so you should be able to make; make install it
21:48:03 <swee> byakuren: 1. "kldload: can't load virtio_p9fs: No such file or directory" 2. /usr/src is empty
21:48:44 <byakuren> and you're 14.3 right? as per the previous message?
21:49:31 <swee> yeah
21:49:54 <byakuren> have you done a freebsd-update fetch; freebsd-update install recently? i only ask, as this should have been checked in since mid 2024: https://cgit.freebsd.org/src/commit/?id=e97ad33a89a78f55280b0485b3249ee9b907a718
21:50:28 <swee> i'll try that now
21:50:33 <byakuren> (2. /usr/src not existing - that's fine, you just don't have the freebsd src repo checked out is all, no biggie c:)
21:52:24 <swee> I don't think i selected the source tree when installing, is there a way to do so post-install?
21:52:55 <byakuren> yeah easily
21:53:54 <byakuren> the basic premise is just git cloning https://git.FreeBSD.org/src.git
21:53:59 <byakuren> into /usr/src
21:54:10 <byakuren> you prolly want to do that as a rood user, since it's system wide
21:54:57 <byakuren> there's 3 main freebsd repos, src, ports, and doc
21:55:18 <byakuren> so personally - i have them each in a zfs filesystem, mounted to /usr/(src;ports;doc)
21:56:00 <byakuren>  zfs list | grep usr/
21:56:02 <byakuren> zroot/usr/doc                                  522M   218G   522M  /usr/doc
21:56:04 <byakuren> zroot/usr/ports                               2.48G   218G  2.48G  /usr/ports
21:56:06 <byakuren> zroot/usr/src                                 2.76G   218G  2.76G  /usr/src
21:59:18 <byakuren> git clone -b releng/14.3 https://git.freebsd.org/src.git /usr/src
21:59:20 <byakuren> git clone https://git.freebsd.org/src.git /usr/src
21:59:39 <swee> I just used freebsd-update, virtio_p9fs.so still doesn't exist
21:59:45 <swee> ko*
22:00:06 <byakuren> have you rebooted since doing that?
22:00:25 <swee> will see what happens when i do so
22:00:31 <byakuren> c:
22:00:38 <byakuren> see ya in a sec then c:
22:01:18 <swee> nope, still doesn't exist
22:02:00 <byakuren> huh
22:02:22 <byakuren> gimme a sec to poke about
22:02:36 <swee> it's using 14.3-RELEASE-p2 now
22:03:33 <byakuren> nice - up to date c:
22:03:58 <swee> fyi I also installed the OS using FreeBSD-14.3-RELEASE-amd64-disc1.iso
22:06:53 <byakuren> so looks like, when i built it manually it installed it into /boot/modules - so sounds like a good way to go
22:06:56 <byakuren>  pwd
22:06:58 <byakuren> /boot/modules
22:07:00 <byakuren>  ls -l *p9*
22:07:02 <byakuren> -r--r--r--  1 root wheel 89560 Sep  6 22:42 p9fs.ko
22:07:04 <byakuren> -r--r--r--  1 root wheel 22424 Sep  6 22:42 virtio_p9fs.ko
22:07:36 <byakuren> so should be a case of, checking out src - heading to /usr/src/sys/modules/p9fs
22:07:42 <byakuren> and running make; make install
22:08:17 <swee> still cloning, cloning a 2GB repo o_O
22:09:08 <swee> compiled and installed, rebooting again
22:09:13 <byakuren> c:
22:09:30 <byakuren> another ideas as well (which is prolly gonna be just helpful) is installing the plan9port : pkg install plan9port
22:09:35 <byakuren> that gives you a bunch of plan9 related tools
22:09:53 <byakuren> and i THINK (just gonna check) there's stuff in there for mounting p9 file systems
22:10:32 <swee> KLD virtio_p9fs.ko: depends on kernel - not available or version mismatch
22:10:32 <swee> kldload: can't load virtio_p9fs: module already loaded or in kernel
22:10:53 <byakuren> !
22:11:30 <byakuren> so does the mounty-mount work now?
22:11:33 <swee> no
22:11:38 <byakuren> D:
22:12:01 <swee> I'll check plan9port as well
22:13:00 <byakuren> 9 mount tcp!server_ip!564 /mnt/plan9fs
22:13:17 <byakuren> once you've got plan9ports installed - this is the way to mount a 9pfs
22:13:26 <byakuren> (all plan9 commands, are prefixed with 9)
22:13:43 <swee> what about when its virtio
22:16:20 <byakuren> are you virtualising plan9 locally?
22:16:57 <swee> I'm not sure how libvirt or qemu does virtio plan9
22:17:08 <byakuren> ahhh
22:17:31 <byakuren> yes so from memory, qemu/kvm don't really do the virtio like that
22:17:37 <byakuren> it's more something supported in bhyve
22:17:43 <byakuren> but i don't wanna upend your whole setup or anything
22:18:28 <swee> the command i mentioned the first time worked fine in my other Alpine Linux guests but not on freebsd, hmmm
22:18:35 <swee> s/other //
22:22:27 <byakuren> hmm
22:22:36 <byakuren> you should have: 9 9pfuse
22:22:44 <byakuren> which will mount it as a fusefs
22:23:46 <byakuren> 9 9pfuse /hostshare /mnt/share
22:24:16 <swee> 9pfuse: dial /hostshare: unknown protocol family %d
22:27:39 <byakuren> how have you got hostshare setup?
22:28:21 <swee> https://lounge.swee.codes/uploads/cb17763654cbf7bb/image.png
22:29:06 <byakuren> ohh
22:29:32 <byakuren> right - so you're like, exporting the underlying cwfs or hjfs into /hostshare
22:30:19 <byakuren> 9 mount vm_host_address /mnt/plan9
22:30:21 <byakuren> try that
22:30:54 <byakuren> because plan9 should export the filesystem on the network, which is how it's meant to be accessed (port :564 should be automatically selected when you do this)
22:32:38 <swee> "don't know how to mount (no fuse)"
22:33:16 <byakuren> pkg install fusefs-libs3
22:33:18 <byakuren> kldload fuse
22:33:23 <byakuren> you need mr fuse
22:33:35 <swee> oh, i thought fuse was the right package, no wonder it tried to install gtk3 libraries when doing so
22:33:41 <byakuren> (user space filesystem driver)
22:33:46 <byakuren> ehehe
22:33:55 <byakuren> yeah - 'fuse' is a zx spectrum emulator
22:33:58 <byakuren> for some reason...
22:34:02 <byakuren> :p
22:34:35 <swee> 9pfuse: dail 192.168.122.187: Connection refused
22:34:54 <swee> and with 192.168.122.1 as well
22:35:17 <byakuren> ok so it has it's own ip address on the network
22:35:34 <byakuren> and that's a file server provinding instance of plan9
22:36:37 <byakuren> and the servers up and running, and you can connect to it with drawterm?
22:38:12 <swee> i'm not sure if qemu and virtio-p9 actually does listen on a tcp address, I'll probably see if sshfs to another (linux) vm might work
22:39:31 <swee> because all my vms in my libvirt setup use the 192.168.122.0 subnet that might be possible
22:40:22 <byakuren> oh...
22:40:26 <byakuren> that might o it
22:40:29 <byakuren> s/o/do
22:45:11 <swee> yep, it can ssh to other vms
22:48:11 <byakuren> huh
22:48:26 <ketas> swee came here too
22:48:38 <ketas> :)
22:50:09 <ketas> i currently try to adjust to pkgbase
22:50:26 <swee> yep, making an sshfs proxy with a small vm works great
22:50:33 <byakuren> ok - so done some research, and i was a bit wrong, sorry - that virtio-9p work (you found in src) - while it is present, it's slated for release only in freebsd 15 - so current, from a qemu host, you can't use virtio-9p it seems
22:51:18 <swee> alright, I'll keep watch when FreeBSD 15 becomes the latest production version
22:51:37 <byakuren> i do recall a script i setup in drawterm, that allowed me to access the plan9filesystem from my host once connected
22:51:41 <byakuren> let me see if i can find it
22:51:54 <byakuren> and that was a freebsd machine a few years ago, connecting to plan9 on metal
22:52:04 <byakuren> (was a great setup! used it at work for yearss)
22:53:43 <swee> I'm using a libvirt + qemu/kvm setup on my homeserver to separate services in vms, like a more advanced proxmox :3
22:54:12 <byakuren> https://pmikkelsen.com/plan9/mounting-9p-over-drawterm - mr pmikkelsen saves the day for me again
22:56:42 <byakuren> swee: ooh, that's a lovely setup - on my big server (out of action at the moment) i had a bunch of different jails setup for everything i needed
22:56:49 <byakuren> shame i can't really do the same on smol lappytop
22:57:24 * byakuren says while running znc and a bunch of other stuff locally... which must be great for the servers ;-;
23:00:02 <byakuren> ketas: how are you finding pkgbase? i'm.... aprehensive(?) for it when 15 comes out proper - but i think it's great
23:01:07 <ketas> APPREHENSIVE Definition & Meaning 1. : viewing the future with anxiety or alarm : feeling or showing fear or apprehension about the future.
23:01:11 <ketas> hmm
23:01:55 <ketas> i build 16-current nearly minimal package set in my 13.5
23:01:57 <ketas> :)
23:02:00 <ketas> built
23:02:37 <ketas> idea is good
23:03:04 <ketas> config files would be fun
23:03:17 <ketas> but config was even funnier before
23:03:29 <ketas> with etcupdate
23:03:45 <ketas> recall mergemaster?
23:03:56 <ek> ketas: Of course!
23:04:07 <ketas> i came from 4.6 after all
23:04:12 <ketas> :p
23:04:13 <byakuren> (apprehensive is sorta right, i know what it means... just not sure if its exactly the right word :p - but ty ^^)
23:04:33 <byakuren> omg mergemaster aha
23:05:10 <ketas> so with enough without_*'s i got cursed empty packages
23:05:34 <ketas> which install just a dir into /var/run maybe
23:05:44 <ketas> also it packaged up src too
23:05:51 <ketas> in zstd
23:06:12 <ketas> so it took 1h packaging and 45m building
23:06:28 <ketas> src, src-sys even
23:06:34 <byakuren> that's amazin
23:06:46 <ketas> funnily pkgbase was around before
23:07:02 <ketas> i mean tracking base is easier now
23:07:06 <ketas> at least
23:07:18 <ketas> no need for delete-old
23:07:30 <ketas> which hopefully gets everything
23:07:51 <ketas> or delete-old-libs which could make you cry
23:08:26 <byakuren> it did a few times...
23:09:41 <ketas> d
23:10:25 <ketas> damn src/src-sys got it slow here for sure
23:15:31 <ketas> also tmux fucking segfaultes again in command line
23:15:44 <ketas> wanted to saveb and then it went down
23:16:35 <ketas> i thought that bug was fixed already
23:17:32 <sig`> I've got a j5 Create Gigabit Ethernet USB 3.0 dongle but I am getting 100baseTX max... (ue0). it is using the: axge0 <ASIX Elec. Corp. AX88179> on usbus0 | ue0: <USB Ethernet> on axge0.
23:18:00 <sig`> but I can't get anything faster than 100. I tested it on the same cat6 cable on a linux box and i get full gigabit
23:18:54 <ketas> doesn't negotiate to 1g?
23:19:10 <sig`> even when I try: ifconfig ue0 media 1000baseT mediaopt ful-duplex the link drops and falls back to 100base
23:19:29 <ketas> any errors?
23:19:35 <ketas> in logs
23:19:51 <ketas> not that i know anything
23:19:54 <sig`> no, I'm wondering if it is the driver?
23:19:58 <ketas> i have rtl one here
23:20:10 <ketas> i only tested a little
23:20:50 <skered> sig`: From man axge   AX88178 the only 1Gb.
23:22:47 <sig`> skered: so my AX88179 doesn't do 1GB
23:22:49 <sig`> hmm
23:22:56 <ketas> no it's all 1g
23:23:39 <ketas> skered: where's the 100m?
23:23:50 <sig`> 1000baseT says only AX88178 but mine is AX88179
23:24:12 <ketas> also axe vs axge
23:25:54 <ketas> if it doesn't do 1g in fbsd, it's yet another bug...
23:26:06 <sig`> mine isn't the AX88178, its the ASIX AX88179 (j5create jue130). the man page note about 1000basteT AX88178 only looks outdated. This chipset does not support gigabit. but it comes up fine on linux. but under this freebsd machine with axge(4) it only ever negotiates to 100basetx
23:27:15 <ketas> also which version we read this man
23:27:27 <ketas> i'm reading at 13.5 now
23:27:39 <markmcb> just checking, it's not possible to install the 15.0 alpha version via freebsd-update, right?
23:28:23 <sig`> https://man.freebsd.org/cgi/man.cgi?query=axge&sektion=4&manpath=FreeBSD+14.3-RELEASE
23:29:00 <sig`> the 13.5 axge shows 1000baseT only for AX88178
23:29:06 <ketas> markmcb: iirc... no
23:29:14 <ketas> but hmm
23:29:16 <sig`> I'll just order a known working dongle
23:30:20 <markmcb> ketas, thanks. it's under /snapshots and not /releases on the download server, so that was my assumption ... i'll wait patiently for a beta :)
23:30:49 <ketas> it doesn't show anywhere that axge should not do 1g?
23:31:14 <ketas> markmcb: but wait
23:31:28 <ketas> how does one upgrade 14 then
23:31:44 <ketas> it must support freebsd-update
23:31:59 <ketas> unsure if *alpha* tho
23:32:30 <sig`> ketas: I agree it should negotiate 1Gb and it even explicitly supports mine
23:32:58 <ketas> so, loga?
23:33:02 <ketas> logs?
23:33:06 <sig`> it never shows 1000
23:33:19 <ketas> would be curious if it moans there
23:33:58 <sig`> it references 1000baseT Set 1000Mbps (Gigabit Ethernet) operation (Ax88178 only)
23:34:02 <ketas> can't be like, you tell it to go 1g and it just does 100m
23:34:27 <ketas> it might not tell any errors tho
23:35:18 <ketas> it would be extremely fun it that hw has some fancy issue
23:35:28 <skered> Appears to be long running issue with agex as well.  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225179
23:36:03 <sig`> That’s exactly what I saw on FreeBSD: when I ran ifconfig ue0 media 1000baseT mediaopt full-duplex the link went DOWN, and when I returned to autoselect it came back at 100baseTX. ifconfig never once showed 1000baseT on FreeBSD.
23:36:44 <ketas> did it report any errors?
23:36:51 <sig`> Same dongle/cable and usb 3.0 port on linux negotiated 500Mb/s immediately
23:37:00 <ketas> they sometimes do
23:37:23 <ketas> usb devices
23:37:40 <sig`> yeah, I'll just order a cheap one that is known to work with 1000
23:37:45 <markmcb> ketas, i think once it's at beta then you'll be able to "freebsd-update upgrade -r 15.0-BETA1"
23:37:50 <sig`> it gave no errors, went up and down with no issues
23:38:27 <ketas> log was empty?
23:38:40 <sig`> forcing ifconfig ue0 media 1000baseT mediaopt full-duplex dropps
23:38:52 <ketas> all.log, if you have it, or other logs, or dmesg
23:38:53 <sig`> but returning to autoselct comes back at 100base
23:39:01 <sig`> no errors messages printed
23:39:24 <ketas> hmm
23:39:29 <ketas> yeah no idea
23:39:57 <sig`> no worries, I can get a cheap one for like $20
23:40:13 <sig`> not worth pulling my hair out any more than what I have
23:40:15 <sig`> :)
23:40:24 <ketas> i got cheap rtl
23:40:36 <sig`> you mind telling me which one and model?
23:41:07 <ketas> 1g usb3 but i only have 2 ports and didn't wire it up on actual eth side
23:41:24 <ketas> RTL8153
23:41:38 <sig`> thanks
23:41:41 <ketas> it had no name :)
23:41:46 <ketas> so no idea
23:41:47 <sig`> I'll search for it
23:42:03 <ketas> i searched in ali and looked for rtls
23:42:11 <ketas> some do say chips
23:42:25 <ketas> one axe fails here
23:42:30 <ketas> supposed axe
23:42:47 <ketas> i think it needs usb modeswitch
23:43:16 <ketas> after a few seconds, device goes off and another one comes on
23:43:34 <ketas> i didn't know usb eth also does this
23:43:44 <ketas> :/
23:43:48 <sig`> heh
23:48:59 <ketas> i also have 3 usb bt's which doesn't work
23:49:15 <ketas> iirc someone had hack for *an* usb bt
23:49:30 <ketas> not for those iirc
23:49:58 <ketas> they come up as usb bt
23:50:21 <ketas> but either have wrong fw or mysteriously fail
23:50:49 <ketas> hack was to reinit it until it works or wait
23:51:04 <ketas> and usb wifi is complete shitshow :p
23:51:30 <ketas> world of hw sucks