02:05:45 hi, I'm not that familiar with FreeBSD, but does anyone have any thoughts on whether this is a general FreeBSD bug and should be forwarded to some FreeBSD bug tracker? https://github.com/opnsense/core/issues/6247 02:06:08 bug report title at OPNsense: "IPv6 MLD listener report going to wrong interface #6247" 02:12:34 T_X: guess id say if you can repro it on freebsd 14.2, then id open a pr with the freebsd project for it 04:05:19 if i'm just using ethernet ports for failover it doesn't matter if their speeds are different does it? 04:05:42 i wanted to use the 2 1gbit onboard ethernet ports as the failovers and the 10gb one as the master port 05:31:46 managed to get fbsd on it and i guess maybe usb drive cache flush was taking forever at the end where it had to halt. 05:32:19 it took like 5-10 minutes to shutdown ... and when i was installing before i thought it froze and didn't matter so i guess something didn't get written to it. 09:34:15 in pkg search on a freebsd 14 machine (an OPNSense build) I'm doing 'pkg search sysutils/puppet8' and getting no results, yet I can see the package should be available detailed here https://ports.freebsd.org/cgi/ports.cgi?query=puppet8&stype=all&sektion=all 09:34:34 why would this packasge no show up in a search, I'm using a public mirror which looks like it hosts the package 09:36:19 I do see a sysutils/puppet7 being returned, is there some sort of catagory masking it ? 10:24:29 zi: thanks for the suggestion! I tried reproducing it with FreeBSD 14.2 in a VM but so far wasn't successful. 10:25:31 does anyone have an idea what mechanism might lead to MLD reports coming out of the wrong interface on a FreeBSD? 12:12:54 hello \(^⁠_⁠^) 12:13:23 O HAI 12:14:15 how can I enable and print these CTR3(KTR_MLD, ...) debug lines in the kernel? 12:44:45 \o/ 13:20:17 Am I correct that bhyve cannot run Linux VMs with Wayland without having an additional GPU to pass through to the bhyve VM? 13:32:24 so i finally go everything in and running 13:33:02 i wish the isilon had an ipmi i could remote to :/ that's the only caveat. it's so old that it's running some ancient java and ancient ssl that nothing wants to allow me to use 13:33:12 and IPMIView won't even work with it 13:38:21 can I somehow check from userspace if V_ip6_mrouter is enabled? 13:38:43 T_X: opensense 25.1+ is based on freebsd 14.2. so if you arent on that release, id upgrade 13:40:00 zi: both my FreeBSD testing VM and the OPNsense in production are running FreeBSD 14.2 according to "uname -a" 13:40:31 and only opnsense is broken? 13:41:11 so far, yes. 13:41:33 compare sysctls? 14:09:05 so what is en vogue for managing jails nowadays? is it iocage? 14:09:18 i'd like to start setting jails up 15:05:17 my FreeBSD is very rusty, I live in Linux, I've got this line in my FreeBSD.conf in /etc/pkg url: "pkg+https://pkg.FreeBSD.org/${ABI}/quarterly", that should be the FreeBSD 14 repo (with ABI linking to the version of FreeBSD right ? 15:06:01 and according to cgit.freebsd.org https://cgit.freebsd.org/ports/tree/sysutils/puppet8 this package should exist in that repo 15:06:05 am I correct on those things ? 15:15:55 yes, you are about right ikonia 15:16:06 thanks, very rust on this 15:16:16 unrust it please 15:16:29 trying, bit of a slog 15:16:33 it nobody acts old cruft will get removed 15:17:27 there are port gravediggers who do this from time to time 15:17:41 can you explain that a bit more please 15:18:32 ikonia: https://docs-archive.freebsd.org/doc/6.4-RELEASE/usr/share/doc/en/books/porters-handbook/dads-deprecated.html 15:19:03 that's very old source, but it's more or less valid 15:19:55 reading that doc, it doesn't look like that should impact the puppet8 package I'm looking for 15:21:37 what would cause pkg search puppet or specfically pkg search sysutils/puppet8 to either display 15:21:40 puppet7-7.34.0 Configuration management framework written in Ruby 15:21:43 or no result 15:22:24 it's fine, but if you can upated it, it will be even better 15:22:45 sorry what do you mean 15:23:07 I may have missunderstood 15:23:32 Puppet Core 7.35 is the latest 15:23:39 ahhhhh 15:23:53 then why is puppet8 listed as a package 15:24:25 eg: https://cgit.freebsd.org/ports/tree/sysutils/puppet8 15:25:29 perhaps it's the upcoming version 15:26:45 no, it's another branch 15:26:52 ahhhhhhhhh 15:26:57 am I looking at a wrong branch 15:27:09 again, sorry, it's been a long time 15:29:51 how do I see this then as that looks to me like the 'stable' or 'main' branch that I should be using 15:38:08 looking at my FreeBSD.conf file I don't see anything that identifies the branch it's working off or defaults to if nothing is set 15:39:01 my file is pretty sparce though 15:51:10 I'm so sorry, I've messed this up, it's a port not a package 15:51:52 that doesn't mean there is a package for it 15:52:09 I still think there is one....but I'm not sure, 16:13:36 ikonia: people who beging using FreeBSD usually deploy RELEASE, not STABLE or CURRENT 16:17:18 My /etc/os-release says VERSION="13.5-RELEASE-p1" but uname -r says 14.2-RELEASE-p1 did I forget a step? 16:19:40 what does uname -KU say ? 16:20:11 1402000 1402000 16:20:28 neat 16:20:47 Looks like when I did the last update I forgot to run pkg upgrade too... Let me remedy that 16:21:13 perhaps you missed etcupdate(8), but it's automatised, so maybe not 16:21:26 pkg has not much to do with /etc/os-release 16:21:41 yeah I didn't think it did 16:27:25 ah - I had never ebooted 16:27:39 probably not the best idea 16:27:47 but it has fixed itself now after a reboot 16:32:07 oh, and another thing. I am using gcc 13 to compile some C++23 program and ldd on the resulting binary is trying to libstdcxx from GCC12 16:36:16 i'm getting some weird result with sshfs 16:36:44 i think i managed to move rename the same file twice 16:36:49 I just uninstalled gcc12 16:36:50 s/move // 16:37:10 i renamed it twice at nearly the same time from 16:37:20 i renamed it twice at nearly the same time from 2 different threads and both succeeded 16:37:48 this was done via std::filesystem::rename and both returned without throwing 16:40:12 this happens both with and without -o cache=no 16:40:23 happens fairly reliably too 16:43:27 exceptions are enabled, they're just not thrown in that case. after a while both my threads try to rename the file from the new name to some other name, and one of them is slightly delayed so an exception is thrown and not caught and my program crashes 16:44:04 this doesn't happen on linux 16:47:22 for context: when both renames succeeded, they were both renaming from a fixed filename to a different fixed filename 17:41:54 what are the requiremements that trigger a port becoming a package, in my example what's stopping the puppet8 port being a package in the repo ? are their dependencies not met around people/process/technology 17:44:26 ikonia_: build errors are the only thing that could block it. It may take many days from commit -> package. 17:44:46 I mean "only" isn't accurate but most of the time it would be a build error. Infrastructure issues could cause problems too 17:45:37 bdrewery: interesting it looks like that ports been around a while, I'll do a local build see what it looks like 17:45:57 sorry and license restrictions could block it 17:46:04 just looking for pointers really so I don't waste my time on something that is (for example) just a process hole rather than a actual problem 17:46:22 which port is it? 17:47:41 puppet8 17:48:07 I'll take a proper look now, I was just box ticking the low hanging fruit before investing my time 17:48:25 puppet8 is a package 17:48:38 just tried to install it on a 14.2-R box using official FreeBSD pkg repos 17:48:50 are you running on an unsupported release by any chance? 17:49:28 I'm missing something then, pkg search puppet only shows the puppet 7 package, it's on an opnsense box but it's configured to use the freebsd 14 repos so that package should exist 17:49:40 sudo pkg install puppet8 17:49:47 I couldn't see any reason it wouldn't exist so working backward I came to the conclusion it was only a port not package 17:50:14 the puppet8 port was initially created in april of 2023, so it has been around for years 17:50:55 ahhh look at that, my FreeBSD.conf in /etc/package shows it's using the offocial repos, yet pkg install is pointing at opnsense repos (whcih I will check) doesn't have it in it 17:51:06 in /etc/pkg sorry 17:51:25 looks like I've wasted your time, sorry 17:54:19 no worries ikonia, feel free to fully switch to FreeBSD 17:54:23 17:57:52 mzar: it's one of the things I'm looking at the moment, overlaying OPNSense ontop of BSD rather than the bundled product, I've got some puppet and ansible that will do it and I need to test it, 17:58:23 it's why I've had to pickup BSD again after a good period away 18:00:44 opnsense is already built on freebsd 18:02:41 ikonia: I have never transitioned from running OPNSense to vanilla FreeBSD on the host, nor have I used OPNSense more than for evaluation, so I can't help 18:04:37 deimosBSD: it is, but it's mirroring the apple eco system of closed package control rather than upstream package control (I understand why) I need to change firewall tech, so I'm looking at OPNSense and OPNSense on top of BSD upstream to be a bit more unlocked by default 18:04:54 mzar: all good appreciate the help you've given, I'll pickup pace as I get back into the flow 18:08:06 /win 1 18:08:08 oops 18:08:12 ikonia: best of luck. I tried years ago and got to the point where if I wanted native pf, not ported pf, i just had to run openbsd 18:09:37 ipfw ended up being sufficient for my needs at the time 18:09:52 deimosBSD: interestingly I'm running native netfilter on Linux, but the move to nftables is a big move so I thought I'd look at other options, I used to use pfsense, but fell out of love due to the community/netgate approach, OPNSense seems a happy middle ground, so I'm just playing around about how tuned to how I like to work I can be safely 18:10:37 ipfw didn't have the sexy opnsense interface to pf however 18:10:40 honestly, I'll probably end up just running OPNSense and enabling the core repo and installing the few packages I want outside of OPNSenses packages (which are old) 18:10:50 deimosBSD: interface is good for day to day use 18:11:09 with opnsense, it depends if you run the business or community version 18:11:11 deimosBSD: running netfilter with iptables was all commandline and flat file based, but that's because I knew it really well 18:11:29 moving to nftables to the same level of confidence will take a long time, opensense allows me to cheat 18:11:38 community version here 18:11:55 for the record, i like ipfw and pf far more than iptables/nfttables 18:12:28 deimosBSD: I agree it's actually more powerful, but I stuck with what I was hugely more confidence and experencd in as a trade off 18:12:37 nft reset that experience and confidence 18:13:15 indeed 18:13:19 welcome to BSD ;) 18:14:03 deimosBSD: check PF in 15-CURRENT, it has many enhancements like af-to translation support (NAT64), they are cooking it all for upcoming FreeBSD 15.0-RELEASE which will be out before Christmas 18:26:50 cool 18:29:49 I'm going to do a little test and mirror the puppet8 package I want to a local repo (maybe) how does BSD packages manaage dependencies between packages 19:53:29 https://hardenedbsd.org/article/shawn-webb/2025-05-20/optional-rust-freebsd-support-may-2025-status-report 20:13:41 lattera: ^5 22:00:38 zeus