44Net Connect Quick Start - Revision history

KI5QKX: mw push

2026-03-01T00:14:36Z

mw push

← Older revision		Revision as of 00:14, 1 March 2026
Line 52:		Line 52:
	''Once the tunnel is active, your system operates as a native 44Net host. Inbound and outbound traffic is routed through the Connect endpoint, giving your device a direct connection to the Internet.''		''Once the tunnel is active, your system operates as a native 44Net host. Inbound and outbound traffic is routed through the Connect endpoint, giving your device a direct connection to the Internet.''
	}}		}}
			[[Category:Participation Methods]]
			[[Category:44Net Connect]]
			[[Category:Getting Started]]

KI5QKX: mw push

2026-02-28T23:20:22Z

mw push

← Older revision		Revision as of 23:20, 28 February 2026
Line 1:		Line 1:
	== Get ~~Started~~ with 44Net Connect ==		== Get started with 44Net Connect ==

	Before you begin, make sure you have what you need: a 44Net Portal account, a verified amateur radio callsign, a device capable of running WireGuard, and some sort of Internet access. If you haven't set up your Portal account or verified your callsign yet, see [[GetStarted\|44Net: Get Started]] for instructions. For a partial list of supported devices, see [[44Net Connect/Supported Platforms\|Supported Platforms]].		Before you begin, make sure you have what you need: a 44Net Portal account, a verified amateur radio callsign, a device capable of running WireGuard, and some sort of Internet access. If you haven't set up your Portal account or verified your callsign yet, see [[GetStarted\|44Net: Get Started]] for instructions. For a partial list of supported devices, see [[44Net Connect/Supported Platforms\|Supported Platforms]].

KI5QKX: // via Wikitext Extension for VSCode

2026-02-24T18:09:48Z

// via Wikitext Extension for VSCode

← Older revision		Revision as of 18:09, 24 February 2026
Line 1:		Line 1:
	== Get Started with 44Net Connect ==		== Get Started with 44Net Connect ==

			Before you begin, make sure you have what you need: a 44Net Portal account, a verified amateur radio callsign, a device capable of running WireGuard, and some sort of Internet access. If you haven't set up your Portal account or verified your callsign yet, see [[GetStarted\|44Net: Get Started]] for instructions. For a partial list of supported devices, see [[44Net Connect/Supported Platforms\|Supported Platforms]].

	{{Section\|class=mw-section--brief\|1=		{{Section\|class=mw-section--brief\|1=
	{{SectionAside\|		{{SectionAside\|
Line 9:		Line 12:
	* Sign in with your 44Net Portal account credentials.		* Sign in with your 44Net Portal account credentials.

	~~''New~~ to the Portal~~? See [[GetStarted]] to sign up~~ and ~~get~~ your ~~callsign verified~~. You ~~must have a verified callsign~~ to ~~use Connect. If~~ you ~~have a callsign but haven't completed verification, please~~ do ~~so before proceeding~~.''		{{Info\|Tip\|The Connect dashboard is where you will manage your tunnels, view your assigned 44Net addresses, and access your WireGuard configurations. Consider bookmarking the dashboard for easy access.}}

			{{Info\|Note\|The Connect dashboard is separate from the Portal dashboard. You will use your Portal account credentials to log in, but the two dashboards have different functions. The Portal dashboard is for managing your account, verifying your callsign, and accessing support resources, while the Connect dashboard is specifically for managing your WireGuard tunnels and configurations. You will need to log in to both dashboards at different times depending on what you want to do.}}
	}}		}}

	{{Section\|class=mw-section--brief\|1=		{{Section\|class=mw-section--brief\|1=
	{{SectionAside\|		{{SectionAside\|
	{{SectionFigure\|file=Choose Region and Node.png\|width=200px\|alt=44Net ~~Connect welcome~~ screen\|class=align-right}}		{{SectionFigure\|file=Choose Region and Node.png\|width=200px\|alt=44Net Choose Region and Node screen\|class=align-right}}
	}}		}}
	=== Step 2: Create your first tunnel ===		=== Step 2: Create your first tunnel ===
Line 21:		Line 26:
	* Enter a name for your tunnel, click the “Create Tunnel” button, and confirm.		* Enter a name for your tunnel, click the “Create Tunnel” button, and confirm.

	''Don’t worry too much about the endpoint selection. You can change it later if needed, and you can have multiple tunnels to different endpoints if you want. The tunnel name is just for your reference.''		Don’t worry too much about the endpoint selection. You can change it later if needed, and you can have multiple tunnels to different endpoints if you want. The tunnel name is just for your reference.
	}}		}}

Line 33:		Line 38:
	* Paste the configuration into your WireGuard client (Windows, macOS), or save it as a configuration file (e.g. <code>wg0.conf</code> on Linux, cloud instances, etc.).		* Paste the configuration into your WireGuard client (Windows, macOS), or save it as a configuration file (e.g. <code>wg0.conf</code> on Linux, cloud instances, etc.).

	''The configuration includes your public and private keys, an automatically-assigned 44Net address, and the endpoint information. It’s a standard WireGuard config that you can use with any compatible client or device.''		The configuration includes your public and private keys, an automatically-assigned 44Net address, and the endpoint information. It’s a standard WireGuard config that you can use with any compatible client or device.

			This is the only time you will see your private key in the Connect dashboard. If you lose it, you can generate a new configuration from the dashboard, but you cannot view the same private key again. If you opted to have the configuration sent to you via email, you can retrieve your private key from the email copy as well.
	}}		}}

	{{Section\|class=mw-section--brief\|1=		{{Section\|class=mw-section--brief\|1=
	{{SectionAside\|		{{SectionAside\|
	{{SectionFigure\|file=WireGuard macOS Manage Tunnels.png\|width=200px\|alt=44Net ~~Connect welcome~~ screen\|class=align-right}}		{{SectionFigure\|file=WireGuard macOS Manage Tunnels.png\|width=200px\|alt=44Net WireGuard macOS Manage Tunnels screen\|class=align-right}}
	}}		}}
	=== Step 4: Activate your tunnel ===		=== Step 4: Activate your tunnel ===

KI5QKX: // via Wikitext Extension for VSCode

2026-02-24T16:38:31Z

// via Wikitext Extension for VSCode

New page

== Get Started with 44Net Connect ==
{{Section|class=mw-section--brief|1=
{{SectionAside|
{{SectionFigure|file=Connect Welcome Screen.png|width=300px|alt=44Net Connect welcome screen|class=align-right}}
}}
=== Step 1: Sign in to the Connect dashboard ===
* Visit [https://connect.44net.cloud The 44Net Connect dashboard].
* Click the “Log In to Get Started” button.
* Sign in with your 44Net Portal account credentials.

''New to the Portal? See [[GetStarted]] to sign up and get your callsign verified. You must have a verified callsign to use Connect. If you have a callsign but haven't completed verification, please do so before proceeding.''
}}

{{Section|class=mw-section--brief|1=
{{SectionAside|
{{SectionFigure|file=Choose Region and Node.png|width=200px|alt=44Net Connect welcome screen|class=align-right}}
}}
=== Step 2: Create your first tunnel ===
* On the dashboard page, click the “Create Tunnel” button.
* Select an endpoint region and node.
* Enter a name for your tunnel, click the “Create Tunnel” button, and confirm.

''Don’t worry too much about the endpoint selection. You can change it later if needed, and you can have multiple tunnels to different endpoints if you want. The tunnel name is just for your reference.''
}}

{{Section|class=mw-section--brief|1=
{{SectionAside|
{{SectionFigure|file=Copy to Clipboard.png|width=200px|alt=44Net Connect welcome screen|class=align-right}}
}}
=== Step 3: Get your WireGuard configuration ===
* Scroll down to find your tunnel configuration.
* Click the “Copy to Clipboard” button to copy the configuration text.
* Paste the configuration into your WireGuard client (Windows, macOS), or save it as a configuration file (e.g. <code>wg0.conf</code> on Linux, cloud instances, etc.).

''The configuration includes your public and private keys, an automatically-assigned 44Net address, and the endpoint information. It’s a standard WireGuard config that you can use with any compatible client or device.''
}}

{{Section|class=mw-section--brief|1=
{{SectionAside|
{{SectionFigure|file=WireGuard macOS Manage Tunnels.png|width=200px|alt=44Net Connect welcome screen|class=align-right}}
}}
=== Step 4: Activate your tunnel ===
* Start the WireGuard tunnel (“Activate” in the client, or <code>wg-quick up wg0</code> on Linux).

''Once the tunnel is active, your system operates as a native 44Net host. Inbound and outbound traffic is routed through the Connect endpoint, giving your device a direct connection to the Internet.''
}}