Port details |
- peering-manager BGP sessions management tool
- 1.9.7 net-mgmt
=0 Package not present on quarterly.This port was created during this quarter. It will be in the next quarterly branch but not the current one. - Maintainer: bofh@FreeBSD.org
 - Port Added: 2025-09-05 12:06:07
- Last Update: 2025-09-05 12:04:45
- Commit Hash: 77178f5
- Also Listed In: python
- License: APACHE20
- WWW:
- https://peering-manager.net/
- Description:
- Peering Manager was originally and still is developed by its lead
maintainer, Guillaume Mazoyer in 2017 as part of an effort to automate
BGP peering provisionning.
Since then, many organisations around the world have used Peering
Manager as their central network source of truth to empower both
network operators and automation.
Key Features
Peering Manager was built specifically to serve the needs of network
engineers and operators operating BGP networks. Below is a very brief
overview of the core features it provides.
- Autonomous system management
- BGP groups
- Internet Exchange Points
- BGP sessions with with differences between classic ones and IXP ones
- BGP communities and routing policies
- Devices and configuration rendering leveraging Jinja2
- Configuration installation for NAPALM supported platforms
- Detailed, automatic change logging
- Global search engine
- Event-driven webhooks
- Interoperability with other tools such as PeeringDB, IX-API, and more
¦ ¦ ¦ ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - USE_RC_SUBR (Service Scripts)
-
- Dependency lines:
-
- peering-manager>0:net-mgmt/peering-manager
- To install the port:
- cd /usr/ports/net-mgmt/peering-manager/ && make install clean
- To add the package, run one of these commands:
- pkg install net-mgmt/peering-manager
- pkg install peering-manager
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.- PKGNAME: peering-manager
- Flavors: there is no flavor information for this port.
- distinfo:
- TIMESTAMP = 1756827986
SHA256 (peering-manager-peering-manager-v1.9.7_GH0.tar.gz) = fa272abe40fec06d3f0c541d771d560f9a93f8940dea96b8538785a9cef32afd
SIZE (peering-manager-peering-manager-v1.9.7_GH0.tar.gz) = 8349343
No package information for this port in our database- Sometimes this happens. Not all ports have packages. This is doubly so for new ports, like this one.
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- python3.11 : lang/python311
- Test dependencies:
-
- python3.11 : lang/python311
- Runtime dependencies:
-
- py311-Jinja2>=3.1 : devel/py-Jinja2@py311
- bgpq4>0 : net-mgmt/bgpq4
- py311-django51>=5.1<5.2 : www/py-django51@py311
- py311-dj51-djangorestframework>=3.15 : www/py-dj51-djangorestframework@py311
- py311-dj51-django-debug-toolbar>=5.0 : www/py-dj51-django-debug-toolbar@py311
- py311-dj51-django-filter>=25.1 : www/py-dj51-django-filter@py311
- py311-dj51-django-netfields>=1.3 : www/py-dj51-django-netfields@py311
- py311-dj51-django-prometheus>=2.3 : www/py-dj51-django-prometheus@py311
- py311-dj51-django-redis>=5.4 : www/py-dj51-django-redis@py311
- py311-dj51-django-rq>=2.10 : devel/py-dj51-django-rq@py311
- py311-dj51-django-tables2>=2.7 : www/py-dj51-django-tables2@py311
- py311-dj51-django-taggit>=6.1 : www/py-dj51-django-taggit@py311
- py311-dj51-drf-spectacular>=0.28 : www/py-dj51-drf-spectacular@py311
- py311-dj51-drf-spectacular-sidecar>=2025 : www/py-dj51-drf-spectacular-sidecar@py311
- py311-dj51-social-auth-app-django>=5.4 : www/py-dj51-social-auth-app-django@py311
- py311-dulwich>=0.22 : devel/py-dulwich@py311
- py311-gunicorn>=23.0.0 : www/py-gunicorn@py311
- py311-markdown>=3.7 : textproc/py-markdown@py311
- py311-napalm>=5.0 : net-mgmt/py-napalm@py311
- py311-packaging>=23.2 : devel/py-packaging@py311
- py311-psycopg>=3.1 : databases/py-psycopg@py311
- py311-psycopg-pool>=3.1 : databases/py-psycopg-pool@py311
- py311-pyixapi>=0.2 : net-mgmt/py-pyixapi@py311
- py311-pynetbox>=7.3 : net-mgmt/py-pynetbox@py311
- py311-pyyaml>=6.0 : devel/py-pyyaml@py311
- py311-requests>=2.32 : www/py-requests@py311
- py311-social-auth-core>=4.5.4 : security/py-social-auth-core@py311
- redis>=8.2.1 : databases/redis
- python3.11 : lang/python311
- Library dependencies:
-
- libpq.so.5 : databases/postgresql17-client
- There are no ports dependent upon this port
Configuration Options:
- ===> The following configuration options are available for peering-manager-1.9.7:
DOCS=on: Build and/or install documentation
====> Key Value Storage Backends: you can only select none or one of them
REDIS=on: Redis Key Value Backend support
VALKEY=off: Valkey Key Value Backend support
===> Use 'make config' to modify these settings
- Options name:
- net-mgmt_peering-manager
- USES:
- cpe pgsql:13+ python:3.10-3.12
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
Number of commits found: 1
Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
Commit | Credits | Log message |
1.9.7 05 Sep 2025 12:04:45
    |
Muhammad Moinur Rahman (bofh)  |
net-mgmt/peering-manager: New port
Peering Manager was originally and still is developed by its lead
maintainer, Guillaume Mazoyer in 2017 as part of an effort to automate
BGP peering provisionning.
Since then, many organisations around the world have used Peering
Manager as their central network source of truth to empower both
network operators and automation.
Key Features
Peering Manager was built specifically to serve the needs of network
engineers and operators operating BGP networks. Below is a very brief
overview of the core features it provides.
(Only the first 15 lines of the commit message are shown above ) |
Number of commits found: 1
|