Sort by new | name | popular

Packet Captures

Showing 76 - 100 of 123

RIPv1_subnet_down.cap 1.0 KB

Submitted Sep 14, 2009

RIPv1 routes are being flooded on the R1-R2 link. R2's connection to 192.168.2.0/24 goes down, and the route is advertised as unreachable (metric 16) in packet #5. Capture perspective from R1's 10.0.1.1 interface.

Ethernet IP RIP UDP

Packets: 8 Duration: 58s Downloads: 5898

RIPv1.cap 876 bytes

Submitted Sep 14, 2009

A RIPv1 router periodically flooding its database. Capture perspective from R1's 10.0.1.1 interface.

Ethernet IP RIP UDP

Packets: 6 Duration: 65s Downloads: 6869

RADIUS.cap 775 bytes

Submitted Sep 14, 2009

A RADIUS authentication request is issued from a switch at 10.0.0.1 on behalf of an EAP client. The user authenticates via MD5 challenge with the username "John.McGuirk" and the password "S0cc3r".

Ethernet IP RADIUS UDP

Packets: 4 Duration: n/a Downloads: 13461

PPP_TCP_compression.cap 1.5 KB

Submitted Sep 14, 2009

A telnet session is established to 191.1.13.3 across a PPP link performing TCP header compression. The user at 191.1.13.1 logs in with the password "cisco" and terminates the connection.

IP LCP PPP TCP

Packets: 43 Duration: 3s Downloads: 5847

PPP.cap 3.6 KB

Submitted Sep 14, 2009

ICMP across a PPP serial link.

CDP ICMP IP LCP PPP

Packets: 50 Duration: 83s Downloads: 7263

PIMv2_hellos.cap 528 bytes

Submitted Sep 14, 2009

Routers 1 and 2 exchange PIMv2 hello packets.

Ethernet IP PIM

Packets: 6 Duration: 63s Downloads: 8312

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.

Ethernet IP PIM

Packets: 8 Duration: 184s Downloads: 6647

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.

Ethernet IGMP IP PIM

Packets: 47 Duration: 473s Downloads: 10208

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.

Ethernet IP PIM UDP

Packets: 38 Duration: 415s Downloads: 6350

path_MTU_discovery.cap 6.2 KB

Submitted Sep 14, 2009

Tracepath is used to determine the MTU of the path between hosts 192.168.0.2 and .1.2. Packet #6 contains an ICMP "fragmentation needed" message, indicating the MTU for that hop is 1400 bytes.

Ethernet ICMP IP UDP

Packets: 8 Duration: n/a Downloads: 11417

OSPF_with_MD5_auth.cap 4.6 KB

Submitted Sep 14, 2009

An OSPF adjacency is formed between two routers configured to use MD5 authentication.

Ethernet IP OSPF

Packets: 34 Duration: 63s Downloads: 7009

OSPF_type7_LSA.cap 3.6 KB

Submitted Sep 14, 2009

Area 10 is configured as a not-so-stubby area (NSSA). The capture records the adjacency formed between routers 2 and 3. The link state update in packet #11 includes several type 7 LSAs from R2. Capture perspective from R3's 10.0.10.1 interface.

Ethernet IP OSPF

Packets: 25 Duration: 32s Downloads: 7974

OSPF_point-to-point_adjacencies.cap 9.9 KB

Submitted Sep 14, 2009

The frame relay network between four routers is configured with point-to-point subinterfaces. No DR/BDR is required as all adjacencies are point-to-point. Capture perspective from R1.

Frame Relay IP OSPF

Packets: 93 Duration: 35s Downloads: 9695

OSPF_NBMA_adjacencies.cap 11.7 KB

Submitted Sep 14, 2009

Formation of OSPF adjacencies across a Non-broadcast Multiaccess (NBMA) frame relay topology. Neighbors have been manually specified on all routers, with R1 configured to become the DR. No BDR is present. Capture perspective from R1.

Frame Relay IP OSPF

Packets: 99 Duration: 66s Downloads: 6647

OSPF_multipoint_adjacencies.cap 16.3 KB

Submitted Sep 14, 2009

Routers 1 through 4 are configured to view the non-broadcast frame relay network as a point-to-multipoint topology. Adjacencies are formed without the need of a DR or BDR. Note that inverse ARP was used to dynamically learn the addresses of neighbors.

ARP Frame Relay IP LMI OSPF Q933

Packets: 196 Duration: 277s Downloads: 7870

OSPF_LSA_types.cap 4.0 KB

Submitted Sep 14, 2009

Capture of adjacency formation between OSPF routers 4 and 5 in area 20. Packet #12 contains LSAs of types 1, 2, 3, 4, and 5.

Ethernet IP OSPF

Packets: 30 Duration: 63s Downloads: 10757

OSPF_broadcast_adjacencies.cap 8.4 KB

Submitted Sep 14, 2009

Three routers form OSPF adjacencies across a broadcast segment. All interface priorities are left default, so R3 (with the highest router ID) becomes the DR, and R2 (with the next-highest router ID) becomes the BDR. Capture perspective from R1.

Ethernet IP OSPF

Packets: 74 Duration: 95s Downloads: 8847

NHRP_registration.cap 648 bytes

Submitted Sep 14, 2009

R2 registers a multipoint GRE tunnel with R1. Capture perspective from the R1-R5 link.

Ethernet GRE IP NHRP

Packets: 4 Duration: n/a Downloads: 6479

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.

Ethernet IGMP IP

Packets: 2 Duration: n/a Downloads: 5590

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.

Ethernet IP MSDP TCP

Packets: 35 Duration: 391s Downloads: 5723

mrinfo_query.cap 182 bytes

Submitted Sep 14, 2009

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

DVMRP Ethernet IGMP IP

Packets: 2 Duration: n/a Downloads: 5100

MPLS_encapsulation.cap 1.3 KB

Submitted Sep 14, 2009

Capture taken from the PE1-P1 link. ICMP traffic between CE1 and CE2 is encapsulated outbound with MPLS label 18. Note that returning traffic is not labeled, due to penultimate hop popping (PHP).

Ethernet ICMP IP MPLS

Packets: 10 Duration: n/a Downloads: 10795

mGRE_ICMP.cap 3.7 KB

Submitted Sep 14, 2009

R2 begins sending ICMP traffic to R4, but it currently only has a GRE tunnel open to R1. The first two ICMP requests (packets #1 and #4) are routed through R1 while R2 sends an NHRP request to R1 for R4's spoke address. Once a GRE tunnel is dynamically built between spoke routers R2 and R4, R2 begins routing the ICMP traffic directly to R4. Capture perspective from the R2-R5 link.

Ethernet GRE IP NHRP

Packets: 24 Duration: 10s Downloads: 9708

LDP_adjacency.cap 5.7 KB

Submitted Sep 14, 2009

PE1 and P1 multicast LDP hellos to 224.0.0.2 on UDP port 646. They then establish an adjacency on TCP port 646 and exchange labels.

Ethernet IP LDP TCP UDP

Packets: 61 Duration: 108s Downloads: 8659

ISAKMP_sa_setup.cap 2.0 KB

Submitted Sep 14, 2009

An ISAKMP session is established prior to setting up an IPsec tunnel. Phase one occurs in main mode, and phase two occurs in quick mode.

Ethernet IP ISAKMP UDP

Packets: 9 Duration: n/a Downloads: 10172

Showing 76 - 100 of 123