Sort by new | name | popular

Packet Captures

Showing 1 - 25 of 51

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

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

bgp as confed sequence.pcapng.cap 432 bytes

Submitted Apr 4, 2014 by altafk

AS confederation sequence set in the BGP updates. Confederations are used to minimize IBGP mesh between BGP speakers but IBGP rules apply between EBGP sub confederation peers. AS confederation sequence are an ordered list of Autonomous systems passed within confederations.

BGP IP TCP

Packets: 1 Duration: n/a Downloads: 4527

bgp med.pcapng.cap 364 bytes

Submitted Apr 2, 2014 by altafk

BGP metric value set to 242( just a random value), used as a suggestion for peer in neighboring AS to influence incoming traffic.

BGP IP TCP

Packets: 1 Duration: n/a Downloads: 3903

bgp orf capabilty negotitation.pcapng.cap 328 bytes

Submitted Apr 3, 2014 by altafk

BGP outbound route filtering capabilities negotiation between BGP speakers, sent during route [ Cisco PrefixList ORF-Type (128)].

BGP IP TCP

Packets: 1 Duration: n/a Downloads: 3971

bgp orf prefix advertisement.pcapng.cap 336 bytes

Submitted Apr 3, 2014 by altafk

BGP prefix list sent during route refresh when outbound route filtering is configured. here we clearly see whether the prefix list is add or delete and permit or deny. Also we can see the actual network/mask sent.

BGP IP TCP

Packets: 1 Duration: n/a Downloads: 4663

bgplu.cap 2.1 KB

Submitted Jan 24, 2016 by mxiao

BGP Labeled Unicast

BGP IP TCP

Packets: 22 Duration: 4s Downloads: 7976

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

BGP_hard_reset.cap 3.2 KB

Submitted Sep 14, 2009

A hard reset (clear ip bgp) is performed on R1 for its adjacency with R2. Packet #7 shows R1 sending a packet with the TCP FIN flag set, indicating the connection is to be torn down. The TCP connection is then reestablished and UPDATEs are retransmitted.

BGP Ethernet IP TCP

Packets: 32 Duration: 208s Downloads: 6582

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

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

BGP_notification.cap 764 bytes

Submitted Sep 14, 2009

R1 has been misconfigured to expect R2 to reside in AS 65100. R2 attempts to peer with R1 advertising itself correctly in AS 65200. R1 issues a NOTIFICATION in packet #5 citing a "bad peer AS" error and terminates the TCP connection.

BGP Ethernet IP TCP

Packets: 9 Duration: n/a Downloads: 6948

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

BGP_soft_reset.cap 2.0 KB

Submitted Sep 14, 2009

R1 performs a soft bidirectional reset (clear ip bgp soft) on its adjacency with R2. The ROUTE-REFRESH message is visible in packet #7. Note that the TCP connection remains uninterrupted, and neither router views the reset as disruptive.

BGP Ethernet IP TCP

Packets: 17 Duration: 180s Downloads: 6680

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

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

EIGRPv2_subnet_transition.cap 5.3 KB

Submitted Sep 14, 2009

R4's 2001:db8:0:400::/64 subnet goes down, then comes back up roughly thirty seconds later. Capture perspective from R1's 2001:db8:0:12::1 interface.

EIGRP Ethernet IPv6

Packets: 49 Duration: 65s Downloads: 6181

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

EIGRP_goodbye.cap 1.3 KB

Submitted Sep 14, 2009

R2 designates its interface facing R1 as passive. The final hello message from R2 (packet #9) has all its K values set to 255, designating the message as a "goodbye." Capture perspective is from R1's 10.0.0.1 interface.

EIGRP Ethernet IP

Packets: 15 Duration: 43s Downloads: 7584

EIGRP_subnet_down.cap 1.8 KB

Submitted Sep 14, 2009

R4's interface to 192.168.4.0/24 goes down and the route is advertised as unreachable. Queries are issued by all routers to find a new path to the subnet but none exists, and the route is removed from the topology. Capture perspective is from R1's 10.0.0.1 interface.

EIGRP Ethernet IP

Packets: 21 Duration: 23s Downloads: 5995

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

IBGP_adjacency.cap 2.3 KB

Submitted Sep 14, 2009

Routers 3 and 4 form an internal BGP relationship. This is evidenced by the OPEN messages in packets #4 and #5, which show both routers belong to the same AS (65300). Also note that IBGP packets are not subject to a limited TTL as are EBGP packets.

BGP Ethernet IP TCP

Packets: 17 Duration: 63s Downloads: 7843

ISIS_external_lsp.cap 17.0 KB

Submitted Sep 14, 2009

R2 floods the external routes redistributed from RIP into area 10. Packet #9 includes the IP external reachability TLV. Capture perspective from R3's 10.0.10.1 interface.

Ethernet ISIS LLC

Packets: 15 Duration: 23s Downloads: 6883

ISIS_level1_adjacency.cap 27.4 KB

Submitted Sep 14, 2009

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

Ethernet ISIS LLC

Packets: 22 Duration: 58s Downloads: 7845

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

Showing 1 - 25 of 51