OpenVisualCloud / OpenVisualCloud/Media-Transport-Library
Rx mcast_sip_addr question
@skolelis is already working on this.
Since Aug 13, 2025.
- Dominant language
- C
- Stars
- 246
- Forks
- 88
- Avg merge
- 7d 16h
- Merged PRs (30d)
- 22
Description
Hi ALL,
I am using "tx_rtp_video_sample"to send mpegts steam and using "rx_rtp_video_sample.c" to receive the mpegts stream, it can works well.
now I need use mcast_sip_addr in st20_rx_ops to filter the same dst ip steam and found it can't work.
I add "--p_source_ip" and "--r_source_ip" cmd params in rx_rtp_video_sample.c
the tx cmd params:
./TxRtpVideoSample --p_port 0000:03:00.0 --r_port 0000:04:00.0 --p_sip 192.168.1.4 --r_sip 192.168.1.25 --p_tx_ip 239.168.77.20 --r_tx_ip 239.168.77.21 --p_udp_port 20000 --r_udp_port 20000
the rx cmd params:
./RxRtpVideoSample -p_port 0000:03:00.0 --r_port 0000:04:00.0 --p_sip 192.168.1.10 --r_sip 192.168.1.3 --p_source_ip 192.168.1.33 --r_source_ip 192.168.1.26 --p_rx_ip 239.168.77.20 --r_rx_ip 239.168.77.21 --p_udp_port 20000 --r_udp_port 20000
you can see in rx, I used the error p_source_ip and r_source_ip, but it still can get the mpegts stream.
rx log:
[20250813 05:28:48.632] - [INFO] - MTL: 2025-08-13 05:28:48, mt_dev_if_init(0), sip: 192.168.1.10
[20250813 05:28:48.632] - [INFO] - MTL: 2025-08-13 05:28:48, mt_dev_if_init(0), netmask: 255.255.255.0
[20250813 05:28:48.632] - [INFO] - MTL: 2025-08-13 05:28:48, mt_dev_if_init(0), gateway: 0.0.0.0
[20250813 05:28:48.632] - [INFO] - MTL: 2025-08-13 05:28:48, mt_dev_if_init(0), mac: a8:a1:59:ee:8c:f6
[20250813 05:28:48.632] - [INFO] - MTL: 2025-08-13 05:28:48, mt_dev_if_init(1), use mt ptp source
[20250813 05:28:48.635] - [INFO] - MTL: 2025-08-13 05:28:48, mt_dev_if_init(1), sip: 192.168.1.3
[20250813 05:28:48.635] - [INFO] - MTL: 2025-08-13 05:28:48, mt_dev_if_init(1), netmask: 255.255.255.0
[20250813 05:28:48.635] - [INFO] - MTL: 2025-08-13 05:28:48, mt_dev_if_init(1), gateway: 0.0.0.0
[20250813 05:28:48.635] - [INFO] - MTL: 2025-08-13 05:28:48, mt_dev_if_init(1), mac: a8:a1:59:ee:98:bb
[20250813 05:28:58.841] - [INFO] - MTL: 2025-08-13 05:28:58, rv_attach(0), user customized rx_burst_size 8192
[20250813 05:28:58.841] - [INFO] - MTL: 2025-08-13 05:28:58, rte_rx_flow_create(0), queue 1 succ, port 20000
[20250813 05:28:58.841] - [INFO] - MTL: 2025-08-13 05:28:58, mt_dev_get_rx_queue(0), q 1 ip 239.168.77.20 port 20000
[20250813 05:28:58.841] - [INFO] - MTL: 2025-08-13 05:28:58, rv_init_hw(0), port(l:0,p:0), queue 1 udp 20000
[20250813 05:28:58.841] - [INFO] - MTL: 2025-08-13 05:28:58, rte_rx_flow_create(1), queue 1 succ, port 20000
[20250813 05:28:58.841] - [INFO] - MTL: 2025-08-13 05:28:58, mt_dev_get_rx_queue(1), q 1 ip 239.168.77.21 port 20000
[20250813 05:28:58.841] - [INFO] - MTL: 2025-08-13 05:28:58, rv_init_hw(0), port(l:1,p:1), queue 1 udp 20000
[20250813 05:28:58.841] - [INFO] - MTL: 2025-08-13 05:28:58, rv_alloc_rtps(0,0), rtp_ring_size 1024
[20250813 05:28:58.841] - [INFO] - MTL: 2025-08-13 05:28:58, mcast_membership_report_on_action(0), send join pkt, mb_report_len 20
[20250813 05:28:58.841] - [INFO] - MTL: 2025-08-13 05:28:58, mt_mcast_join(0), join group 239.168.77.20
[20250813 05:28:58.841] - [INFO] - MTL: 2025-08-13 05:28:58, mt_mcast_join(0), with source 192.168.1.33
[20250813 05:28:58.841] - [INFO] - MTL: 2025-08-13 05:28:58, mcast_membership_report_on_action(1), send join pkt, mb_report_len 20
[20250813 05:28:58.841] - [INFO] - MTL: 2025-08-13 05:28:58, mt_mcast_join(1), join group 239.168.77.21
[20250813 05:28:58.841] - [INFO] - MTL: 2025-08-13 05:28:58, mt_mcast_join(1), with source 192.168.1.26
[20250813 05:29:18.630] - [INFO] - MTL: 2025-08-13 05:29:18, DEV(0): Avr rate, tx: 0.000048 Mb/s, rx: 13.211450 Mb/s, pkts, tx: 1, rx: 11990
[20250813 05:29:18.631] - [INFO] - MTL: 2025-08-13 05:29:18, DEV(1): Avr rate, tx: 0.000048 Mb/s, rx: 13.215859 Mb/s, pkts, tx: 1, rx: 11994
I think the tx source ip params are 192.168.1.33 and 192.168.1.26, but why it can still receiving the data from source ip 192.168.1.4 and 192.168.1.25? thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.