.. _example_protocols_bgp_parameters_disable-ebgp-connected-route-check:

##################################
Disable-Ebgp-Connected-Route-Check
##################################

Scenario to verify BGP **disable-ebgp-connected-route-check** parameter configuration.

By default, eBGP requires the neighbor's address to be on a directly connected network.
The ``disable-ebgp-connected-route-check`` global parameter disables this verification for
all eBGP neighbors, allowing sessions with peers that are not directly connected, such as
loopback-to-loopback peering. Unlike the per-neighbor ``disable-connected-check``, this
parameter applies globally to all eBGP sessions.

In this test suite, **DUT0** (AS 10) and **DUT1** (AS 20) establish an eBGP session using
loopback addresses. The first test verifies that the session establishes and routes are
exchanged when the parameter is enabled. The second test verifies that without the parameter,
the session fails to establish.

*****************************************************************************
Test eBGP - Global disable-ebgp-connected-route-check allows loopback peering
*****************************************************************************

Description
===========

This test verifies that the global ``disable-ebgp-connected-route-check`` parameter 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 the global parameter enabled on both routers,
the session establishes successfully and **DUT0** receives route 3.3.3.0/24 from **DUT1**.

Scenario
========

.. include:: disable-ebgp-connected-route-check/testebgp-globaldisable-ebgp-connected-route-checkallowsloopbackpeering

.. raw:: html

  <hr>

******************************************************************************************
Test eBGP - Session fails without disable-ebgp-connected-route-check on non-connected peer
******************************************************************************************

Description
===========

This test verifies that without ``disable-ebgp-connected-route-check``, the eBGP session
fails to establish when the neighbor address is not on a directly connected network. Both
**DUT0** and **DUT1** try to peer using loopback addresses but without the global parameter
and without static routes to reach each other's loopbacks, the connected route check fails
and the session does not establish. **DUT0** does not receive any routes from **DUT1**.

Scenario
========

.. include:: disable-ebgp-connected-route-check/testebgp-sessionfailswithoutdisable-ebgp-connected-route-checkonnon-connectedpeer

.. raw:: html

  <hr>