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
This is clearly nonsensical. A possible reason for this is that hopglass gathers these numbers through separate queries at different times. In an attempt to do better merging of these queries, it could use max(wifi, total) as the count actually printed into the JSON.
"total clients" querries the current (batman) claimtable.
"wifi-clients" querries the wifi driver.
if batman and wifidriver have different gate times or different "keep alive/ttl-values": that's what gluon is reporting.
We occasionally see nodes with data like this in the hopglass JSON file:
This is clearly nonsensical. A possible reason for this is that hopglass gathers these numbers through separate queries at different times. In an attempt to do better merging of these queries, it could use
max(wifi, total)
as the count actually printed into the JSON.Cc @nudelkiste
The text was updated successfully, but these errors were encountered: