BGP/Quick Start: Difference between revisions

From 44Net Wiki
mw push
 
mw push
 
(2 intermediate revisions by the same user not shown)
Line 27: Line 27:
* [[Policies|Policies]]
* [[Policies|Policies]]
* [[Community|Community and mailing lists]]
* [[Community|Community and mailing lists]]
* [[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.
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]]
* [[FAQ|Why can’t I announce my allocation directly?]]
* [[SWIP]]
* [[NSP Details]]
* See [[Archive]] for more.

Latest revision as of 21:47, 27 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

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: