fstrm_replay(1)

💖 fstrm_replay — the girlies' guide 💖

okay so bestie, welcome to fstrm_replay from the General Commands Manual section (yes it's a section-1 command, main character energy only) ✨

🌸 NAME 🌸

fstrm_replay — replay your saved Frame Streams data straight into a socket connection. it's giving rerun the whole tape, but make it network 💅

🦋 SYNOPSIS 🦋

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 ]

short flags girlies and long flags girlies, both served, no cap 🫶

✨ DESCRIPTION ✨

so here's the vibe: fstrm_replay connects to a Frame Streams receiver — either on the socket-path you gave it as a UNIX domain socket, or on the TCP address and port you gave it — and then it reads data of the content-type you supplied, out of the file(s) you supplied, and sends it over 🌈

that's it. that's the whole plot. she reads, she sends, she slays 💖

👑 OPTIONS 👑

• -t content-type, --type content-type — tell her the content-type to read from the files and send to the Frame Streams socket. files whose content-type differ are skipped — like, not invited to the party 🙈. and if the socket server doesn't accept the content-type? fstrm_replay will fail. no cap, it just will 💀
• -r file, --read file — read data from file. you can stack multiple files by giving multiple -r options, go off 👑. files which cannot be opened, or which don't contain valid Frame Streams data, will be skipped — she's not gonna fight them, she's just gonna move on 🧚
• -u socket-path, --unix socket-path — connect to the UNIX domain socket-path to write Frame Streams data. ⚠️ only one of -u or -a may be given — pick a lane bestie, you cannot have both 💅
• -a IP, --tcp IP — connect to TCP address IP to write Frame Streams data. ⚠️ only one of -u or -a may be given, same rule, same energy. and using -a requires a port given with -p — she needs her little port bestie or she's not going anywhere 🎀
• -p port, --port port — if -a is given, use TCP port port to write Frame Streams data. that's the whole job. iconic, honestly 🌟

🌈 EXAMPLES 🌈

replay dnstap data over a UNIX domain socket, the classic:

fstrm_replay -t protobuf:dnstap.Dnstap \
     -u /var/run/named/dnstap.sock -r dnstap-log.fstrm

look at her go 😭💖

🎀 SEE ALSO 🎀

• fstrm_capture(1), fstrm_dump(1)
• Frame Streams C Library https://farsightsec.github.io/fstrm

and that's the whole page, bestie 🫶 this was fstrm_replay(1) from the General Commands Manual, version fstrm_replay(1) — go forth and replay, you've got this ⭐💜