Routing: Difference between revisions
mw push |
mw push |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
== What you can do today == | == What you can do today == | ||
* Pick the operating model that matches your environment in [[ | * Pick the operating model that matches your environment in [[Provisioning Methods|Provisioning Methods]]. | ||
* For fast single-endpoint onboarding, use [[44Net Connect/Quick Start|44Net Connect Quick Start]]. | * For fast single-endpoint onboarding, use [[44Net Connect/Quick Start|44Net Connect Quick Start]]. | ||
* For shared routing environments, review [[IPIP Mesh/Quick Start|IPIP Mesh Quick Start]] orientation. | * For shared routing environments, review [[IPIP Mesh/Quick Start|IPIP Mesh Quick Start]] orientation. | ||
| Line 21: | Line 21: | ||
== Related pages == | == Related pages == | ||
* [[ | * [[Provisioning Methods|Provisioning Methods]] | ||
* [[44Net Connect|44Net Connect overview]] | * [[44Net Connect|44Net Connect overview]] | ||
* [[44Net Connect/Quick Start|44Net Connect Quick Start]] | * [[44Net Connect/Quick Start|44Net Connect Quick Start]] | ||
| Line 31: | Line 31: | ||
* [[Decentralization|How Connect, IPIP Mesh, and BGP fit together]] | * [[Decentralization|How Connect, IPIP Mesh, and BGP fit together]] | ||
== Contribute / | == 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. | 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. | ||
| Line 44: | Line 44: | ||
* [[Announcing your allocation directly]] | * [[Announcing your allocation directly]] | ||
* See [[Archive]] for more. | * See [[Archive]] for more. | ||
[[Category:Infrastructure]] | |||
[[Category:Routing]] | |||
Latest revision as of 01:14, 1 March 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 Provisioning Methods.
- 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
- Provisioning Methods
- 44Net Connect overview
- 44Net Connect Quick Start
- IPIP Mesh Quick Start
- BGP Quick Start
- Request Address Space
- DNS and naming
- Community and mailing lists
- How Connect, IPIP Mesh, and BGP fit together
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: