#230 multiple Subscribers with same comId, sourceIPs but different destinationIPs not working

[Stefan Bender]

If a telegram with multiple destinationIPs using the same source Ips and comIds is defined, only one subscriber can be created.
The issue lies with trdp_queueFindSubAddr() in trdp_utils.c:357, where the destinationIP is not checked to find already existing elements.

[Stefan Bender]

Setting destIpAddr to 0 in tlp_subscribe() in trdp_if.c when it is not a multicast address to avoid the subscriber not being detected because of a deviating destinationIP.

[Stefan Bender]

Added provisions in trdp_queueFindSubAddr() for systems, that return no destination address (e.g. lwIP)

[Bernd Löhr]

Is related to #235, #243, #236

[Matthias Mossner]

unfortunately wrote another ticket for that: #257 ! And also implemented another solution for the problem - gathering out at in tlp_subscribe whether it is a mcast address and set it and only check in trdp_queueFindSubAddr for differing mcast.
Why? In our scenarios another element is only needed in case of mcast cause then IGMP packet is sent so that ethernet switch forwards that multicast group to device.
Is there another scenario on your side or do you also only need several subscribers when mcast is used with several mcast groups?

[Stefan Bender]

Continued in ticket #257