Packet Captures
IGMP_V2.cap 1.3 KB
Submitted Mar 27, 2012 by Emieeecy
All IGMP V2 requests : Query General, Query specfic group, Join specific group, leave specific group
| Packets: 18 | Duration: 133s | Downloads: 16926 |
IGMP_V1.cap 2.0 KB
Submitted Apr 2, 2012 by Emieeecy
All IGMP V1 requests : Query General, Join specific group
| Packets: 27 | Duration: 259s | Downloads: 11785 |
PIM-SM_join_prune.cap 3.8 KB
Submitted Sep 14, 2009
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.
| Packets: 47 | Duration: 473s | Downloads: 11553 |
PIM_register_register-stop.cap 258 bytes
Submitted Sep 30, 2009 by pierky
Switch at 192.168.0.6 receives an IGMP request for the group 239.1.2.3, encapsulates the original IGMP packet in a PIM Register and sends it to the RP at 192.168.1.254. In packet #2 RP sends a Register-Stop to the switch.
| Packets: 2 | Duration: n/a | Downloads: 10950 |
PIMv2_hellos.cap 528 bytes
Submitted Sep 14, 2009
Routers 1 and 2 exchange PIMv2 hello packets.
| Packets: 6 | Duration: 63s | Downloads: 9271 |
IGMPv2_query_and_report.cap 438 bytes
Submitted Sep 14, 2009
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.
| Packets: 6 | Duration: 126s | Downloads: 8804 |
PIMv2_bootstrap.cap 712 bytes
Submitted Sep 14, 2009
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.
| Packets: 8 | Duration: 184s | Downloads: 7346 |
PIM-DM_pruning.cap 10.2 KB
Submitted Sep 14, 2009
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.
| Packets: 38 | Duration: 415s | Downloads: 7053 |
TDP.cap 2.8 KB
Submitted Sep 14, 2009
P2 and PE2 exchange Tag Distribution Protocol hellos and form an adjacency over TCP port 711.
| Packets: 33 | Duration: 47s | Downloads: 6408 |
Auto-RP.cap 726 bytes
Submitted Sep 14, 2009
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.
| Packets: 9 | Duration: 239s | Downloads: 6365 |
MSDP.cap 4.1 KB
Submitted Sep 14, 2009
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.
| Packets: 35 | Duration: 391s | Downloads: 6326 |
mtrace.cap 238 bytes
Submitted Sep 14, 2009
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.
| Packets: 2 | Duration: n/a | Downloads: 6169 |