BSD-NL Conference Early 2026 - Florian Obser - Let's find out how to get predictable IPv6 addresses assigned to VMs...

BSD-NL Conference Early 2026 - Florian Obser - Let's find out how to get predictable IPv6 addresses assigned to VMs...

Today is the BSD-NL Conference - Early 2026 🐡😈⛳
In between all the hacking and slacking there will be talks!
You can catch the stream on: https://exquisite.tube/c/bsdnlconference/videos
🌐 https://events.bsdnl.nl/early2026/talk/W9P9RT/
🎤 Let's find out how to get predictable IPv6 addresses assigned to OpenBSD VMs
by Florian Obser
🌐 https://events.bsdnl.nl/early2026/talk/BGGPZQ/
🎤 On DOS, floppies, NetBSD and nostalgia
by Eirik Øverby
The full schedule 📅 https://events.bsdnl.nl/early2026/schedule/
📆 2026-05-09 / May 9th 2026
🕐 10:00-23:00 CET
📍 Brouwerij Maximus (Utrecht)
🌐 https://bsdnl.nl
#BSDNL #RUNBSD #BSD #OpenBSD #FreeBSD #NetBSD #HardenedBSD #SecBSD #DragonflyBSD
Sadly, the non-systemd distros are getting fewer and fiddlier.
The no-ai operating systems are incredibly few. The only one I know of off the top of my head is #NetBSD.
All of the other ones are slop-friendly or slop-neutral.
It's sad that #Fedora doesn't seem to have the will or perhaps even understanding to take a principled stance on this. I can't say I expected a lot better of them, but one can freaking hope.
#NetBSD has a no-slop policy
Various #FOSS OS communities' reactions to joining them:
#Linux: "Hey, welcome to the fam! Here's a stack of CDs I burned, see which one boots for you."
#FreeBSD: "Hey, we're glad you're here! Here's an amazing handbook to get you started, holler if you need a hand!"
#NetBSD: "Of course it runs NetBSD! Welcome! :D"
#OpenBSD: "Don't expect a lot of hand-holding, but we're all having fun with it, and hopefully you will enjoy the process, too."
#9front: "Are... you... sure you want to do this?"
😆
(For the record, I love them all. I only regret I haven't had much of a chance to play with #Haiku, or interact with that community, yet!)
ifconfig: exec_matches: No such file or directory
I recently installed NetBSD/amd64 10.1 on my ThinkPad T400, but I am having issues with WiFi.
My WiFi card is supported by the iwn(4) driver, and it worked just fine in the installer; but when when booting, I get this error in my dmesg:
[ 170.004879] iwn0: autoconfiguration error: could not get firmware handle iwlwifi-5000-2.ucode
[ 170.004879] iwn0: autoconfiguration error: could not read firmware
[ 762.464956] iwn0: autoconfiguration error: could not get firmware handle iwlwifi-5000-2.ucode
[ 762.464956] iwn0: autoconfiguration error: could not read firmware
When I try to start networking manually, I get this:
amethyst# sh /etc/rc.d/network start
Starting network.
Hostname: amethyst.fritz.box
IPv6 mode: host
Configuring network interfaces: iwn0ifconfig: exec_matches: No such file or directory
.
Adding interface aliases:.
Waiting for duplicate address detection to finish...
And I can confirm that the file does exist in the correct location:
amethyst# file /libdata/firmware/if_iwn/iwlwifi-5000-2.ucode
lhs/off overflow 4270589976 0
/libdata/firmware/if_iwn/iwlwifi-5000-2.ucode: data
Does anyone have any idea how to fix this?
ifconfig: exec_matches: No such file or directory
I recently installed NetBSD/amd64 10.1 on my ThinkPad T400, but I am having issues with WiFi.
My WiFi card is supported by the iwn(4) driver, and it worked just fine in the installer; but when when booting, I get this error in my dmesg:
[ 170.004879] iwn0: autoconfiguration error: could not get firmware handle iwlwifi-5000-2.ucode
[ 170.004879] iwn0: autoconfiguration error: could not read firmware
[ 762.464956] iwn0: autoconfiguration error: could not get firmware handle iwlwifi-5000-2.ucode
[ 762.464956] iwn0: autoconfiguration error: could not read firmware
When I try to start networking manually, I get this:
amethyst# sh /etc/rc.d/network start
Starting network.
Hostname: amethyst.fritz.box
IPv6 mode: host
Configuring network interfaces: iwn0ifconfig: exec_matches: No such file or directory
.
Adding interface aliases:.
Waiting for duplicate address detection to finish...
And I can confirm that the file does exist in the correct location:
amethyst# file /libdata/firmware/if_iwn/iwlwifi-5000-2.ucode
lhs/off overflow 4270589976 0
/libdata/firmware/if_iwn/iwlwifi-5000-2.ucode: data
Does anyone have any idea how to fix this?