Packet Captures

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

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

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

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

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

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

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

OSPFv3_NBMA_adjacencies.cap 12.9 KB

Submitted Sep 14, 2009

Router 3 forms OSPFv3 adjacencies with routers 1 and two across the non-broadcast multi-access (NBMA) frame relay link.

Frame Relay IPv6 OSPF

OSPFv3_broadcast_adjacency.cap 5.4 KB

Submitted Sep 14, 2009

Routers 1 and 2 form an OSPFv3 adjacency across their common Ethernet link (2001:db8:0:12::/64).

Ethernet IPv6 OSPF

OSPFv3_multipoint_adjacencies.cap 11.5 KB

Submitted Sep 14, 2009

The frame relay link connecting routers 1, 2, and 3 has been configured as a point-to-multipoint network with broadcast capability. Router 3 forms OSPFv3 adjacencies with routers 1 and 2, but no DR or BDR is elected.

Frame Relay IPv6 OSPF

OSPFv3_with_AH.cap 10.7 KB

Submitted Sep 14, 2009

The adjacency between R1 and R2 in the 2001:db8:0:12::/64 subnet is configured with IPsec AH authentication. Note the inclusion of an IPsec AH header immediately following the IPv6 header of each OSPF packet.

Ethernet IPv6 OSPF

Open Network Connection.pcapng.cap 26.8 KB

Submitted Jul 2, 2014 by correia_ramos

Open Network Connection

ARP DNS HTTP IP MEDIA NBDGM NBNS NTP SMB TCP UDP XML

PAGP.cap 2.5 KB

Submitted Nov 15, 2009

Ethernet LLC PAGP

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

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

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.

Ethernet IP PIM

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

PIMv2_hellos.cap 528 bytes

Submitted Sep 14, 2009

Routers 1 and 2 exchange PIMv2 hello packets.

Ethernet IP PIM

PPP.cap 3.6 KB

Submitted Sep 14, 2009

ICMP across a PPP serial link.

CDP ICMP IP LCP PPP

PPP_EAP.cap 2.5 KB

Submitted Jun 7, 2010

PPP link negotiation employing EAP MD5 authentication

CDP CDPCP EAP IPCP LCP PPP

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

PPP_negotiation.cap 4.6 KB

Submitted Oct 22, 2009

CDP CDPCP CHAP ICMP IP IPCP LCP PPP

PPPoE_Dual-Stack_IPv4_IPv6-with_DHCPv6.cap 6.1 KB

Submitted Sep 13, 2010 by pierky

Dual-stack PPPoE: IP (IPv4) and IPv6 with DHCPv6

Ethernet IPCP IPV6CP IPv6 LCP PAP PPP PPPOED PPPOES

PPTP_negotiation.cap 2.7 KB

Submitted Jan 16, 2015 by werteny

PPTP negotiation between PNS and PAC PPTP RFC: https://www.ietf.org/rfc/rfc2637.txt

ARP GRE IP IPCP LCP PAP PPP PPTP TCP

QinQ.pcap.cap 184 bytes

Submitted Jan 9, 2011 by Ysaad

ARP requests having two vlan IDs attached (QinQ)

ARP Ethernet VLAN