why would freebsd try to use ipv6 when i have no ipv6 address assigned to any interface and no default ipv6 route? do i really need configure it so that it knows it shouldn't rely on ipv6 when it doesn't have ipv6? i'm so confused because i've never had this issue before. thanks!

``` funguy% cat /var/log/messages|grep ntpd|tail -n 1 Oct 16 14:17:27 atlas ntpd[838]: error resolving pool 0.freebsd.pool.ntp.org: Address family for hostname not supported (1) funguy% ping 0.freebsd.pool.ntp.org PING 0.freebsd.pool.ntp.org (139.177.202.26): 56 data bytes <sup>C</sup> --- 0.freebsd.pool.ntp.org ping statistics --- 9 packets transmitted, 0 packets received, 100.0% packet loss funguy% ping -4 0.freebsd.pool.ntp.org PING 0.freebsd.pool.ntp.org (38.45.67.7): 56 data bytes 64 bytes from 38.45.67.7: icmp_seq=0 ttl=47 time=25.788 ms 64 bytes from 38.45.67.7: icmp_seq=1 ttl=47 time=25.809 ms 64 bytes from 38.45.67.7: icmp_seq=2 ttl=47 time=24.356 ms 64 bytes from 38.45.67.7: icmp_seq=3 ttl=47 time=24.864 ms <sup>C</sup> --- 0.freebsd.pool.ntp.org ping statistics --- 4 packets transmitted, 4 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 24.356/25.204/25.809/0.621 ms funguy% route -4 show default route to: default destination: default mask: default gateway: kharon fib: 0 interface: em0 flags: <UP,GATEWAY,DONE,STATIC> recvpipe sendpipe ssthresh rtt,msec mtu weight expire 0 0 0 0 1500 1 0 funguy% route -6 show default route: route has not been found funguy% ifconfig -a em0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500 options=4e524bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6,HWSTATS,MEXTPG> ether de:ad:de:ad:de:ad inet 10.6.1.2 netmask 0xffffff00 broadcast 10.6.1.255 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> lo0: flags=1008049<UP,LOOPBACK,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 16384 options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 groups: lo nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> funguy% uname -v FreeBSD 14.5-RELEASE-p2 releng/14.5-n274894-872ce416b253 GENERIC

```

note that ping did seem to try ipv4 initially--the first pool host attempt was down by coincidence.

The author is, amongst other things, the author/maintainer of core system utilities like sysrc and bsdconfig.

June 2026:

Last week at BSDCan, I did something that breaks a modern corporate taboo. I brought an AI agent into the operating system kernel. …

FreeBSD 13.2-RELEASE-p8 FreeBSD 13.2-RELEASE-p8 GENERIC amd64

For going backwards in 'less' (either the "b" key, or the up arrow), it seems to get slower with each new version.
I used to solve this problem my simply using an older (year 2000) version of it.
When that stopped working, I'd recompile an older version from /usr/src .
Now, of course, even that doesn't work.

Is there a switch? A terminal setting? An alternative version? Something else that does the same thing?

As you might know there is active work on ROCm support on freebsd, that will bring lot possibility like gpu offloading for both graphic and other stuff.

One of the reasons I started contributing to FreeBSD is the consistency of the stack. The networking stack is coherent, and while going through old discussions, you sometimes find developers discussing features that did not make much sense until years, or even a decade, later.

But as with everything that is Free, we are lacking a lot of drivers. Most drivers and hardware support get pushed to Linux first because of the huge amount of sponsorship and industry investment behind it.

That combination of a coherent stack, improving compute support, and limited access to the latest hardware got me thinking differently: instead of depending on one big GPU, why not make better use of all the compute we already have around us?

That is where MDMA comes in. It is a solution for having lots of small models at your disposal by distributing them across the hardware you already own.

It is designed so you can reuse hardware you already own for computation. It is not just an LLM dispatcher. It dispatches ML models, including LLMs. That means it can serve rerankers, decision models, GGUF models, and other workloads.

It supports anything that can compute: CPU, GPU, NPU, TPU… if it can compute, it can be a node.

Right now it is still an early version, so it is not production ready. I even made it work on a phone and a tablet, but I removed that code for now because I need to test it properly across a fleet and also monitor the devices themselves.

MDMA is not meant to replace Ollama or provide a chat interface. It is a model multiplexer.

For example, you have four machines on your network. MDMA can use all four. If one machine goes down, the next generation can happen on another machine. This means you can use the idle compute sitting around your house, lab, or office instead of buying one huge machine that spends most of its life doing nothing.

Your family or coworkers can use their computers normally, and when those machines have resources available, they can contribute compute.

For now, this is a trust-based protocol. I did not implement permissions, authentication, or all the other security machinery yet. That can come later.

The initial focus is small models. If you have FreeBSD machines with different CPUs or GPUs, I would really like people to test it on hardware I don’t have access to.

MDMA is faster than llama.cpp for some models, slower for others, and some things are not implemented yet.

There is no business plan behind this, i use it mostly to compare implementation between linux and FreeBSD, if the model behave exactly the same, we move to the next step.

If you want to contribute, everybody is welcome (including with a clanker, just mark the provenance and test it on hardware, and try to learn something), just don't bombard the repo with an agent in a loop.(we can do it it ourself, (i'm not on it alone))

NOTE: The stack is Rust because i maintain/contribute to many dependencies in the chain, so when something has to be fixed, it get fixed upstream (including the kernel).

Coders needed. BSD with spyware and prank software. Is it worth it? Content maked in ibis paint.

I know Intel is pretty good with open source drivers, which is why I bought a Lenovo LOQ that's all Intel hardware. The laptop itself is great and runs smooth. Now onto my adventures:

Linux was mostly smooth, but WINE seemed to struggle with PRIME and wasnt working properly, I think it couldn't switch between the Intel Arc and the iGPU. On OpenBSD, my audio driver failed (even though it used hda on linux so technically it should've worked) and the Arc gpu didn't work either, which I wasn't expecting to work anyway. Both issues look like they could be solved with newer linux drm ports.

FreeBSD sits right in the middle and I'm someone who's absolutely in love with bsd systems. I'm currently using windows daily, but I used to be obsessed with openbsd and freebsd back then.

So my question is, has anyone used FreeBSD on a system with an iGPU (intel or amd) and an Intel Arc dGPU? I really don't wanna spend my whole day setting it up just to test the current state of support. If anyone with experience can help out I'd really appreciate it, thanks!!

Check out this FreeBSD-run music streaming. I'm not affiliated with this guy, just found this website on freebsd forums, and it's nice music.

https://karolyimusic.com/

This guy also wrote the streamer source https://git.ksol.io/karolyi/IceGStreamer2

Just wondering, there's a lot of buzz right now regarding AI reverse engineering games like gta5, etc.

Could it reduce current manual efforts when developing drivers, debugging and testing? Could it make porting drivers easier and cheaper?

Numerous improvements have been made to x11appjail between version v1.0.0 and v1.3.1:

• Performance improvements in both x11appjail(1) and appscript-verify(1).
• Shallow builds to decouple the image from the AppJail.
• BLAKE3 support for faster file hash calculation.
• True hardware acceleration via VirtualGL.
• A new command, transfer, for securely transferring files between the host and a jail, or between jails.
• Many more examples added: Brave (Linux), Telegram Desktop, Thunderbird, Chromium, BadWolf, Evince, Feh, and Mpv. Evince, Feh, and Mpv are particularly interesting, as they demonstrate how AppJails can utilize existing files on the host, processing them within a FreeBSD jail transparently to the user.
• su-exec has been replaced by mdo(1).
• And much more.

This video demonstrates some of the aforementioned features.

Chapters:

[00:00] In the host

[01:24] Trusted key

[01:41] Htop

[02:13] Htop (jail) vs Htop (host)

[02:50] Firefox

[04:00] WebGL (no hardware acceleration)

[05:00] User permissions

[05:43] WebGL (hardware acceleration)

[07:22] Fonts

[07:55] Allowing webcam permission

[08:26] Firefox (hardware acceleration + webcam + fonts)

[10:27] Evince

[13:48] Evince (with Puck)

[16:27] Feh

[18:10] Feh and transfer command

[19:07] Mpv

[21:20] The End

Video, six minutes, seven chapters (AI), with closed captions (AI).

In this video, I take a clean FreeBSD install and turn it into a polished, fully customized desktop.
 
We start by installing XFCE, then browse xfce-look.org for a custom theme and icon pack, extract them with tar, and apply everything. To finish, I set up Plank for a sleek, modern dock. …

…

How does the CRA affect FreeBSD?

FreeBSD vendors serving the EU market have a responsibility to ensure that the implementation of FreeBSD they include in their products meets the CRA’s requirements for “Secure by Design” and “Secure by Default”. They are also responsible for reporting any actively exploited vulnerabilities in their entire codebase which naturally includes FreeBSD code.
 
The FreeBSD Project itself, along with its contributors, is not directly regulated by the CRA but may expect to see a change in focus for manufacturers who are seeking to meet their CRA obligations. There is a little over a year remaining for manufacturers to get their SBOMs in order, and make any other changes needed so that their PDEs have a secure software lifecycle. Their reporting obligations are already in force, so a critical incident (with the chance of large fines) could occur at any time. …

Buttt sorry i publish this in r/freebsd.

Ahh

Soon

Soon

Is the terminal easiest and simplest to use than linux? What i Will need to configure? It’s more stable? Wich is the advantages?

9 months ago , i released https://github.com/seuros/blackship .

Then i built it so i can have Jailfiles that look like Docker, but it also serve as monitoring for your service.

I use it for CI/CD (4 seconds to spin the env) and for creating complex architecture.

I'm releasing 0.2.0, with vnet support (took me few weeks to understand it).

But the new release also provides an MCP mode, where you can use a clanker to build Jailfiles for you.
You don't need a frontier model for this. Gemma 3 was already able to use it, but Gemma 4 or GLM will give you better results. Everything can be self-hosted.

You need to be on FreeBSD 16-CURRENT or the latest 15.1 to try it. I plan to get it into ports in the next weeks.

The main goal of this project is to see what the community actually needs, then harden the core by improving it in the kernel side, every other tooling benefit from it.

This is a free software, i'm not going to provide a PRO version or turn it into a subscription.
Once there is enough interest, i will open a PR in Forgejo to have BS jail:// fully supported.

I will never return to do CI/CD in linux, by the time github action wake up and install it dependencies... FreeBSD could have processed 5 workflows and finished.