sudo iwconfig wlan0mon You should see in the output.
PHY Interface Driver Chipset phy0 wlan0 ath9k Qualcomm Atheros (mac80211 monitor mode vif enabled for [phy0]wlan0 on [phy0]wlan0mon) (mac80211 station mode vif disabled for [phy0]wlan0) Your new interface will be named something like wlan0mon or mon0 . Check the new interface:
Also test packet capture (optional but satisfying):
Install Airmon-ng ((better)) | UHD |
sudo iwconfig wlan0mon You should see in the output.
PHY Interface Driver Chipset phy0 wlan0 ath9k Qualcomm Atheros (mac80211 monitor mode vif enabled for [phy0]wlan0 on [phy0]wlan0mon) (mac80211 station mode vif disabled for [phy0]wlan0) Your new interface will be named something like wlan0mon or mon0 . Check the new interface: install airmon-ng
Also test packet capture (optional but satisfying): sudo iwconfig wlan0mon You should see in the output
This could have to do with the pathing policy as well. The default SATP rule is likely going to be using MRU (most recently used) pathing policy for new devices, which only uses one of the available paths. Ideally they would be using Round Robin, which has an IOPs limit setting. That setting is 1000 by default I believe (would need to double check that), meaning that it sends 1000 IOPs down path 1, then 1000 IOPs down path 2, etc. That’s why the pathing policy could be at play.
To your question, having one path down is causing this logging to occur. Yes, it’s total possible if that path that went down is using MRU or RR with an IOPs limit of 1000, that when it goes down you’ll hit that 16 second HB timeout before nmp switches over to the next path.