Draft: RIST Sender binds to the wild card address during multicast
Compare changes
There are no changes yet
No changes between issue_181 and master
When running the ristsender with different multicast addresses but the same destination port. The sockets opened for multicast bind to "0.0.0.0" which causes both sockets to receive any data being sent to the destination port.
strace -fD --trace=bind ./ristsender -i "udp://@224.0.0.1:6655?miface=eth0&stream-id=2&multiplex-mode=1,udp://@224.0.0.2:6655?miface=eth0&stream-id=4&multiplex-mode=1" -o rist://127.0.0.1:5566 -p 1 -v 0
# Output
1723840168.822456|0.0|[INFO] Starting ristsender version: v0.2.10 libRIST library: v0.2.10 API version: 4.4.0
1723840168.823438|0.0|[INFO] Starting in Main Profile Mode
bind(3, {sa_family=AF_NETLINK, nl_pid=0, nl_groups=00000000}, 12) = 0
bind(4, {sa_family=AF_INET, sin_port=htons(6655), sin_addr=inet_addr("0.0.0.0")}, 16) = 0
1723840168.830357|0.0|[INFO] Joining multicast address: 224.0.0.1 with eth0
1723840168.830750|0.0|[INFO] Starting in Main Profile Mode
bind(5, {sa_family=AF_NETLINK, nl_pid=0, nl_groups=00000000}, 12) = 0
bind(6, {sa_family=AF_INET, sin_port=htons(6655), sin_addr=inet_addr("0.0.0.0")}, 16) = 0
1723840168.836042|0.0|[INFO] Joining multicast address: 224.0.0.2 with eth0
strace: Process 2764 attached
strace: Process 2765 attached
strace: Process 2766 attached
Closes #181 (closed)
No changes between issue_181 and master
VideoLAN code repository instance