Lines Matching +full:data +full:- +full:width
24 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
39 as a module at run-time, run the following command as root:
40 .Bd -literal -offset indent
49 .Bd -literal -offset indent
66 .Ss Compile-time Configuration
72 .Bd -literal -offset indent
73 CFLAGS+=-DSIFTR_IPV6
80 In the IPv4-only (default) mode, standard dotted decimal notation (e.g.
83 and standard colon-separated hex notation (see RFC 4291) is used to format IPv6
85 .Ss Run-time Configuration
89 interface to export its configuration variables to user-space.
91 .Bl -tag -offset indent -width Va
104 .Bl -tag -offset indent -width Va
113 .Bl -tag -offset indent -width Va
119 .Bl -tag -offset indent -width Va
140 enabled and starts collecting data from the running kernel.
142 The fields are tab delimited key-value
144 .Bd -literal -offset indent
150 .Bl -tag -offset indent -width Va
154 .Bl -tag -offset indent -width Va
158 .Bl -tag -offset indent -width Va
163 .Bl -tag -offset indent -width Va
167 .Bl -tag -offset indent -width Va
171 .Bl -tag -offset indent -width Va
178 .Qq Compile-time Configuration
182 The second type of log message is written to the file when a data log message
184 The text below shows an example data log triggered by an IPv4
186 The data is CSV formatted.
187 .Bd -literal -offset indent
194 .Bl -tag -offset indent -width Va
203 .Bl -tag -offset indent -width Va
210 .Bl -tag -offset indent -width Va
213 or colon-separated hex (IPv6 packet) notation.
215 .Bl -tag -offset indent -width Va
219 .Bl -tag -offset indent -width Va
222 or colon-separated hex (IPv6 packet) notation.
224 .Bl -tag -offset indent -width Va
228 .Bl -tag -offset indent -width Va
232 .Bl -tag -offset indent -width Va
236 .Bl -tag -offset indent -width Va
240 .Bl -tag -offset indent -width Va
245 .Bl -tag -offset indent -width Va
250 .Bl -tag -offset indent -width Va
254 .Bl -tag -offset indent -width Va
258 .Bl -tag -offset indent -width Va
264 .Bl -tag -offset indent -width Va
268 .Bl -tag -offset indent -width Va
272 .Bl -tag -offset indent -width Va
276 .Bl -tag -offset indent -width Va
283 .Bl -tag -offset indent -width Va
287 .Bl -tag -offset indent -width Va
291 .Bl -tag -offset indent -width Va
295 .Bl -tag -offset indent -width Va
299 .Bl -tag -offset indent -width Va
303 .Bl -tag -offset indent -width Va
305 The current number of unacknowledged bytes in-flight.
308 .Bl -tag -offset indent -width Va
312 .Bl -tag -offset indent -width Va
320 .Bl -tag -offset indent -width Va
331 and ceases collecting data from the running kernel.
333 The fields are tab delimited key-value pairs which provide statistics about
335 .Bd -literal -offset indent
342 flow_list=10.1.1.2;32291-10.1.1.3;5001,10.1.1.2;58544-10.1.1.3;5001,
346 .Bl -tag -offset indent -width Va
350 .Bl -tag -offset indent -width Va
354 .Bl -tag -offset indent -width Va
361 .Bl -tag -offset indent -width Va
368 .Bl -tag -offset indent -width Va
372 .Bl -tag -offset indent -width Va
378 .Bl -tag -offset indent -width Va
384 .Bl -tag -offset indent -width Va
389 .Bl -tag -offset indent -width Va
394 .Bl -tag -offset indent -width Va
399 .Bl -tag -offset indent -width Va
404 .Bl -tag -offset indent -width Va
408 .Bl -tag -offset indent -width Va
410 A CSV list of TCP flows that triggered data log messages to be generated since
414 .Qq local_ip;local_port-foreign_ip;foreign_port .
415 If there are no entries in the list (i.e., no data log messages were generated),
421 The total number of data log messages found in the log file for a module
422 enable/disable cycle should equate to total_tcp_pkts - total_skipped_tcp_pkts.
440 .Bd -literal -offset indent
441 ----------------------------------
443 ----------------------------------
449 ----------------------------------
454 ---------
456 ---------
462 ----------------------------------
467 ----------------------------------
469 ----------------------------------
475 interface to manage writing data to disk.
497 allows you to correlate and observe the cause-and-affect relationship between
505 to gather the necessary data to piece together the complete picture.
507 data.
525 the data structure shared between the threads of operation.
545 they could not successfully trigger a data log message.
552 .Bl -enum
559 .Bl -dash
620 project 2008-2009.
627 .An -nosplit
638 .Bl -dash
644 to cope with bursty network traffic, but sustained high packet-per-second
673 There is no way to filter which TCP flows you wish to capture data for.
674 Post processing is required to separate out data belonging to particular flows
691 However, we suspect (based on analogies with other hash table performance data)
718 and processing overhead on the system for non-TCP packets as well.
719 Hooking in at the IP layer is also not ideal from the data gathering point of
723 cannot observe the cause-and-affect relationship between inbound events and the
734 tend to trigger outbound events, allowing the cause-and-effect to be observed