summaryrefslogtreecommitdiffstats
path: root/doc/user
diff options
context:
space:
mode:
authorDonald Sharp <sharpd@nvidia.com>2024-01-19 19:37:36 +0100
committerDonald Sharp <sharpd@nvidia.com>2024-01-19 19:37:36 +0100
commitaa3a108672fbe1c30d92271e18e34aa5c96cf22e (patch)
tree41a78551687f6ece1e97b2beb2a5044a0b28d319 /doc/user
parentMerge pull request #15175 from idryzhov/affinity-map-fixes (diff)
downloadfrr-aa3a108672fbe1c30d92271e18e34aa5c96cf22e.tar.xz
frr-aa3a108672fbe1c30d92271e18e34aa5c96cf22e.zip
doc: Update bgp unnumbered documentation
Mention the limitations of this type of peering in bgp. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Diffstat (limited to 'doc/user')
-rw-r--r--doc/user/bgp.rst5
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/user/bgp.rst b/doc/user/bgp.rst
index 11bd67674..232abfd74 100644
--- a/doc/user/bgp.rst
+++ b/doc/user/bgp.rst
@@ -1604,7 +1604,10 @@ Configuring Peers
Configure an unnumbered BGP peer. ``PEER`` should be an interface name. The
session will be established via IPv6 link locals. Use ``internal`` for iBGP
- and ``external`` for eBGP sessions, or specify an ASN if you wish.
+ and ``external`` for eBGP sessions, or specify an ASN if you wish. Finally
+ this connection type is meant for point to point connections. If you are
+ on an ethernet segment and attempt to use this with more than one bgp
+ neighbor, only one neighbor will come up, due to how this feature works.
.. clicmd:: neighbor PEER next-hop-self [force]