diff options
| author | Donald Sharp <sharpd@nvidia.com> | 2024-02-05 17:55:07 +0100 |
|---|---|---|
| committer | Donald Sharp <sharpd@nvidia.com> | 2024-02-05 19:33:25 +0100 |
| commit | 5842a70a198f0e72817423fd28d8b2a2be933105 (patch) | |
| tree | 2133b15dfd8e605a3442c00fee3e42a7cc824dd7 /doc/user/bgp.rst | |
| parent | Merge pull request #15291 from idryzhov/mgmtd-yang-embed (diff) | |
| download | frr-5842a70a198f0e72817423fd28d8b2a2be933105.tar.xz frr-5842a70a198f0e72817423fd28d8b2a2be933105.zip | |
doc: Document `update-source <IFNAME>` command better
There was a question in regards to how the update-source
choose the ip address for the source when using the `update-source`
command in BGP. Upon looking at the code, I was a but surprised,
so I decided to document this behavior.
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Diffstat (limited to '')
| -rw-r--r-- | doc/user/bgp.rst | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/doc/user/bgp.rst b/doc/user/bgp.rst index 66096f226..86d7c402e 100644 --- a/doc/user/bgp.rst +++ b/doc/user/bgp.rst @@ -1626,10 +1626,12 @@ Configuring Peers .. clicmd:: neighbor PEER update-source <IFNAME|ADDRESS> - Specify the IPv4 source address to use for the :abbr:`BGP` session to this - neighbour, may be specified as either an IPv4 address directly or as an + Specify the IPv4 or IPv6 source address to use for the :abbr:`BGP` session to this + neighbour, may be specified as either an IP address directly or as an interface name (in which case the *zebra* daemon MUST be running in order - for *bgpd* to be able to retrieve interface state). + for *bgpd* to be able to retrieve interface state). When there are multiple + addresses on the choosen IFNAME then BGP will use the address that matches + the most number of bits in comparison to the destination peer address. .. code-block:: frr |