No that is not a conflict. A port is not simply written to, a connection is first established.
A server can accept connections from multiple clients on the same port, so the correct way would be to separate the arrows on port 30104 both transporting data to dump1090.
listen means server mode and connect means client mode. (–net also means client mode for beast splitter)
But your diagram is showing the DATA flow, not which program is client and which program is server. (You would need to either annotate this or invent some graphical representation if you want to show it)
Anyway this all won’t work correctly with piaware MLAT as you are feeding data from two receivers.
In case the UAT is already connected to it’s own piaware you can devise a method to display the data on this dump1090 though.
You would have to change the beast splitter config and stop piaware from changing it.
A packet install would be easier to avoid configuration options being overwritten.
On a packet install you would need to modify the following defaults (this is one possible configuration to achieve what i described above):
--net-bo-port 30005 with
--net-only in /etc/default/dump1090-fa
Remove the listen 30005 option in /etc/default/beast-splitter
Set ENABLED to yes in /etc/default/beast-splitter
# in front of the
INPUT_OPTIONS="--serial /dev/beast" line
# in front
#INPUT_OPTIONS="--net remotehost:remoteport" change to IP:30005 so it connects to you UAT source.
For the airspy: Listen on 30005 and connect to 30004 so both piaware and dump1090 get their data from the airspy.
Now if your separate piaware instance running on the UAT device is generating MLAT data and you want to have in the dump1090 on this device then you can use the piaware-config on the UAT device to make it connect to the dump1090 on this this device
piaware-config mlat-results-format "beast,connect,localhost:30104 beast,listen,30105 beast,connect,AIRSPY-IP:30104"
There are of course other possible setups i just wanted to explain a bit more.
I might have also forgotten something. Also i’m unsure which programs will try reconnect their client after say 60 seconds when they couldn’t make a connection on startup.
For example piaware if it can’t find data on 30005 it will try again 60 seconds later.