Protocol » Border Gateway Protocol (Info)
Viewing 1 - 6 of 6 captures
Sort by: Newest · Name · Popularity

BGP_AS_set.cap (1.6 KB)

Packets: 18 Avg Size: 74 bytes Duration: 0.9 sec
Data Rate: 11.63 Kbps Added: 17 Sep 2008 Downloads: 564

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

BGP_notification.cap (764 bytes)

Packets: 9 Avg Size: 66 bytes Duration: 0.1 sec
Data Rate: 32.33 Kbps Added: 30 Jun 2008 Downloads: 318

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_soft_reset.cap (2.0 KB)

Packets: 17 Avg Size: 105 bytes Duration: 180.2 sec
Data Rate: 0.08 Kbps Added: 30 Jun 2008 Downloads: 262

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_hard_reset.cap (3.2 KB)

Packets: 32 Avg Size: 87 bytes Duration: 208.1 sec
Data Rate: 0.10 Kbps Added: 29 Jun 2008 Downloads: 310

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.

IBGP_adjacency.cap (2.3 KB)

Packets: 17 Avg Size: 119 bytes Duration: 62.6 sec
Data Rate: 0.25 Kbps Added: 29 Jun 2008 Downloads: 246

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.

EBGP_adjacency.cap (2.7 KB)

Packets: 24 Avg Size: 96 bytes Duration: 182.3 sec
Data Rate: 0.10 Kbps Added: 29 Jun 2008 Downloads: 256

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.

Viewing 1 - 6 of 6 captures