Routing: Difference between revisions

From 44Net Wiki
mw push
mw push
 
Line 4: Line 4:
This page is the routing orientation hub for 44Net participation.
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.
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 ==
== What you can do today ==
Line 28: Line 29:
* [[DNS|DNS and naming]]
* [[DNS|DNS and naming]]
* [[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 ==

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

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: