PÁLI Gábor János

Hi @felicia-wen: Could you please help me to see how is this report related to #11? The cited issue talks about 14.0-CURRENT and the use of `bhyve+`. Are you using...

The contents of `wifibox.log` seems to be scrambled: the timestamps are not linear and there are missing sections.

> I just upgraded the system to 14.0-CURRENT without bhyve+ installed, according to #11 I do not think that #11 is relevant in this case. As you can see in...

Nice work @MegaManSec, thank you for tracking down this issue! Since we can control all the packages for Wifibox/Alpine, the guest image that is shipped for Wifibox by default, I...

Version `20240823` of `net/wifibox-alpine` contains both fixes for the problem: Joshua's kernel patch and a `remove-wireless` OpenRC script that is run on shutdown and it implements the logic described above....

Yes, that is an acknowledged risk.

Thanks for the report! Apparently the logs are from the `20230326` version of `wifibox-alpine`. [Broadcom cards are not yet properly supported in that version](https://github.com/pgj/freebsd-wifibox/discussions/58), please try a development branch on...

Wow, I have not seen such messages before... You will have modify the `Makefile` for the `net/wifibox-alpine` port to download the requires files (as distfiles) and copy them to the...

For what it is worth, the firmware files are part of the standard `linux-firmware` distribution. If you choose the `FW_BRCM` option, they should be added to the image. Though it...

Based on the log messages, it is `brcm/brcmfmac43602-pcie.FreeBSD-BHYVE.bin` what the driver is looking for, while the `linux-firmware` package contains only `brcm/brcmfmac43602-pcie.ap.bin` and `brcm/brcmfmac43602-pcie.bin`. Hence a symbolic link with the name...