You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to propose renaming "wireless_ap" to "wireless_bssid" to align with the naming convention of network objects.
I would also like to porpose adding a "time" metric to the wireless object. Tracking the amount of time the client (laptop, typically) is associated with that specific BSSID is necessary to identify network issues when network devices roam across multiple APs , and may be re-associating either with another BSSID , or re-associating with the same BSSID. Either way, this disconnect/reconnect is difficult to track with the basic tools. I am hoping to have this time metric show via conky to expose the issue to the user.
In doing a it of searching the concept of "time elapsed since this client has been associated to this BSSID" does not appear readily available.
Is this available at the system level ? If not, should it be something we push into network or kernel-land to see that timing out of /proc ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Just setting up conky and I see the variables for the names are shown here : https://conky.sourceforge.net/variables.html
I would like to propose renaming "wireless_ap" to "wireless_bssid" to align with the naming convention of network objects.
I would also like to porpose adding a "time" metric to the wireless object. Tracking the amount of time the client (laptop, typically) is associated with that specific BSSID is necessary to identify network issues when network devices roam across multiple APs , and may be re-associating either with another BSSID , or re-associating with the same BSSID. Either way, this disconnect/reconnect is difficult to track with the basic tools. I am hoping to have this time metric show via conky to expose the issue to the user.
In doing a it of searching the concept of "time elapsed since this client has been associated to this BSSID" does not appear readily available.
Is this available at the system level ? If not, should it be something we push into network or kernel-land to see that timing out of /proc ?
Beta Was this translation helpful? Give feedback.
All reactions