[DISPATCH-1181] handling MAU when local address is not yet defined can result in wrong treatment

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.5.0
• Assignee: Gordon Sim
• Reporter: Gordon Sim
• Created: 09/Nov/18 23:00
• Updated: 14/Jan/19 21:28
• Resolved: 12/Nov/18 18:19

Description

When dynamically configuring routers in a network, it is possible for an MAU from one route rto reach another router for an address that the second router has not yet had defined. At present this may cause the wrong treatment to be applied to that address, which does not then get updated when the address is defined. If the default distribution is unavailable then the MAU handling exits without mapping the destination.

 

E.g.

 

start router 1

define a multicast address on it

create receiver on that address & router

start router 2

wait a bit before creating the same multicast address

create receiver on this router using the same address

send to the address on router 2

 

The address is treated as anycast (the default distribution). Using qdstat -a the incorrect (or undesired) distribution can also be seen.

Issue Links

• links to: GitHub Pull Request #418