This is good news; FreeBSD's wifi/bluetooth stack definitely more love and a bit of polishing. The last time I tried using Intel wifi on FreeBSD the driver kept trying to use wrong tx settings without allowing me to change them, leading to slow performance and poor signal (the same card under Linux/Windows had excellent signal from the same AP).
Yup, there are a ton of people, myself included, who would love to be able to build an all-in-one router/firewall/WAP box for a small environment where such a thing makes sense, but we like pfSense for the router/firewall part. FreeBSD's wireless support has been horrible every time I've tried it compared to the same hardware running a Linux-based platform.
I don't mind using (and in fact generally prefer) separate WAPs in cases where I expect to want to expand (most businesses and larger homes) but there are occasionally cases where an all-in-one device does actually make sense. Mostly small mall businesses where you have a coverage area of ~150 square feet and need to cram all the equipment under the front counter.
> but we like pfSense for the router/firewall part.
Thank you very much!
> FreeBSD's wireless support has been horrible every time I've tried it compared to the same hardware running a Linux-based platform.
That’s why Netgate and the FreeBSD foundation are employing bz@ full-time to work on the 802.11 stack. FF for mostly intel client 802.11ac support, Netgate for the AP side, starting with Atheros, because Intel 802.11 parts are somewhat crippled here prior to 802.11ax.
I know Adrian, and I like Adrian, but his mention of bz@‘s efforts seems dismissive to me.
I once considered getting into the 802.11 stack for a couple of BSDs after experiencing several issues with my cards. Some were minor and I was able to fix (driver wouldn't attach because it was missing a PCIe device ID) and other weren't.
I couldn't find much good material on it though. A popular FreeBSD driver book noted that 802.11 driver development was too complicated to be in scope of the book, and that to even start, you should you have a solid understanding of 802.11.
I figured the specs might be a good place to start, but noped out as soon as I saw how much IEEE charges for the individual 802.11 specs. Some resources, including the site for the Linux kernel's wireless stack note that IEEE at one point would make the specs available for free once they reached a certain age, but that doesn't seem to be the case anymore. The closest thing I could find was a copy of the 802.11b spec, which isnt very helpful.
Yep I can confirm intel cards are still an issue. I installed FreeBSD a week ago and gave up trying to enable Wi-Fi after an hour of struggle on a Thinkpad T490, didn't even get to the point of having the interface show up in ifconfig. Ended up using my phone in USB tethering mode instead.
What is the cause of this situation? Is it simply that commercial entities using FreeBSD does not have wifi as a requirement? (E.g. companies using FreeBSD in server environments.)
In many cases, like say the intel WiFi drivers on Linux, the driver is written by Intel employees.
The BSDs don’t have the critical mass to get this vendor support. For example, much of the intel WiFi work on OpenBSD is done by one person, Stephan Sperling, on a volunteer basis.
I only mention intel in the above examples because that’s what’s in the Thinkpad I had that didn’t have support yet. So I looked into the driver situation on Linux, FreeBSD and OpenBSD.
> What is the cause of this situation? Is it simply that commercial entities using FreeBSD does not have wifi as a requirement?
I don't have any numbers to back it up and I'm not sure if anyone even could know (does FreeBSD have any kind of hardware statistics program?) but I have a strong suspicion that the proportion of laptop users running anything even related to BSD other than Mac OS is fairly tiny. Beyond that, I suspect that many of those that do are using one of the same bunch of older Thinkpads that are popular with the kinds of people who work on operating systems. Devices that aren't used with those laptops probably don't get much attention.
Also 802.11ac in particular seems to mostly require firmware blobs, which are kryptonite to a lot of the kinds of people who would have to be developing these drivers. That's why you might have noticed that devices like the Librem 5 and PinePhone only have 802.11n.
