Routing

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:

• RIP
• Filtering RFC1918 Addresses
• Firewalls
• Ipv6
• Networks that use 44Net
• Routing your allocation via BGP
• Announcing your allocation directly
• See Archive for more.