|
Protocol »
Border Gateway Protocol
(Info)
Viewing 1 - 6 of 6 captures
BGP_AS_set.cap (1.6 KB)
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)
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)
R1 performs a soft bidirectional reset ( BGP_hard_reset.cap (3.2 KB)
A hard reset ( IBGP_adjacency.cap (2.3 KB)
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)
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 Viewing 1 - 6 of 6 captures
|
Navigation
Armory
Online Toolbox
|