"meshnode_traffic" counter split (rx/tx, fwd?)

[Adorfer]

on current version (commit/9d8e9076e4a3471125955618eec64c75928dd3e3) i observe
meshnode_traffic_tx and
meshnode_traffic_rx
split in "mgmt_traffic" and "traffic"

What of thas is "client rx/tx" and what is "mesh fwd rx/tx"?
(I got those values separated in alfred, to determine what the mesh network and what the client-ap was taking. For an Offloader (without client) i don't see any significant traffic at the moment. And this value would be of great interest.)

[dereulenspiegel]

Currently these structures are simply taken from announced. It is possible that there are probably more information I need to model as a struct or that there is work in announced necessary to get these values. Next week I will have a closer look at this.

[Adorfer]

If you take look at the structs anyway, id's like to make some different markup for "wifimesh" and "lanmesh". I do not know how announced reports this, but perhaps as "ibss/mesh" vs "eth0/eth1". (and meshvpn....)

[Adorfer]

as i am new to announced: what whould be the right way to dumpe the information sent by a node.
either by calling /usr/bin/respondd manually on the node.
Or on the collecting backend machine.

in the alfred it was the value of "forward" (see below)

{"node_id":"60e327600468","clients":{"wifi":1,"total":1,"wifi24":1,"wifi5":0},"rootfs_usage":0.59375,"gateway":"04:ca:ff:ee:ba:10","processes":{"total":50,"running":2},"memory":{"cached":3136,"total":28540,"buffers":1632,"free":4976},"uptime":190325.84,"idletime":157880.62,"mesh_vpn":{"groups":{"backbone":{"peers":{"w1":{"established":78822.364},"w7":null,"w3":null,"w2":null,"w12":null,"w11":null,"w14":null,"w15":null,"w6":null,"w0":{"established":78824.725},"w5":null,"w4":null,"w16":null,"w13":null,"w9":null,"w8":null}}}},"traffic":{"tx":{"packets":3399848,"dropped":1694,"bytes":793308987},"rx":{"bytes":5746683512.9999995,"packets":7021601},"forward":{"bytes":4729472436.9999999,"packets":6824421},"mgmt_tx":{"bytes":591336392,"packets":3495858},"mgmt_rx":{"bytes":1905201924,"packets":12285844}},"loadavg":0}