From b5c7c337058146df336e5ee7fa3a2d1005a7ec63 Mon Sep 17 00:00:00 2001 From: Neel Chauhan Date: Wed, 27 Mar 2024 10:41:56 -0700 Subject: [PATCH] `openbgpd_bgp_router.md`: Clarify `router-id` section --- docs/guides/network/openbgpd_bgp_router.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/network/openbgpd_bgp_router.md b/docs/guides/network/openbgpd_bgp_router.md index c3dcffbb3c..441875e90c 100644 --- a/docs/guides/network/openbgpd_bgp_router.md +++ b/docs/guides/network/openbgpd_bgp_router.md @@ -89,7 +89,7 @@ Replace the following information: The above lines mean the following: * The `AS` line contains your BGP AS number. -* The `router-id` line contains your BGP router ID. This is an IPv4 address but can be a dummy value if you are doing IPv6-only BGP. +* The `router-id` line contains your BGP router ID. This is an IPv4 address but can be a dummy non-routable address (e.g. 169.254.x.x) if you are doing IPv6-only BGP. * The `listen on` line tells which interfaces to listen to. We should listen on all interfaces speaking BGP. * The `network` lines add the networks we want to advertise. * The `allow to ebgp prefix` line adds [RFC8212](https://datatracker.ietf.org/doc/html/rfc8212) compliance for routing security. Some hosting companies, such as BuyVM, require this.