BGP/Quick Start: Difference between revisions

Revision as of 23:20, 28 February 2026

What this page is

This is an orientation stub for BGP-based 44Net participation. A full end-to-end quick start procedure is not published yet.

What you can do today

Use Ways to Connect to confirm BGP is the right operating model.
Make sure your network already operates BGP-capable edge routing and has a stable tunnel or transit plan.
Start account and eligibility prerequisites in Getting started and Portal Sign Up.
Review Routing and connectivity for routing concepts and decision points.
Ask implementation questions in Community and mailing lists.

What this page will cover

Prerequisites: ASN, policy ownership, and upstream coordination.
Address assignment scope and route advertisement boundaries.
Session design, failover patterns, and filtering expectations.
Validation and troubleshooting checklist.
Operational hygiene for changes and incident response.

Related pages

Contribute / next steps

If you can share a proven deployment path, capture topology, BGP edge role, filtering assumptions, and rollback strategy. Add that material through Contributing so this stub can be upgraded to a real Quick Start.

Older docs and notes

Earlier pages that may still be useful:

Routing your allocation via BGP
Announcing your allocation directly
Why can’t I announce my allocation directly?
SWIP
NSP Details
See Archive for more.

@@ Line 29: / Line 29: @@
 * [[Decentralization|How Connect, IPIP Mesh, and BGP fit together]]
-== Contribute / Next steps ==
+== Contribute / next steps ==
 If you can share a proven deployment path, capture topology, BGP edge role, filtering assumptions, and rollback strategy. Add that material through [[Contributing]] so this stub can be upgraded to a real Quick Start.