01 / OVERVIEW
Overview
P2P VPN includes a public website, a user console, clients, backup hole-punching nodes, and independent relays. Users manage networks, groups, and devices, with clients preferring direct connections. The control service coordinates accounts and connectivity; relaying depends on deployed online infrastructure.
02 / CAPABILITIES
Key capabilities
01
Network, group, and device management
02
P2P direct connections with optional WSS relays
03
Windows and Linux clients, plus Android source
03 / POSSIBILITIES
Ideas to explore
- Validate virtual-network connections between grouped devices in a controlled environment
- Study NAT traversal, control coordination, and optional relaying
- Evaluate client behavior across operating systems and network conditions
04 / GET STARTED
Getting started
Before you begin
- Check the current release for operating-system and architecture support
- Configure server authentication, email, and nodes as documented
- Client installation and virtual interfaces require appropriate system permissions
Get the project
git clone https://github.com/hnlyf168/p2pvpn.gitNext steps
- Read the deployment and architecture documents to understand each service's role.
- Create a network and group in your test environment, then add devices.
- Verify connectivity with a second grouped device and evaluate relay needs.
05 / SCOPE & STATUS
Current boundaries
Connectivity depends on NAT, firewalls, and network conditions. Relaying requires deployed online nodes. Platform availability follows the current release documentation.
This introduction is based on the public README. Consult the repository for current versions, licenses, and supported features.
Updated 2026-10-27