Categories
Protocols
Reading Captures

Get Wireshark

RSS Feed

Keep up with the latest captures by subscribing to the RSS feed.

Leech

To download all captures, point your download manager to the leech page.

More Captures
Category » Multicast
Viewing 1 - 9 of 9 captures
Sort by: Newest · Name · Popularity

MSDP.cap (4.1 KB)

Packets: 35 Avg Size: 105 bytes Duration: 391.3 sec
Data Rate: 0.07 Kbps Added: 6 Jul 2008 Downloads: 363

R2 and R3 become MSDP peers and exchange keepalives. A multicast source 172.16.40.10 begins sending traffic to group 239.123.123.123, and R2 begins sending periodic source active messages to R3. Capture perspective is the R2-R3 link.

PIMv2_bootstrap.cap (712 bytes)

Packets: 8 Avg Size: 70 bytes Duration: 184.1 sec
Data Rate: 0.02 Kbps Added: 6 Jul 2008 Downloads: 346

Router 1 is the BSR and routers 2 and 3 are candidate RPs with the default priority of 0. R1 collects the RP advertisement unicasts from R2 and R3 and combines them in a bootstrap multicast to all PIM routers. Capture perspective is the R1-R3 link.

Auto-RP.cap (726 bytes)

Packets: 9 Avg Size: 62 bytes Duration: 239.3 sec
Data Rate: 0.02 Kbps Added: 5 Jul 2008 Downloads: 335

Routers 2 and 3 have been configured as candidate RPs, and multicast RP announcements to 239.0.1.39. Router 1 is the RP. R1 sees the candidate RP announcements from R2 and R3, and designates R3 the RP because it has a higher IP address (3.3.3.3). R1 multicasts the RP mapping to 224.0.1.40. The capture is from the R1-R2 link.

PIM-SM_join_prune.cap (3.8 KB)

Packets: 47 Avg Size: 67 bytes Duration: 472.9 sec
Data Rate: 0.05 Kbps Added: 5 Jul 2008 Downloads: 281

A host on R4's 172.16.20.0/24 subnet requests to join the 239.123.123.123 group. R4 sends a PIMv2 join message up to the RP (R1). Subsequent join messages are sent every 30 seconds, until R4 determines it no longer has any interested hosts and sends a prune request (packet #45). PIMv1 RP-Reachable messages for the group are also visible from R1.

mtrace.cap (238 bytes)

Packets: 2 Avg Size: 91 bytes Duration: 0.0 sec
Data Rate: 59.05 Kbps Added: 5 Jul 2008 Downloads: 252

mtrace 172.16.40.1 172.16.20.1 is issued on R1 to trace the RPF path from R4's 172.16.20.0/24 subnet to R1's 172.16.40.0/24 subnet. The capture is taken on the R1-R3 link.

mrinfo_query.cap (182 bytes)

Packets: 2 Avg Size: 63 bytes Duration: 0.0 sec
Data Rate: 122.85 Kbps Added: 5 Jul 2008 Downloads: 230

mrinfo 2.2.2.2 is issued on R1. DVMRPv3 is used to query R2 for its multicast interfaces.

PIM-DM_pruning.cap (10.2 KB)

Packets: 38 Avg Size: 258 bytes Duration: 415.0 sec
Data Rate: 0.18 Kbps Added: 4 Jul 2008 Downloads: 249

The multicast source at 172.16.40.10 begins sending traffic to the group 239.123.123.123, and PIM-DM floods the traffic down the tree. R4 has no group members, and prunes itself from the tree. R2 and R3 then realize they have no members, and each prunes itself from the tree. The capture shows R2 receiving the multicast traffic flooded from R1 and subsequently pruning itself every three minutes.

PIMv2_hellos.cap (528 bytes)

Packets: 6 Avg Size: 68 bytes Duration: 63.2 sec
Data Rate: 0.05 Kbps Added: 4 Jul 2008 Downloads: 246

Routers 1 and 2 exchange PIMv2 hello packets.

IGMPv2_query_and_report.cap (438 bytes)

Packets: 6 Avg Size: 53 bytes Duration: 125.5 sec
Data Rate: 0.02 Kbps Added: 4 Jul 2008 Downloads: 293

R1 issues IGMPv2 general membership queries to the 172.16.40.0/24 segment every 60 seconds. A host replies to each query reporting it belongs to the multicast group 239.255.255.250.

Viewing 1 - 9 of 9 captures