I am interested in testing out lidi, and I'm curious whether there is a way to use lidi like I currently use udpcast.
First question: using udpcast, I can send data from the sender's STDIN, and receive data via the receiver's STDOUT. For example:
$ udp-sender --async --broadcast --rexmit-hello-interval 100 --autostart 1 \
--mcast-rdv-address 127.0.0.1 < /tmp/my_input_file
$ udp-receiver --nosync --interface lo > /tmp/my_output_file
From my understanding of lidi's documentation, I could use netcat as an intermediary, since netcat supports reading from STDIN and writing to STDOUT, but I wonder if there is an easier way.
Second question: if packet loss causes corruption of a udpcast transfer, udp-receiver will exit with a non-zero exit code. This makes it easy to detect transfer errors in shell scripts. Does lidi offer this functionality? I'm imagining diode-send and diode-receive running for a single transfer, and diode-receive's exit code reflecting whether the transfer was successful.
Thanks in advance!
I am interested in testing out lidi, and I'm curious whether there is a way to use lidi like I currently use udpcast.
First question: using udpcast, I can send data from the sender's STDIN, and receive data via the receiver's STDOUT. For example:
From my understanding of lidi's documentation, I could use netcat as an intermediary, since netcat supports reading from STDIN and writing to STDOUT, but I wonder if there is an easier way.
Second question: if packet loss causes corruption of a udpcast transfer,
udp-receiverwill exit with a non-zero exit code. This makes it easy to detect transfer errors in shell scripts. Does lidi offer this functionality? I'm imaginingdiode-sendanddiode-receiverunning for a single transfer, anddiode-receive's exit code reflecting whether the transfer was successful.Thanks in advance!