fstrm_replay - Replay saved Frame Streams data to a socket connection.
Contents
Description
fstrm_replay connects to a Frame Streams receiver on either the given UNIX domain socket-path or TCP
address and port, then reads and sends data of the supplied content-type from the given file(s).
Examples
Replay dnstap data over UNIX domain socket:
fstrm_replay -t protobuf:dnstap.Dnstap \
-u /var/run/named/dnstap.sock -r dnstap-log.fstrm
Name
fstrm_replay - Replay saved Frame Streams data to a socket connection.
Options
-tcontent-type|--typecontent-type
Specify the content-type to read from files and send to the Frame Streams socket. Files whose
content-type differ are skipped. If the socket server does not accept the content-type,
fstrm_replay will fail.
-rfile|--readfile
Read data from file. Multiple files can be given with multiple -r options. Files which cannot be
opened, or do not contain valid Frame Streams data will be skipped.
-usocket-path|--unixsocket-path
Connect to Unix domain socket-path to write Frame Streams data. Only one of -u or -a may be
given.
-aIP|--tcpIP
Connect to TCP address IP to write Frame Streams data. Only one of -u or -a may be given. Use of
-a requires a port given with -p.
-pport|--portport
If -a is given, use TCP port port to write Frame Streams data.
See Also
fstrm_capture(1), fstrm_dump(1), Frame Streams C Library https://farsightsec.github.io/fstrmfstrm_replay(1)
Synopsis
fstrm_replay-tcontent-type-rfile[-rfile...][-usocket-path][-aIP-pport]fstrm_replay--typecontent-type--readfile[--readfile...][--unixsocket-path][--tcpIP--portport]
