Ways to Connect - Revision history

KI5QKX: mw push

2026-03-01T00:14:39Z

mw push

← Older revision		Revision as of 00:14, 1 March 2026
Line 1:		Line 1:
	#REDIRECT [[Provisioning Methods]]		#REDIRECT [[Provisioning Methods]]
			[[Category:Participation Methods]]

KI5QKX: mw push

2026-02-28T18:37:47Z

mw push

← Older revision		Revision as of 18:37, 28 February 2026
Line 1:		Line 1:
	~~{{DISPLAYTITLE:Ways to Connect}}~~		#REDIRECT [[Provisioning Methods]]

	~~New here? Start with~~ [[~~GetStarted\|Getting started~~]].

	There are several ways to bring 44Net to your device or network. Each method reflects a different networking environment rather than a level of experience. Some participants place 44Net on a single system behind NAT, others operate within shared community networks, and some integrate 44Net directly into independently operated infrastructure.

	~~Choose the approach that fits best with your current setup.~~
	~~To understand why these approaches are independent by design, see [[Decentralization]].~~

	~~== Choose your starting point ==~~

	~~=== Single host or mobile deployment ===~~
	~~'''[[44Net Connect/Quick Start\|44Net Connect]]'''~~

	~~The fastest way to put 44Net on a device or small network.~~

	* Works from typical home networks, cloud hosts, or mobile devices
	* Minimal setup; often requires no router changes
	* Good for experimentation, hosting services, or learning how 44Net works
	* Lets you route a small subnet if you want to grow beyond a single host

	~~→ [[44Net Connect/Quick Start\|Get started with 44Net Connect]]~~

	~~----~~

	~~=== Community or regional network ===~~
	~~'''[[IPIP Mesh/Quick Start\|IPIP Mesh]]'''~~

	~~A long‑standing 44Net deployment model built around shared community routing.~~

	* Connect independent stations into a shared routed environment
	* Common in long‑running regional and club networks
	* Traffic to and from the wider Internet typically transits shared gateways (such as UCSD)
	* Well suited for persistent stations that participate in community infrastructure

	~~----~~

	~~=== Independently routed network ===~~
	~~'''[[BGP/Quick Start\|BGP-announced subnet]]'''~~

	~~Integrate 44Net directly into an independently operated network.~~

	* Announce 44Net routes using your existing routing infrastructure
	* Maintain your own routing policy and operational practices
	* Suitable for research networks, IX-connected operators, community backbones, and advanced deployments
	* Emphasizes autonomy rather than centralized gateways

	~~== Comparing the approaches ==~~

	~~Use this table to decide which model matches how you want to participate.~~

	~~{\| class="wikitable"~~
	~~! Path~~
	~~! Best when you…~~
	~~! How your traffic reaches the Internet~~
	~~! What you operate~~
	\|-
	~~\| 44Net Connect~~
	~~\| want a 44Net presence on one host or a small network, from almost any uplink (home, cloud, mobile)~~
	~~\| 44Net traffic is carried over a tunnel you operate from your host or router~~
	~~\| a tunnel endpoint you control; optional routing for a small routed subnet~~
	\|-
	~~\| IPIP Mesh~~
	~~\| want to participate in a shared community network (regional, club, collaborative)~~
	~~\| your traffic typically transits shared mesh gateways (such as UCSD) and can route within the mesh~~
	~~\| a mesh node that peers with other nodes; routing within the shared mesh~~
	\|-
	~~\| BGP-announced subnet~~
	~~\| already operate routable infrastructure and want to integrate 44Net directly into it~~
	~~\| your routes are announced via BGP as part of global routing (under your policy)~~
	~~\| your own routers, BGP edge, and routing policy for the subnet~~
	\|}

	~~== Choosing the right fit ==~~

	~~These connection methods coexist and serve different operational needs.~~

	* '''44Net Connect''' places 44Net on an individual device or small network and works from almost anywhere.

	* '''IPIP Mesh''' connects independently operated stations into a shared routing environment with community gateways.

	* '''BGP‑announced subnets''' integrate 44Net into networks that already participate in Internet routing.

	~~Many participants use whichever model fits their environment today. Some operate more than one at the same time.~~

	~~== Under the hood ==~~

	All connection methods ultimately place your systems into the same shared 44Net address space. The differences are operational: how routes reach you, where gateways exist, and who is responsible for routing decisions.

	~~== Learn more ==~~

	* [[GetStarted\|Getting started]]
	* [[Routing\|Routing and connectivity]]
	* [[CommunityProjects\|Community projects]]
	* [[Decentralization\|How Connect, IPIP Mesh, and BGP fit together]]

	~~== Older docs and notes ==~~
	~~Earlier pages that may still be useful:~~
	* [[Gateway]]
	* [[Registering Your Gateway]]
	* [[Tunnel]]
	* [[AMPRNet VPN]]
	* [[Routing your allocation via BGP]]
	* [[Announcing your allocation directly]]
	* [[FAQ\|Why can’t I announce my allocation directly?]]
	* See [[Archive]] for more.

KI5QKX: mw push

2026-02-27T21:47:18Z

mw push

← Older revision		Revision as of 21:47, 27 February 2026
Line 6:		Line 6:

	Choose the approach that fits best with your current setup.		Choose the approach that fits best with your current setup.
			To understand why these approaches are independent by design, see [[Decentralization]].

	== Choose your starting point ==		== Choose your starting point ==
Line 92:		Line 93:
	* [[Routing\|Routing and connectivity]]		* [[Routing\|Routing and connectivity]]
	* [[CommunityProjects\|Community projects]]		* [[CommunityProjects\|Community projects]]
			* [[Decentralization\|How Connect, IPIP Mesh, and BGP fit together]]

	== Older docs and notes ==		== Older docs and notes ==

KI5QKX: mw push

2026-02-27T19:13:29Z

mw push

← Older revision		Revision as of 19:13, 27 February 2026
Line 101:		Line 101:
	* [[Routing your allocation via BGP]]		* [[Routing your allocation via BGP]]
	* [[Announcing your allocation directly]]		* [[Announcing your allocation directly]]
	* [[Why ~~can't~~ I ~~just route~~ my ~~AMPRNet~~ allocation directly ~~myself~~ ?]]		* [[FAQ\|Why can’t I announce my allocation directly?]]
	* See [[Archive]] for more.		* See [[Archive]] for more.

KI5QKX: mw push

2026-02-27T00:24:10Z

mw push

← Older revision		Revision as of 00:24, 27 February 2026
Line 92:		Line 92:
	* [[Routing\|Routing and connectivity]]		* [[Routing\|Routing and connectivity]]
	* [[CommunityProjects\|Community projects]]		* [[CommunityProjects\|Community projects]]

			== Older docs and notes ==
			Earlier pages that may still be useful:
			* [[Gateway]]
			* [[Registering Your Gateway]]
			* [[Tunnel]]
			* [[AMPRNet VPN]]
			* [[Routing your allocation via BGP]]
			* [[Announcing your allocation directly]]
			* [[Why can't I just route my AMPRNet allocation directly myself ?]]
			* See [[Archive]] for more.

KI5QKX: mw push

2026-02-26T04:39:38Z

mw push

← Older revision		Revision as of 04:39, 26 February 2026
Line 1:		Line 1:
	{{DISPLAYTITLE:Ways to Connect}}		{{DISPLAYTITLE:Ways to Connect}}

	~~{{Lead~~\|~~44Net supports multiple connection paths~~. ~~Choose the one that matches your current setup and experience.}}~~		New here? Start with [[GetStarted\|Getting started]].

	~~New here? Start~~ with [[~~GetStarted~~\|~~Getting started~~]] -> [[~~Ways to~~ Connect\|~~Ways to~~ Connect]]~~. Fastest first path:~~ [[~~GetStarted#Get_Started_with_44Net_Connect~~\|44Net Connect]].		There are several ways to bring 44Net to your device or network. Each method reflects a different networking environment rather than a level of experience. Some participants place 44Net on a single system behind NAT, others operate within shared community networks, and some integrate 44Net directly into independently operated infrastructure.

			Choose the approach that fits best with your current setup.

			== Choose your starting point ==

			=== Single host or mobile deployment ===
			'''[[44Net Connect/Quick Start\|44Net Connect]]'''

			The fastest way to put 44Net on a device or small network.

			* Works from typical home networks, cloud hosts, or mobile devices
			* Minimal setup; often requires no router changes
			* Good for experimentation, hosting services, or learning how 44Net works
			* Lets you route a small subnet if you want to grow beyond a single host

			→ [[44Net Connect/Quick Start\|Get started with 44Net Connect]]

			----

			=== Community or regional network ===
			'''[[IPIP Mesh/Quick Start\|IPIP Mesh]]'''

			A long‑standing 44Net deployment model built around shared community routing.

			* Connect independent stations into a shared routed environment
			* Common in long‑running regional and club networks
			* Traffic to and from the wider Internet typically transits shared gateways (such as UCSD)
			* Well suited for persistent stations that participate in community infrastructure

			----

			=== Independently routed network ===
			'''[[BGP/Quick Start\|BGP-announced subnet]]'''

			Integrate 44Net directly into an independently operated network.

			* Announce 44Net routes using your existing routing infrastructure
			* Maintain your own routing policy and operational practices
			* Suitable for research networks, IX-connected operators, community backbones, and advanced deployments
			* Emphasizes autonomy rather than centralized gateways

			== Comparing the approaches ==

			Use this table to decide which model matches how you want to participate.

	{\| class="wikitable"		{\| class="wikitable"
	! Path		! Path
	! ~~Setup effort~~		! Best when you…
	! ~~Networking knowledge~~		! How your traffic reaches the Internet
	! ~~Typical use case~~		! What you operate
	\|-		\|-
	\| ~~[[GetStarted#Get_Started_with_44Net_Connect~~\|44Net ~~Connect~~ (~~WireGuard~~)]]		\| 44Net Connect
	\| ~~Low~~		\| want a 44Net presence on one host or a small network, from almost any uplink (home, cloud, mobile)
	\| ~~Basic~~		\| 44Net traffic is carried over a tunnel you operate from your host or router
	~~\| Fastest way to get~~ a ~~host online~~		\| a tunnel endpoint you control; optional routing for a small routed subnet
	\|-		\|-
	~~\| [[GetStarted#Get_Started_with_IPIP_Mesh~~\|IPIP Mesh]]		\| IPIP Mesh
	\| ~~Medium~~		\| want to participate in a shared community network (regional, club, collaborative)
	\| ~~Basic to intermediate~~		\| your traffic typically transits shared mesh gateways (such as UCSD) and can route within the mesh
	\| ~~Host and site interconnection via tunnel~~ mesh		\| a mesh node that peers with other nodes; routing within the shared mesh
	\|-		\|-
	~~\| [[GetStarted#Get_Started_with_BGP-Announced_Subnets~~\|BGP-~~Announced Subnet]]~~		\| BGP-announced subnet
	\| ~~High~~		\| already operate routable infrastructure and want to integrate 44Net directly into it
	\| ~~Advanced~~		\| your routes are announced via BGP as part of global routing (under your policy)
	\| ~~Operating~~ your own ~~routed network~~ and ~~announcements~~		\| your own routers, BGP edge, and routing policy for the subnet
	\|}		\|}

	== ~~IPIP mesh~~ ==		== Choosing the right fit ==

	~~Choose this when you want community tunnel interconnection~~ and ~~are comfortable with basic tunnel configuration~~.		These connection methods coexist and serve different operational needs.

	~~Primary next step: [[GetStarted#Get_Started_with_IPIP_Mesh\|Get Started with IPIP Mesh]]~~		* '''44Net Connect''' places 44Net on an individual device or small network and works from almost anywhere.

	~~Technical references:~~		* '''IPIP Mesh''' connects independently operated stations into a shared routing environment with community gateways.
	* ~~[[Routing\|Routing and connectivity]]~~

	== 44Net ~~Connect (WireGuard) ==~~		* '''BGP‑announced subnets''' integrate 44Net into networks that already participate in Internet routing.

	~~Choose this when your priority is a straightforward first deployment on a single system~~.		Many participants use whichever model fits their environment today. Some operate more than one at the same time.

	~~Primary next step: [[GetStarted#Get_Started_with_44Net_Connect\|Get Started with 44Net Connect]]~~

	~~Technical references:~~
	* [[Routing\|Routing and connectivity]]

	== ~~BGP-announced subnet~~ ==		== Under the hood ==

	~~Choose this when you~~ are ~~operating router infrastructure and need full control of announced~~ routes and ~~policy~~.		All connection methods ultimately place your systems into the same shared 44Net address space. The differences are operational: how routes reach you, where gateways exist, and who is responsible for routing decisions.

	~~Primary next step: [[GetStarted#Get_Started_with_BGP-Announced_Subnets\|Get Started with BGP-Announced Subnets]]~~		== Learn more ==

	~~Technical references:~~		* [[GetStarted\|Getting started]]
	* [[Routing\|Routing and connectivity]]		* [[Routing\|Routing and connectivity]]
			* [[CommunityProjects\|Community projects]]

KI5QKX: mw push

2026-02-25T22:50:43Z

mw push

← Older revision		Revision as of 22:50, 25 February 2026
Line 27:		Line 27:
	\|}		\|}

	= IPIP ~~Mesh~~ =		== IPIP mesh ==

	Choose this when you want community tunnel interconnection and are comfortable with basic tunnel configuration.		Choose this when you want community tunnel interconnection and are comfortable with basic tunnel configuration.
Line 36:		Line 36:
	* [[Routing\|Routing and connectivity]]		* [[Routing\|Routing and connectivity]]

	= 44Net Connect (WireGuard) =		== 44Net Connect (WireGuard) ==

	Choose this when your priority is a straightforward first deployment on a single system.		Choose this when your priority is a straightforward first deployment on a single system.
Line 45:		Line 45:
	* [[Routing\|Routing and connectivity]]		* [[Routing\|Routing and connectivity]]

	= BGP-~~Announced Subnet~~ =		== BGP-announced subnet ==

	Choose this when you are operating router infrastructure and need full control of announced routes and policy.		Choose this when you are operating router infrastructure and need full control of announced routes and policy.

KI5QKX: mw push

2026-02-25T20:30:15Z

mw push

New page

{{DISPLAYTITLE:Ways to Connect}}

{{Lead|44Net supports multiple connection paths. Choose the one that matches your current setup and experience.}}

New here? Start with [[GetStarted|Getting started]] -> [[Ways to Connect|Ways to Connect]]. Fastest first path: [[GetStarted#Get_Started_with_44Net_Connect|44Net Connect]].

{| class="wikitable"
! Path
! Setup effort
! Networking knowledge
! Typical use case
|-
| [[GetStarted#Get_Started_with_44Net_Connect|44Net Connect (WireGuard)]]
| Low
| Basic
| Fastest way to get a host online
|-
| [[GetStarted#Get_Started_with_IPIP_Mesh|IPIP Mesh]]
| Medium
| Basic to intermediate
| Host and site interconnection via tunnel mesh
|-
| [[GetStarted#Get_Started_with_BGP-Announced_Subnets|BGP-Announced Subnet]]
| High
| Advanced
| Operating your own routed network and announcements
|}

= IPIP Mesh =

Choose this when you want community tunnel interconnection and are comfortable with basic tunnel configuration.

Primary next step: [[GetStarted#Get_Started_with_IPIP_Mesh|Get Started with IPIP Mesh]]

Technical references:
* [[Routing|Routing and connectivity]]

= 44Net Connect (WireGuard) =

Choose this when your priority is a straightforward first deployment on a single system.

Primary next step: [[GetStarted#Get_Started_with_44Net_Connect|Get Started with 44Net Connect]]

Technical references:
* [[Routing|Routing and connectivity]]

= BGP-Announced Subnet =

Choose this when you are operating router infrastructure and need full control of announced routes and policy.

Primary next step: [[GetStarted#Get_Started_with_BGP-Announced_Subnets|Get Started with BGP-Announced Subnets]]

Technical references:
* [[Routing|Routing and connectivity]]