44Net Connect/Supported Platforms: Difference between revisions
mw push |
Added platform list section and link to 44Net Connect/Quick Start/Raspberry Pi |
||
| Line 18: | Line 18: | ||
* Platform-specific notes for key handling and persistence. | * Platform-specific notes for key handling and persistence. | ||
* Known incompatibilities and current workarounds. | * Known incompatibilities and current workarounds. | ||
== Platform List == | |||
* [[44Net Connect/Quick Start/Raspberry Pi|Raspberry Pi]] | |||
== Related pages == | == Related pages == | ||
Latest revision as of 23:01, 28 May 2026
What this page is
This page lists platform support for 44Net Connect and who should use each option. Use it when you need to choose a device, OS, or router for a tunnel endpoint.
What you can do today
- Confirm baseline setup flow in 44Net Connect Quick Start.
- Use 44Net Connect on pfSense for a pfSense firewall or gateway.
- Verify account and callsign status in Getting started and Portal Sign Up.
- Check whether your target environment can run WireGuard before requesting production routing changes.
- If your platform is not documented yet, ask in the ARDC 44Net discussion group.
What this page will cover
- Supported desktop operating systems and client choices.
- Supported router/firewall platforms and caveats behind NAT.
- Mobile platform status and operational limitations.
- Platform-specific notes for key handling and persistence.
- Known incompatibilities and current workarounds.
Platform List
Related pages
- 44Net Connect Quick Start
- 44Net Connect overview
- Getting started
- Provisioning Methods
- Portal Sign Up
- Routing and connectivity
- Community and mailing lists
Contribute / next steps
If you operate a platform that works (or fails), document the exact OS/version, WireGuard client, NAT or firewall posture, and handshake behavior. Share those details in Contributing so this page can be updated with reproducible guidance.