Sort by new | name | popular

Packet Captures

Showing 1 - 25 of 51

BGP_MP_NLRI.cap 2.9 KB

Submitted Jun 28, 2010

IPv6 routes are carried as a separate address family inside MP_REACH_NLRI attributes.

BGP Ethernet IP IPv6 TCP

Packets: 24 Duration: 60s Downloads: 16472

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: 12061

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: 11421

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: 10877

BGP_MD5.cap 1.7 KB

Submitted Nov 26, 2009

An EBGP with TCP MD5 authentication enabled

BGP Ethernet IP TCP

Packets: 16 Duration: 61s Downloads: 10799

RIPv2.cap 1.7 KB

Submitted Sep 14, 2009

A RIPv2 router periodically flooding its database. Capture perspective from R1's 10.0.0.1 interface.

Ethernet IP RIP UDP

Packets: 12 Duration: 141s Downloads: 10200

EIGRP_adjacency.cap 5.1 KB

Submitted Sep 14, 2009

Formation of an EIGRP adjacency between routers R1 and R2. Capture point is R1's 10.0.0.1 interface.

EIGRP Ethernet IP

Packets: 53 Duration: 104s Downloads: 10193

ISIS_p2p_adjacency.cap 21.7 KB

Submitted Sep 14, 2009

Routers 1 and 2 form a L1/L2 adjacency over a point-to-point serial link. Note that both levels of adjacency are managed with a point-to-point (P2P) hello.

HDLC ISIS

Packets: 26 Duration: 113s Downloads: 10023

BGP_redist.cap 378 bytes

Submitted Oct 28, 2009 by colinbsd

The OSPF metric is preserved and propagated within the MPLS cloud by the MP-BGP MED attribute.

BGP HDLC IP MPLS TCP

Packets: 2 Duration: n/a Downloads: 9993

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: 9821

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: 9661

OSPF_Down-Bit.cap 8.9 KB

Submitted Oct 27, 2009 by colinbsd

LSA Update with down bit set. Router R5 56.0.0.5 PE is receiving an update from the MPLS VPN, which is advertised to CE 56.0.0.6 ospf routing table. In order for for the packet(LSA) not to be re-advertised back into the MPLS cloud through another PE(2) router, PE sets the Down-bit to 1. filter: ospf.v2.options.dn == 1

CDP HDLC IP OSPF SLARP

Packets: 98 Duration: 203s Downloads: 9581

4-byte_AS_numbers_Mixed_Scenario.cap 414 bytes

Submitted Apr 30, 2010 by pierky

Router "B" (AS 2) at 172.16.3.2 does not support 4-byte AS numbers, while router "A" (AS 10.1 / 655361) at 172.16.3.1 does.

Router "A" receives an UPDATE for the 40.0.0.0/8 subnet from an external router ("D") in the AS 40.1 / 2621441 (not shown), and it forwards it to "B" (pkt n. 2): AS_PATH contains "23456 23456" (the first stands for AS 10.1, the second for the originating AS 40.1), but NEW_AS_PATH contains the real 4-byte AS numbers.

At pkt n. 3 "B" receives the same subnet directly from "D" and sends it to "A", including the original NEW_AS_PATH attribute previously appended by "D".

BGP HDLC IP TCP

Packets: 4 Duration: 60s Downloads: 9476

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: 9184

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: 8966

ISIS_level2_adjacency.cap 51.8 KB

Submitted Sep 14, 2009

Routers 3 and 4 form an IS-IS level 2 adjacency.

Ethernet ISIS LLC

Packets: 43 Duration: 85s Downloads: 8919

4-byte_AS_numbers_Full_Support.cap 1.2 KB

Submitted Apr 30, 2010 by pierky

Router at 172.16.1.2 (hostname "D", AS 40.1 / 2621441) clears a previous established peering with 172.16.1.1 (hostname "A", AS 10.1 / 655361); They both support 32-bit ASN.

While opening the new session, they negotiate the "Four-octet AS Number Capability" (pkts n. 2 and 3).

Then, both "A" and "D" send some UPDATEs containing 4-octect encoded AS_PATH attributes (pkts n. 6 and 9). Please note: WireShark may show wrong paths unless you force 4-byte encoding in the Preferences / Protocols / BGP options.

BGP HDLC IP TCP

Packets: 9 Duration: 56s Downloads: 8832

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: 8812

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

Packets: 61 Duration: 170s Downloads: 8546

RIPv2_subnet_down.cap 1.3 KB

Submitted Sep 14, 2009

RIPv2 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 #7. Capture perspective from R1's 10.0.0.1 interface.

Ethernet IP RIP UDP

Packets: 10 Duration: 86s Downloads: 8438

EBGP_adjacency.cap 2.7 KB

Submitted Sep 14, 2009

The external BGP adjacency between routers 1 and 2 is brought online and routes are exchanged. Keepalives are then exchanged every 60 seconds. Note that the IP TTL (normally 1) has been increased to 2 with ebgp-multihop to facilitate communication between the routers' loopback interfaces.

BGP Ethernet IP TCP

Packets: 24 Duration: 182s Downloads: 8055

bgplu.cap 2.1 KB

Submitted Jan 24, 2016 by mxiao

BGP Labeled Unicast

BGP IP TCP

Packets: 22 Duration: 4s Downloads: 7981

EIGRPv2_adjacency.cap 4.1 KB

Submitted Sep 14, 2009

Routers 1 and 2 form an EIGRPv2 adjacency and exchange IPv6 routes.

EIGRP Ethernet IPv6

Packets: 31 Duration: 52s Downloads: 7980

EIGRP_subnet_up.cap 1.3 KB

Submitted Sep 14, 2009

R4's 192.168.4.0/24 subnet is brought online. R1 receives updates from both R2 and R3 (only R2's update is shown in the capture). The poison-reverse in packet #9 informs R2 not to use R1 as a path to 192.168.4.0/24. The capture perspective is from R1's 10.0.0.1 interface.

EIGRP Ethernet IP

Packets: 15 Duration: 18s Downloads: 7970

BGP_AS_set.cap 1.6 KB

Submitted Sep 14, 2009

Packet #15 includes a BGP update containing both an AS sequence and an AS set in its AS path attribute.

BGP Ethernet IP TCP

Packets: 18 Duration: 1s Downloads: 7896

Showing 1 - 25 of 51