fstrm_replay1
Replay saved frame streams data to a socket connection.
Usage
fstrm_replay -t
content-type
-r
file
[-r
file ...]
[-u
socket-path]
[-a
IP
-p
port]
fstrm_replay --type
content-type
--read
file
[--read
file ...]
[--unix
socket-path]
[--tcp
IP
--port
port]
Overview
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).
Options
- -t content-type | --type content-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_replaywill fail.
- -r file | --read file
-
Read data from file. Multiple files can be given with multiple
-roptions. Files which cannot be opened, or do not contain valid Frame Streams data will be skipped.
- -u socket-path | --unix socket-path
-
Connect to Unix domain socket-path to write Frame Streams data. Only one of
-uor-amay be given.
- -a IP | --tcp IP
-
Connect to TCP address IP to write Frame Streams data. Only one of
-uor-amay be given. Use of-arequires a port given with-p.
- -p port | --port port
-
If
-ais given, use TCP port port to write Frame Streams data.
Examples
Replay dnstap data over UNIX domain socket:
fstrm_replay -t protobuf:dnstap.Dnstap \ -u /var/run/named/dnstap.sock -r dnstap-log.fstrm
Releases
Unchanged in 5 releases since Debian 10 (Buster).