Created attachment 249378 [details] /var/log/messages output (includes kernel msgs) Hardware: Framework 13". At varying intervals, but quite frequent, I get disconnected from wifi and need to issue an `ifconfig wlan0 scan` or a `service netif restart wlan0` to reconnect. `/var/log/messages` output attached, as is pciconf -lv and dmesg.boot. Not sure what I can do to help with this?
Created attachment 249379 [details] pciconf -lv
Created attachment 249380 [details] dmesg.boot
For reference - dmesg indicates `FreeBSD 15.0-CURRENT #1 main-d0bf8b5aac: Mon Feb 19 00:43:40 CET 2024`
(In reply to Eirik Oeverby from comment #0) From the `/var/log/messages` output, looks the firmware keeps having microcode errors "WRT: Invalid buffer destination", etc.
(In reply to Cheng Cui from comment #4) The "WRT: Invalid buffer destination" are because for (unknown) reasons the firmware disabled various debug buffers. We've had this while discussing the HT fw assertions in February. It's so much in the log because he issues a service netif restart and the VAP (wlan interface) gets destroyed and re-created. Eirik, it's really hard to debug it like this. Not sure if we tried in the past or with someone else given this is a Ubiquity again? If ifconfig wlan0 scan as su does not help (wpa_cli scan), it would be interesting to know if ifconfig wlan0 down && sleep 1 && ifconfig wlan0 up helps (instead of serivce restart). it would be helpful if could add at least one -d to the wpa_supplicant flags in rc.conf to get a bit more logging. Of course it would be interesting to see if the AP has logs of these events too. can you ssh into the AP and check?
(In reply to Bjoern A. Zeeb from comment #5) I have two -d's in rc.conf right now, you want more than that? Also there are no debug logs of any kind available on the Amplifi HD :( Now that you mention it, I don't think I've seen this happening in the office, where we have more "pro-grade" wifi APs (Ubiquiti, so same maker, but quite different class). It's also worth mentioning I have two APs in the house, one on each floor, and they're linked by gbit ethernet. So no fancy matrix stuff, just "ethernet backbone", in Amplify-speak. In my usual position in the house, the secondary AP is also visible in a scan, I don't know if this is relevant? In light of the above, documentation states I have the following "advanced" options available to me: *A-MSDU for wireless clients Improves wireless clients throughput 802.11r - Fast BSS Transition Faster authentication when roaming *802.11k - Neighbor Report Improves AP scan speed *802.11v - BSS Transition Management Directs stations to better AP * = currently enabled. Fun fact: STP is an optional feature, and disabled by default. Go figure. /Eirik