samplicator VS rtlmuxer

However, if the SNMP traps happen over UDP (and I think they do, SNMP generally travels over UDP) you can use something like samplicator to receive and re-send the traps while spoofing an IP address. The -S flag tells it which IP address to spoof.

This tool should help with the UDP duplication beyond the two target challenge with iptables: https://github.com/sleinen/samplicator - still, some additional details on the app/data being transmitted would help; data actually push only? Did you verify that targets other than the original host would correctly interpret the data?

You could also flip this idea on its head and point the feed at something which will replicate the packets to both the endpoints, like samplicator, which you could run on one or the other of the servers if you wanted. I use this sometimes to replicate netflow or syslog data. It does create a bit more dependency chaining, but is simple and basically 'free'.

I can't say for sure on the Fortigate, but I use Samplicator for duplicating flows to more collectors than my equipment can export to.

Samplicator is a simple tool for receiving UDP datagrams on a given port and resending them to a specified set of receivers for occasions when you need to export NetFlow traffic to more than one NetFlow collector. Can also be configured to individually specify a sampling divisor N for each receiver that will only receive one in N of the received packets. crankynetadmin adds, "It's normally used for replicating netflow data, but can also replicate any UDP traffic."

As another commented mentioned we use Samplicator. Works for lots of different UDP traffic.

Only one program at a time. OpenWebRX just runs a single instance of rtl_sdr and multiple demodulators on the IQ stream. That one program can be a multiplexer, though. For example: https://github.com/alexander-sholohov/rtlmuxer https://github.com/slepp/rtlmux It's a bit clunky, and obviously you can't tune into different chunks of the spectrum simultaneously.