.. _example_protocols_bgp_neighbor_disable-connected-check: ####################### Disable-Connected-Check ####################### This scenario demonstrates how to configure the disable-connected-check option for an eBGP neighbor. By default, eBGP requires the neighbor's address to be on a directly connected network. When disable-connected-check is enabled, the router skips this verification and allows establishing eBGP sessions with neighbors that are not directly connected, such as loopback-to-loopback peering. ******************************************************************** Test eBGP - Neighbor disable-connected-check allows loopback peering ******************************************************************** Description =========== Test to verify that disable-connected-check allows an eBGP session to establish when the neighbor address is not on a directly connected network. DUT0 (AS 10) and DUT1 (AS 20) peer using their loopback addresses instead of the directly connected interface addresses. With disable-connected-check enabled, the session establishes successfully and DUT0 receives route 3.3.3.0/24 from DUT1. Scenario ======== .. include:: disable-connected-check/testebgp-neighbordisable-connected-checkallowsloopbackpeering .. raw:: html