PÁLI Gábor János

Thanks for the feedback! A couple of comments: - I was talking about the `dmesg` of the FreeBSD host. When a program crashes (which is the Linux-native `apk` in our...

Personally, I do not have any problems with Nose2. But if the integration tests were migrated to Elixir, there is no need for it any more. On its web site,...

I am not sure if I got you right @big-r81. Elixir has already been used in CouchDB and there are a lot of integration tests written in that language. And,...

Thanks for the report! Looks like that is happening because the `wlan0` interface is disabled for some reason. Could you please tell me what does the following command, on the...

The `status` results that you added to the description is with the `wlan0` device? What does the following command say on the _host_: ```console wpa_cli -i wlan0 status ```

I can of course recommend to do restart WPA Supplicant on the `wifibox console`: ```console service wpa_supplicant restart ``` Does it help?

You could also stop `wpa_supplicant` on `wifibox console` and start the service in the foreground to learn more about the potential causes: ```console service wpa_supplicant stop wpa_supplicant -i wlan0 -c...

It might be worth to see if this is kernel-specific. You can try to build the `net/wifibox-alpine` port using the `KERN_EDGE` configuration option to use Linux 6.8 instead.

These commands should be executed on the _guest_. Use the `wifibox console` to log in there.

I think I have found a possible cause for this issue. Could you please try the `20240414` version of the `net/wifibox-alpine` that I published here: https://github.com/pgj/freebsd-wifibox-port/tree/chore/net/wifibox-alpine/update-20240414 There the port is...