#75 Bug in multicast message delivery
A long-standing bug in the delivery of multicast messages, affecting TIPC 1.5.3 through 1.7.5 (and possibly affecting earlier versions), has been discovered. This bug may result in an incoming multicast message being incorrectly delivered to ports that published corresponding names with "node" scope, or in a multicast message not being correctly delivered to ports that published corresponding names with "cluster" or "zone" scope.
Note: This bug will only cause problems if a TIPC node's name table contains publications for the same name (or name sequence) that use both "node" and "cluster"/"zone" scope.
example: An application creates a socket that binds the name {X,Y} with "node" scope; a second application (possibly on a different node) creates another socket that binds the name {X,Y} with "cluster" scope.
Patch for TIPC 1.7.5
Logged In: YES
user_id=995681
Originator: YES
A patch for TIPC 1.7.5 is now available that fixes this issue.
File Added: 0009-Fix-bug-in-scope-checking-for-multicast-messages.txt