An RV publisher automatically joining an IGMP group will result in undesired traffic from other RV publishers for the same multicast group going to this machine. How to avoid this?
Article ID: KB0088601
Updated On:
| Products | Versions |
|---|---|
| TIBCO Rendezvous | - |
| Not Applicable | - |
Description
Resolution:
Description
========
For a UDP multicast sender, it is not necessary to join the multicast group to be able to send datagrams to the multicast group. However, when part two - multicast groups is specified for the network parameter, RV publishers will join the IGMP group. This implies that if RV publishers on another host in the same network is also publishing on the same multicast group, the traffic will also goes to this machine regardless of whether there are RV listeners running.
Example:
On Machine A, tibrvsend -network ";228.1.1.1" test
On Machine B, tibrvsend -network ";228.1.1.1" another.subject
The packet send from B will arrive at machine A ( and vice versa). You can verify this by "netstat -s" statistics of UDP received packets. This is not necessary since machine A is not interested in any specific subject (except the normal protocol/advisory message).
Environment
=========
All
Resolution
=========
To prevent the unnecessary traffic from going to the publisher host in the preceeding scenario set the network parameter of the RV publisher as ";;[multicast address]"
In this case, the RV publisher will not join the IGMP group. Since the part three - send address specify that the data should be sent to the multicast address, it is equivalent to ";[multicast address" in terms of the message delivery. However, it saves the network bandwidth of sending the data to the undesired host.
Keywords:
=========
IGMP
Description
========
For a UDP multicast sender, it is not necessary to join the multicast group to be able to send datagrams to the multicast group. However, when part two - multicast groups is specified for the network parameter, RV publishers will join the IGMP group. This implies that if RV publishers on another host in the same network is also publishing on the same multicast group, the traffic will also goes to this machine regardless of whether there are RV listeners running.
Example:
On Machine A, tibrvsend -network ";228.1.1.1" test
On Machine B, tibrvsend -network ";228.1.1.1" another.subject
The packet send from B will arrive at machine A ( and vice versa). You can verify this by "netstat -s" statistics of UDP received packets. This is not necessary since machine A is not interested in any specific subject (except the normal protocol/advisory message).
Environment
=========
All
Resolution
=========
To prevent the unnecessary traffic from going to the publisher host in the preceeding scenario set the network parameter of the RV publisher as ";;[multicast address]"
In this case, the RV publisher will not join the IGMP group. Since the part three - send address specify that the data should be sent to the multicast address, it is equivalent to ";[multicast address" in terms of the message delivery. However, it saves the network bandwidth of sending the data to the undesired host.
Keywords:
=========
IGMP
Issue/Introduction
An RV publisher automatically joining an IGMP group will result in undesired traffic from other RV publishers for the same multicast group going to this machine. How to avoid this?
Feedback
Yes
No
Powered by
