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? opnsense/core #6247

bug report title at OPNsense: "IPv6 MLD listener report going to wrong interface #6247"

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

if i'm just using ethernet ports for failover it doesn't matter if their speeds are different does it?

i wanted to use the 2 1gbit onboard ethernet ports as the failovers and the 10gb one as the master port

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.

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.

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 ports.freebsd.org/cgi/ports.cgi?query=puppet8&stype=all&sektion=all

why would this packasge no show up in a search, I'm using a public mirror which looks like it hosts the package

I do see a sysutils/puppet7 being returned, is there some sort of catagory masking it ?

zi: thanks for the suggestion! I tried reproducing it with FreeBSD 14.2 in a VM but so far wasn't successful.

does anyone have an idea what mechanism might lead to MLD reports coming out of the wrong interface on a FreeBSD?

hello \(^⁠_⁠^)

O HAI

how can I enable and print these CTR3(KTR_MLD, ...) debug lines in the kernel?

\o/

Am I correct that bhyve cannot run Linux VMs with Wayland without having an additional GPU to pass through to the bhyve VM?

so i finally go everything in and running

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

and IPMIView won't even work with it

can I somehow check from userspace if V_ip6_mrouter is enabled?

T_X: opensense 25.1+ is based on freebsd 14.2. so if you arent on that release, id upgrade

zi: both my FreeBSD testing VM and the OPNsense in production are running FreeBSD 14.2 according to "uname -a"

and only opnsense is broken?

so far, yes.

compare sysctls?

so what is en vogue for managing jails nowadays? is it iocage?

i'd like to start setting jails up

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 ?

and according to cgit.freebsd.org cgit.freebsd.org/ports/tree/sysutils/puppet8 this package should exist in that repo

am I correct on those things ?

yes, you are about right ikonia

thanks, very rust on this

unrust it please

trying, bit of a slog

it nobody acts old cruft will get removed

there are port gravediggers who do this from time to time

can you explain that a bit more please

ikonia: docs-archive.freebsd.org/doc/6.4-RE…rters-handbook/dads-deprecated.html

that's very old source, but it's more or less valid

reading that doc, it doesn't look like that should impact the puppet8 package I'm looking for

what would cause pkg search puppet or specfically pkg search sysutils/puppet8 to either display

puppet7-7.34.0 Configuration management framework written in Ruby

or no result

it's fine, but if you can upated it, it will be even better

sorry what do you mean

I may have missunderstood

Puppet Core 7.35 is the latest

ahhhhh

then why is puppet8 listed as a package

eg: cgit.freebsd.org/ports/tree/sysutils/puppet8

perhaps it's the upcoming version

no, it's another branch

ahhhhhhhhh

am I looking at a wrong branch

again, sorry, it's been a long time

how do I see this then as that looks to me like the 'stable' or 'main' branch that I should be using

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

my file is pretty sparce though

I'm so sorry, I've messed this up, it's a port not a package

that doesn't mean there is a package for it

I still think there is one....but I'm not sure,

ikonia: people who beging using FreeBSD usually deploy RELEASE, not STABLE or CURRENT

My /etc/os-release says VERSION="13.5-RELEASE-p1" but uname -r says 14.2-RELEASE-p1 did I forget a step?

what does uname -KU say ?

1402000 1402000

neat

Looks like when I did the last update I forgot to run pkg upgrade too... Let me remedy that

perhaps you missed etcupdate(8), but it's automatised, so maybe not

pkg has not much to do with /etc/os-release

yeah I didn't think it did

ah - I had never ebooted

probably not the best idea

but it has fixed itself now after a reboot

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

i'm getting some weird result with sshfs

i think i managed to move rename the same file twice

I just uninstalled gcc12

s/move //

i renamed it twice at nearly the same time from

i renamed it twice at nearly the same time from 2 different threads and both succeeded

this was done via std::filesystem::rename and both returned without throwing

this happens both with and without -o cache=no

happens fairly reliably too

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

this doesn't happen on linux

for context: when both renames succeeded, they were both renaming from a fixed filename to a different fixed filename

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

ikonia_: build errors are the only thing that could block it. It may take many days from commit -> package.

I mean "only" isn't accurate but most of the time it would be a build error. Infrastructure issues could cause problems too

bdrewery: interesting it looks like that ports been around a while, I'll do a local build see what it looks like

sorry and license restrictions could block it

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

which port is it?

puppet8

I'll take a proper look now, I was just box ticking the low hanging fruit before investing my time

puppet8 is a package

just tried to install it on a 14.2-R box using official FreeBSD pkg repos

are you running on an unsupported release by any chance?

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

sudo pkg install puppet8

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

the puppet8 port was initially created in april of 2023, so it has been around for years

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

in /etc/pkg sorry

looks like I've wasted your time, sorry

no worries ikonia, feel free to fully switch to FreeBSD

 

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,

it's why I've had to pickup BSD again after a good period away

opnsense is already built on freebsd

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

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

mzar: all good appreciate the help you've given, I'll pickup pace as I get back into the flow

/win 1

oops

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

ipfw ended up being sufficient for my needs at the time

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

ipfw didn't have the sexy opnsense interface to pf however

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)

deimosBSD: interface is good for day to day use

with opnsense, it depends if you run the business or community version

deimosBSD: running netfilter with iptables was all commandline and flat file based, but that's because I knew it really well

moving to nftables to the same level of confidence will take a long time, opensense allows me to cheat

community version here

for the record, i like ipfw and pf far more than iptables/nfttables

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

nft reset that experience and confidence

indeed

welcome to BSD ;)

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

cool

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

lattera: ^5

zeus