Routing - Revision history

KI5QKX: mw push

2026-09-28T22:28:11Z

mw push

← Older revision		Revision as of 22:28, 28 September 2026
Line 1:		Line 1:
	{{DISPLAYTITLE:Routing}}		{{DISPLAYTITLE:Routing}}

	~~== What this page is ==~~		Routing determines where packets go next. A working 44Net connection needs a path to your address and a return path for replies. An address assignment or DNS record alone does not establish those paths.
	~~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~~ ==		== How traffic reaches you ==
	* Pick the operating model that matches your environment in [[Provisioning Methods\|~~Provisioning Methods]].~~		{\| class="wikitable"
	* For fast single-~~endpoint onboarding, use~~ [[44Net Connect~~/Quick Start~~\|~~44Net~~ Connect ~~Quick Start]]~~.		! Connection method !! Traffic path
	* For shared routing environments, review [[IPIP Mesh~~/Quick Start~~\|IPIP ~~Mesh Quick Start]] orientation~~.		\|-
	* For independently routed infrastructure, review [[BGP~~/Quick Start\|BGP Quick Start~~]] ~~orientation~~.		\| [[44Net Connect]] \|\| A Connect node carries traffic through a WireGuard tunnel to your device or gateway.
	* Confirm address and naming prerequisites in [[Portal/Request Address Space\|~~Request Address Space]] and [[DNS\|DNS]].~~		\|-
			\| [[IPIP Mesh]] \|\| Participating gateways exchange traffic through IPIP tunnels. A shared Internet gateway handles traffic between the mesh and the wider Internet.
			\|-
			\| [[BGP]] \|\| Your provider or your own network announces your prefix. The provider delivers traffic over the connection you arrange.
			\|}

	~~== What this page will cover ==~~		Use [[Provisioning Methods]] to choose a connection method.
	* 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~~ ==		== One device or a local network ==
	* [[Provisioning Methods\|Provisioning Methods]]		With a [[44Net Connect/Single Device Tunnel\|single-device tunnel]], the 44Net address belongs to the device running WireGuard. That device controls its routes and firewall.
	* [[44Net Connect\|44Net Connect overview]]
	* [[44Net Connect/~~Quick Start\|44Net Connect Quick Start]]~~
	* [[IPIP Mesh/Quick Start\|IPIP Mesh Quick Start]]
	* [[BGP/Quick Start\|BGP Quick Start]]
	* [[Portal/Request Address Space\|Request Address Space]]
	* [[DNS\|~~DNS and naming~~]]
	* [[Community\|Community and mailing lists]]
	* [[Decentralization\|How Connect, IPIP Mesh, and ~~BGP fit together]]~~

	== ~~Contribute / next steps~~ ==		With a [[44Net Connect/Routed Subnet\|routed subnet]], the tunnel ends at a gateway. The gateway forwards traffic to local devices, which need addresses and return routes through it. Those devices do not need their own tunnels.
	~~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~~.
			Whether other Internet traffic also uses the tunnel depends on the configuration. In a split-tunnel setup, some traffic keeps using the ordinary Internet connection. See [[44Net Connect/Ways to Connect\|Ways to deploy Connect]] for the traffic behavior of each model.

			== Finding a broken path ==
			Check each part of the path before changing configuration:

			# '''Connection:''' Is the underlying Internet connection working? For Connect, is there a recent WireGuard handshake? For BGP, is the expected prefix visible outside your network?
			# '''Routes:''' Does traffic reach the tunnel or provider connection? For a routed subnet, can the gateway forward to the destination, and can that device send replies back through it?
			# '''Service and firewall:''' Is the service listening on the intended address and port? Do both the gateway and host firewalls allow it? See [[Firewalling Basics]].
			# '''Naming:''' If access by address works but access by name fails, check the [[DNS/Portal/Records\|DNS record]].
			# '''Packet size:''' If small packets work but transfers stall, check [[MTU and MSS]].

			Test both inbound and outbound traffic. A successful outbound connection does not establish that a new inbound connection is permitted. When asking for [[Get Help\|help]], include the source and destination addresses, the expected path, and the step that fails.

	~~== 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.
	[[Category:Explanation]]		[[Category:Explanation]]
	[[Category:Infrastructure]]		[[Category:Infrastructure]]
	[[Category:Routing]]		[[Category:Routing]]

KI5QKX: mw push

2026-04-30T18:52:46Z

mw push

← Older revision		Revision as of 18:52, 30 April 2026
Line 44:		Line 44:
	* [[Announcing your allocation directly]]		* [[Announcing your allocation directly]]
	* See [[Archive]] for more.		* See [[Archive]] for more.
			[[Category:Explanation]]
	[[Category:Infrastructure]]		[[Category:Infrastructure]]
	[[Category:Routing]]		[[Category:Routing]]

KI5QKX: mw push

2026-03-01T01:14:35Z

mw push

← Older revision		Revision as of 01:14, 1 March 2026
Line 7:		Line 7:

	== What you can do today ==		== What you can do today ==
	* Pick the operating model that matches your environment in [[~~Ways to Connect~~\|~~Ways to Connect~~]].		* 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 ==
	* [[~~Ways to Connect~~\|~~Ways to Connect~~]]		* [[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]]

KI5QKX: mw push

2026-03-01T00:14:45Z

mw push

← Older revision		Revision as of 00:14, 1 March 2026
Line 44:		Line 44:
	* [[Announcing your allocation directly]]		* [[Announcing your allocation directly]]
	* See [[Archive]] for more.		* See [[Archive]] for more.
			[[Category:Infrastructure]]
			[[Category:Routing]]

KI5QKX: mw push

2026-02-28T23:20:31Z

mw push

← Older revision		Revision as of 23:20, 28 February 2026
Line 31:		Line 31:
	* [[Decentralization\|How Connect, IPIP Mesh, and BGP fit together]]		* [[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.		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.

KI5QKX: mw push

2026-02-27T21:47:28Z

mw push

← Older revision		Revision as of 21:47, 27 February 2026
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 ==

KI5QKX: mw push

2026-02-27T00:24:15Z

mw push

← Older revision		Revision as of 00:24, 27 February 2026
Line 31:		Line 31:
	== 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.		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.

KI5QKX: mw push

2026-02-26T04:39:43Z

mw push

New page

{{DISPLAYTITLE: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.

== What you can do today ==
* Pick the operating model that matches your environment in [[Ways to Connect|Ways to Connect]].
* 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 independently routed infrastructure, review [[BGP/Quick Start|BGP Quick Start]] orientation.
* Confirm address and naming prerequisites in [[Portal/Request Address Space|Request Address Space]] and [[DNS|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 ==
* [[Ways to Connect|Ways to Connect]]
* [[44Net Connect|44Net Connect overview]]
* [[44Net Connect/Quick Start|44Net Connect Quick Start]]
* [[IPIP Mesh/Quick Start|IPIP Mesh Quick Start]]
* [[BGP/Quick Start|BGP Quick Start]]
* [[Portal/Request Address Space|Request Address Space]]
* [[DNS|DNS and naming]]
* [[Community|Community and mailing lists]]

== 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.