What cause UDP Multicast Stream Statistics to double count streams
I have a multicast capture of "mpeg ts" packets. When I opend Statistics->UDP Multicast streams I notice duplication of streams in the table output instead of only unique streams. In fact known some unique streams i can see in the capture are not showing up there. E.g I see the same src IP, src prt and dst IP,dst prt pair duplicated. What is the cause of this and is there a fix. Wireshark versions tested: 2.6.2
Copy of table shown below
=========================================================================================================================================================================== UDP Multicast Streams - split.pcap: Source Address Source Port Destination Address Destination Port Packets Packets/s Avg BW (bps) Max BW (bps) Max Burst Burst Alarms Max Buffers (B) Buffer Alarms --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 172.25.245.161 1041 228.1.161.17 2001 2231 103.562677 1125104.920457 108640000.000000 10 0 2586637 2 172.25.245.159 1033 228.1.159.9 2001 1163 53.987672 586522.068215 32592000.000000 3 0 792549 2 172.25.245.159 1036 228.1.159.12 2001 2146 99.616971 1082238.776774 108640000.000000 10 0 2528386 2 172.25.245.159 1036 228.1.159.12 2001 2146 99.616971 1082238.776774 108640000.000000 10 0 2528386 2 172.25.245.157 1030 228.1.157.6 2001 1487 69.027490 749914.655655 76048000.000000 7 0 1633275 2 172.25.245.157 1039 228.1.157.15 2001 1931 89.637493 973821.720729 97776000.000000 9 0 2248536 2 172.25.245.155 1042 228.1.155.18 2001 1716 79.657114 865394.888539 86912000.000000 8 0 1967434 2 172.25.245.155 1038 228.1.155.14 2001 1287 59.743360 649051.860811 43456000.000000 4 0 960844 2 ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I have seen the same problem with 2.6.4 and 2.4.10 stable releases. How can we file a bug for the issue?