Output of netgrind

When using netgrinds passive measurement method, the measured metrics are basically a time interval for the measurement and the throughput during this interval. Further these metrics are connected to a specific flow id and the source or destination node of this flow.

# ID  begin    end  through
#       [s]    [s] [Mbit/s]
D  0 29.354 29.402 0.000000
S  0 29.400 29.450 0.000000
D  1 29.402 29.450 0.000000
S  1 29.450 29.501 0.000000
S  0 29.501 29.551 0.000000

Together with the final report, which shows the corresponding IPs to a node id's source or destination, one can reconstruct the dataflow in the mesh. The source node is always the node, that detects a data connection to a new node which has not been in the measurement so far. A simple example:

We start our passive measurement at node A
A is listening for new tcp/udp connections within the given subnet
Once A establishes a new connection to a node B, the measurement starts, as seen above
If now during this measurement B establishes a connection to another node C, then a new flow will be created with B as source node and C as destination node

#   0 S: 192.168.9.17/137.226.54.131, sbuf = 16384/0, rbuf = 87380/0 (real/req),
 flow duration = 29.990s/30.000s (real/req), through = 0.000639/0.000000Mbit/s (out/in)
#   0 D: 192.168.9.9/137.226.54.148, sbuf = 16384/0, rbuf = 87380/0 (real/req),
 flow duration = 29.994s/30.000s (real/req), through = 0.000711/0.000000Mbit/s (out/in)

#   1 S: 192.168.9.9/137.226.54.148, sbuf = 16384/0, rbuf = 87380/0 (real/req), 
 flow duration = 29.990s/30.000s (real/req), through = 0.000639/0.000000Mbit/s (out/in)
#   1 D: 192.168.9.12/137.226.54.159, sbuf = 16384/0, rbuf = 87380/0 (real/req), 
 flow duration = 29.994s/30.000s (real/req), through = 0.000711/0.000000Mbit/s (out/in)

Outputs for active measurements as known from Flowgrind are in the same kind as described in the "Output" section of Flowgrind.