sam/obmp-docker
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix GoBGP BMP target: use host IP, not collector hostname

Browse Source 
GoBGP's BMP config requires a literal IP — 'obmp-collector' failed
to parse and the container crash-looped. Point BMP export at the
docker host IP (10.40.40.202) where the collector publishes port
5000; stable across container recreation.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
sam 2026-05-19 07:51:41 -07:00
parent 8ced62e491
commit af4b816bef
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
gobgp/gobgpd.conf
View File

@ -58,13 +58,15 @@
afi-safi-name = "ipv6-unicast"
# --- BMP export to the OpenBMP collector ------------------------------------
# GoBGP connects OUT to the collector. "obmp-collector" resolves on the shared
# compose network; port 5000 is the collector's BMP listener.
# GoBGP connects OUT to the collector. GoBGP's BMP config requires a literal
# IP (it cannot resolve a hostname), so we target the docker host IP where the
# collector publishes port 5000 -- stable across container recreation, unlike
# the collector's internal docker IP. Matches HOST_IP in .env.
# route-monitoring-policy = "pre-policy" exports the Adj-RIB-In (received
# routes, pre import-policy) -- consistent with the rest of the OpenBMP fleet.
[[bmp-servers]]
[bmp-servers.config]
address = "obmp-collector"
address = "10.40.40.202"
port = 5000
route-monitoring-policy = "pre-policy"
statistics-timeout = 3600