Packet Captures
bgplu.cap 2.1 KB
Submitted Jan 24, 2016 by mxiao
BGP Labeled Unicast
| Packets: 22 | Duration: 4s | Downloads: 8247 |
bgp-add-path.cap 1.1 KB
Submitted Jun 15, 2015 by xiaoquwl
BGP additional path feature. https://tools.ietf.org/html/draft-ietf-idr-add-paths-10
| Packets: 9 | Duration: 54s | Downloads: 7227 |
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.
| Packets: 1 | Duration: n/a | Downloads: 4630 |
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.
| Packets: 1 | Duration: n/a | Downloads: 4768 |
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)].
| Packets: 1 | Duration: n/a | Downloads: 4063 |
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.
| Packets: 1 | Duration: n/a | Downloads: 4000 |
no-advertise community.pcapng.cap 420 bytes
Submitted Mar 31, 2014 by altafk
BGP update packet with no-advertise community set [Community:NO_ADVERTISE (0xffffff02)] A BGP router telling its BGP peer not to advertise this route to any other peer whether EBGP or IBGP.
| Packets: 2 | Duration: n/a | Downloads: 3889 |
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.
| Packets: 24 | Duration: 60s | Downloads: 16615 |
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".
| Packets: 4 | Duration: 60s | Downloads: 9551 |
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.
| Packets: 9 | Duration: 56s | Downloads: 8906 |
BGP_MD5.cap 1.7 KB
Submitted Nov 26, 2009
An EBGP with TCP MD5 authentication enabled
| Packets: 16 | Duration: 61s | Downloads: 10882 |
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.
| Packets: 2 | Duration: n/a | Downloads: 10068 |
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.
| Packets: 17 | Duration: 63s | Downloads: 7940 |
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.
| Packets: 24 | Duration: 182s | Downloads: 8162 |
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.
| Packets: 17 | Duration: 180s | Downloads: 6761 |
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.
| Packets: 9 | Duration: n/a | Downloads: 7022 |
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.
| Packets: 32 | Duration: 208s | Downloads: 6656 |