BGP: Difference between revisions

Content added Content deleted
Line 178: Line 178:
<br />
<br />


= iBGP vs eBGP =
= EBGP vs IBGP =




{| class="wikitable"
{| class="wikitable"
|-
|-
! eBGP !! iBGP
! EBGP !! IBGP
|-
|-
| peering between two different AS || is between same AS
| Peering is between two different AS || Peering is between same AS
|-
|-
| Routes learned from eBGP peer will be advertised to other peers (EBGP or IBGP) || routes learned from IBGP peer will not be advertised to other IBGP peers but can be advertised to an EBGP peer.
| Routes learned from eBGP peer will be advertised to other peers(EBGP or IBGP) || Routes learned from IBGP peer will not be advertised to other IBGP peers, can be advertised to EBGP peer.
|-
|-
| By default, EBGP peers are set with TTL = 1, which means neighbors are assumed to be directly connected.<br />We can change this behavior for EBGP by using command “neighbor x.x.x.x ebgp-multihop <TTL>”. <br />Multihop is the term used in EBGP only.|| For IBGP peers dont need to be directly connected.
| EBGP peers are set with TTL = 1, neighbors are assumed to be directly connected.<br />Can change this behavior for EBGP by “neighbor x.x.x.x ebgp-multihop <TTL>”. <br />Multihop is the term used in EBGP only.|| For IBGP peers dont need to be directly connected.
|-
|-
| routes have administrative distance of 20 || whereas IBGP has 200
| Routes have AD of 20 || Routes have AD of 200
|-
|-
| Next hop remains unchanged when route is advertised to IBGP peer.<br />It is changed when it is advertised to EBGP peer by default.<br />This default behavior of IBGP can be changed by the command “neighbor x.x.x.x next-hop-self”;<br /> this changes the next hop, while advertising, as a local route. || Next-hop IP will not be changed when adv prefixes to another IBGP.
| Next hop is changed on advertised routers || Next-hop IP will not be changed when adv prefixes to another IBGP
|}
|}


Retrieved from "https://aman.awiki.org/wiki/BGP"