Routing: Difference between revisions

Revision as of 23:20, 28 February 2026

What this page is

This page is the routing orientation hub for 44Net participation. Use it to understand how traffic reaches your systems across Connect, mesh, or BGP-operated networks. For a conceptual overview of why these methods are separate, see Decentralization.

What you can do today

Pick the operating model that matches your environment in Ways to Connect.
For fast single-endpoint onboarding, use 44Net Connect Quick Start.
For shared routing environments, review IPIP Mesh Quick Start orientation.
For independently routed infrastructure, review BGP Quick Start orientation.
Confirm address and naming prerequisites in Request Address Space and DNS.

What this page will cover

Core routing concepts used by 44Net operators.
Traffic flow patterns: behind NAT, shared gateways, and BGP edges.
Prefix planning and route advertisement boundaries.
Troubleshooting methodology for reachability and asymmetry.
Operational checklists for changes and rollback.

Related pages

Contribute / next steps

If you troubleshoot a routing issue, document topology, path expectation, observed path, and fix. Submit concise incident notes through Contributing so this page can grow into a practical reference.

Older docs and notes

Earlier pages that may still be useful:

@@ Line 31: / Line 31: @@
 * [[Decentralization|How Connect, IPIP Mesh, and BGP fit together]]
-== Contribute / Next steps ==
+== Contribute / next steps ==
 If you troubleshoot a routing issue, document topology, path expectation, observed path, and fix. Submit concise incident notes through [[Contributing]] so this page can grow into a practical reference.